导航|地址|刷新
Cascade Skills






!DOCTYPE html>


Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.


Skip to main content









Devin Docs home page
English




Search...

⌘ KAsk Assistant


Support

Devin


Devin





Search...



Navigation


Cascade

Skills




Cloud

CLI

Desktop

Enterprise

Use Cases

API

Federal
















Devin Desktop



Editor






Devin Local Agent




Cascade





Overview





Arena Mode





Modes





App Deploys





Web and Docs Search





Memories & Rules





Skills





AGENTS.md





Workflows





Worktrees





Model Context Protocol (MCP)





Cascade Hooks





Context Awareness





Troubleshooting







Agent Command Center




Agent Command Center





Spaces





Devin





Agent Client Protocol (preview)





Building a custom ACP agent






Releases






Changelog







Changelog (Next)







Releases







Releases (Next)






Windsurf Plugins



Changelog





Get Started





Features





Cascade (JetBrains)





Context Awareness





Best Practices





Troubleshooting







Accounts




Usage





Quota





Analytics




Teams & Enterprise







Security




FedRAMP Security Admin Guide





Reporting















On this page


How to Create a Skill
Using the UI (easiest)

Manual Creation


SKILL.md File Format
Example skill

Required Frontmatter Fields


Adding Supporting Resources

Invoking Skills
Automatic Invocation

Manual Invocation


Skill Scopes
System-Level Skills (Enterprise)


Example Use Cases
Deployment Workflow

Code Review Guidelines

Testing Procedures


Best Practices

Skills vs Rules vs Workflows

Related Documentation









Cascade


Skills


Copy pageCopy page





Skills help Cascade handle complex, multi-step tasks.



Copy pageCopy page


The hardest engineering tasks often take more than just good prompts. They might require reference scripts, templates, checklists, and other supporting files. Skills let you bundle all of these together into folders that Cascade can invoke (read and use).Skills are a great way to teach Cascade how to execute multi-step workflows consistently.The Devin Local agent uses the Devin CLI skills format and discovery — see Skills.Cascade uses progressive disclosure: only the skill’s name and description are shown to the model by default. The full SKILL.md content and supporting files are loaded only when Cascade decides to invoke the skill (or when you @mention it). This keeps your context window lean even with many skills defined.For more details on the Skills specification, visit agentskills.io.

​


How to Create a Skill


​


Using the UI (easiest)

Open the Cascade panel

Click the three dots in the top right of the panel to open up the customizations menu

Click on the Skills section

Click + Workspace to create a workspace (project-specific) skill, or + Global to create a global skill

Name the skill (lowercase letters, numbers, and hyphens only)


​


Manual Creation
Workspace Skill (project-specific):
Create a directory: .windsurf/skills/<skill-name>/

Add a SKILL.md file with YAML frontmatter
Global Skill (available in all workspaces):
Create a directory: ~/.codeium/windsurf/skills/<skill-name>/

Add a SKILL.md file with YAML frontmatter


​


SKILL.md File Format
Each skill requires a SKILL.md file with YAML frontmatter containing the skill’s metadata:

​


Example skill











---name: deploy-to-productiondescription: Guides the deployment process to production with safety checks---## Pre-deployment Checklist1. Run all tests2. Check for uncommitted changes3. Verify environment variables## Deployment StepsFollow these steps to deploy safely...[Reference supporting files in this directory as needed]








​


Required Frontmatter Fields

name: Unique identifier for the skill (displayed in UI and used for @-mentions)

description: Brief explanation shown to the model to help it decide when to invoke the skill
Examples of valid names: deploy-to-staging, code-review, setup-dev-environment

​


Adding Supporting Resources
Place any supporting files in the skill folder alongside SKILL.md. These files become available to Cascade when the skill is invoked:










.windsurf/skills/deploy-to-production/├── SKILL.md├── deployment-checklist.md├── rollback-procedure.md└── config-template.yaml








​


Invoking Skills


​


Automatic Invocation
When your request matches a skill’s description, Cascade automatically invokes the skill and uses its instructions and resources to complete the task. This is the most common way skills are used—you simply describe what you want to do, and Cascade determines which skills are relevant.The description field in your skill’s frontmatter is key: it helps Cascade understand when to invoke the skill. Write descriptions that clearly explain what the skill does and when it should be used.

​


Manual Invocation
You can always explicitly activate a skill by typing @skill-name in the Cascade input. This is useful when you want to ensure a specific skill is used, or when you want to invoke a skill that might not be automatically triggered by your request.

​


Skill Scopes

Scope	Location	Availability
Workspace	.windsurf/skills/	Current workspace only. Committed with your repo.
Global	~/.codeium/windsurf/skills/	All workspaces on your machine. Not committed.
System (Enterprise)	OS-specific (see below)	All workspaces, deployed by IT. Read-only.

For cross-agent compatibility, Devin Desktop also discovers skills in .agents/skills/ and ~/.agents/skills/. If you have enabled Claude Code config reading, .claude/skills/ and ~/.claude/skills/ are scanned as well.



​


System-Level Skills (Enterprise)
Enterprise organizations can deploy skills that are available across all workspaces and cannot be modified by end users:

OS	Path
macOS	/Library/Application Support/Windsurf/skills/
Linux/WSL	/etc/windsurf/skills/
Windows	C:\ProgramData\Windsurf\skills\

Each skill is a subdirectory containing a SKILL.md file, just like workspace skills.

​


Example Use Cases


​


Deployment Workflow
Create a skill with deployment scripts, environment configs, and rollback procedures:










.windsurf/skills/deploy-staging/├── SKILL.md├── pre-deploy-checks.sh├── environment-template.env└── rollback-steps.md








​


Code Review Guidelines
Include style guides, security checklists, and review templates:










.windsurf/skills/code-review/├── SKILL.md├── style-guide.md├── security-checklist.md└── review-template.md








​


Testing Procedures
Bundle test templates, coverage requirements, and CI/CD configs:










.windsurf/skills/run-tests/├── SKILL.md├── test-template.py├── coverage-config.json└── ci-workflow.yaml








​


Best Practices

Write clear descriptions: The description helps Cascade decide when to invoke the skill. Be specific about what the skill does and when it should be used.

Include relevant resources: Templates, checklists, and examples make skills more useful. Think about what files would help someone complete the task.

Use descriptive names: deploy-to-staging is better than deploy1. Names should clearly indicate what the skill does.


​


Skills vs Rules vs Workflows
All three customize Cascade, but they differ in structure, invocation, and context cost:

	Skills	Rules	Workflows
Purpose	Multi-step procedures with supporting files	Behavioral guidelines (“how to behave”)	Prompt templates for repeatable tasks
Structure	Folder with SKILL.md + any resource files	Single .md file with frontmatter	Single .md file
Invocation	Model decides (progressive disclosure) or @mention	always_on / glob / model_decision / manual	Manual only via /slash-command
In system prompt?	No — only name + description until invoked	Depends on activation mode	No — listed as available commands
Best for	Deployments, code review, testing procedures that need scripts/templates	Coding style, project conventions, constraints	One-shot runbooks you trigger explicitly

Rule of thumb: if Cascade should pick it up automatically and it needs supporting files, use a Skill. If it’s a short behavioral constraint, use a Rule. If you always want to trigger it yourself, use a Workflow.

​


Related Documentation
If Skills aren’t what you’re looking for, check out these other Cascade features:
Workflows - Automate repetitive tasks with reusable markdown workflows invoked via slash commands

AGENTS.md - Provide directory-scoped instructions that automatically apply based on file location

Memories & Rules - Persist context across conversations with auto-generated memories and user-defined rules


Memories & RulesAGENTS.md





⌘ I





linkedinx


Powered byThis documentation is built and hosted on Mintlify, a developer documentation platform












Assistant









Responses are generated using AI and may contain mistakes.


















self.__next_f.push([1,"\"use strict\";const{Fragment:_Fragment,jsx:_jsx,jsxs:_jsxs}=arguments[0];const{useMDXComponents:_provideComponents}=arguments[0];function _createMdxContent(props){const _components={a:`a`,code:`code`,em:`em`,li:`li`,ol:`ol`,p:`p`,pre:`pre`,span:`span`,strong:`strong`,tbody:`tbody`,td:`td`,th:`th`,thead:`thead`,tr:`tr`,ul:`ul`,..._provideComponents(),...props.components},{CodeBlock,Heading,Note,Table}=_components;if(!CodeBlock)_missingMdxReference(`CodeBlock`,true);if(!Heading)_missingMdxReference(`Heading`,true);if(!Note)_missingMdxReference(`Note`,true);if(!Table)_missingMdxReference(`Table`,true);return _jsxs(_Fragment,{children:[_jsx(_components.p,{children:`The hardest engineering tasks often take more than just good prompts. They might require reference scripts, templates, checklists, and other supporting files. Skills let you bundle all of these together into folders that Cascade can invoke (read and use).`}),`\n`,_jsx(_components.p,{children:`Skills are a great way to teach Cascade how to execute multi-step workflows consistently.`}),`\n`,_jsxs(_components.p,{children:[`The `,_jsx(_components.a,{href:`/desktop/devin-local`,children:`Devin Local agent`}),` uses the Devin CLI skills format and discovery — see `,_jsx(_components.a,{href:`/cli/extensibility/skills/overview`,children:`Skills`}),`.`]}),`\n`,_jsxs(_components.p,{children:[`Cascade uses `,_jsx(_components.a,{href:`https://agentskills.io/what-are-skills#how-skills-work`,children:_jsx(_components.strong,{children:`progressive disclosure`})}),`: only the skill’s `,_jsx(_components.code,{children:`name`}),` and `,_jsx(_components.code,{children:`description`}),` are shown to the model by default. The full `,_jsx(_components.code,{children:`SKILL.md`}),` content and supporting files are loaded `,_jsx(_components.strong,{children:`only when Cascade decides to invoke the skill`}),` (or when you `,_jsx(_components.code,{children:`@mention`}),` it). This keeps your context window lean even with many skills defined.`]}),`\n`,_jsxs(_components.p,{children:[`For more details on the Skills specification, visit `,_jsx(_components.a,{href:`https://agentskills.io/home`,children:`agentskills.io`}),`.`]}),`\n`,_jsx(Heading,{level:`2`,id:`how-to-create-a-skill`,children:`How to Create a Skill`}),`\n`,_jsx(Heading,{level:`3`,id:`using-the-ui-easiest`,children:`Using the UI (easiest)`}),`\n`,_jsxs(_components.ol,{children:[`\n`,_jsx(_components.li,{children:`Open the Casc
------
导航页 打开网址