Some screenshots show mcp-s.com, which some existing organizations still use. New organizations use withwillow.ai. Copy the URLs shown in your own organization.
Create Skills
Skills are Markdown documents that instruct your AI on how to approach a task. There are three ways to create them.
Method 1: Manual (write in the editor)
The fastest way for short skills or when you're writing from scratch.
- Click Skills in the sidebar
- Click + Add Skill
- Select Manual

- Fill in the form:
- Name: 1–64 characters: lowercase letters, numbers, and hyphens (for example,
code-review-checklist) - Slug: Lowercase letters, numbers, and hyphens
- Description: What the skill does and when to use it, up to 1,024 characters
- Content (Markdown): The skill body
- Name: 1–64 characters: lowercase letters, numbers, and hyphens (for example,
- Click Create Skill
The preview panel on the right shows how the content renders as you type.

Method 2: Upload (.skill or .zip)
Use this when you have skill files on your computer, for example exported from another Willow instance.
- Click + Add Skill
- Select Upload .zip / .skill
- A file picker opens. Select your
.skillor.zipfile. - Review the imported content
- Click Create Skill
.skill files are individual skills. .zip files can contain multiple skills at once.
Method 3: From GitHub
Import skills from a public GitHub repository. Useful when your team stores skills in version control.
- Click + Add Skill
- Select From GitHub
- In Import Skills from GitHub, enter the repository as
owner/repo(a fullhttps://github.com/owner/repoURL also works)

- Click Next
Willow scans the whole repository for skills: any folder containing a SKILL.md file, for example under skills/, .claude/skills/, or .cursor/skills/, in nested folders, or at the repository root.
Managing existing skills
Each skill card shows the name, description, and a preview. Available actions:

Eye icon (View): See the full skill content.
Use: Opens a dialog to install the skill into your coding agent. Choose Install via CLI to run the install command in your terminal (npx @mcp-s/skills add ...), or Download to save the skill file locally. On Install via CLI, you can pick a specific Agent (the default installs for all supported agents) and choose Install globally to install at user level instead of in the current project.

Three-dot menu (⋮): Opens additional actions.

- Edit: Open in the editor to modify name, description, or content.
- Share: Share this skill with specific teammates by email. Set their permission to Read or Write.

- Duplicate: Creates a copy. Useful as a starting point for a variation.
- Delete: Permanently removes the skill.
Skill content format
Skills are plain Markdown. Write them as instructions to your AI:
# Code Review Process
When reviewing code, follow this sequence:
1. Check for logic errors and edge cases
2. Verify error handling is complete
3. Look for missing test coverage
4. Review for security issues (injection, auth, data exposure)
5. Check code style matches the project conventions
For each issue found, note:
- The line or section
- Why it's a problem
- A suggested fix
Keep skills focused on one task. Broad skills ("be a good developer") are less useful than specific ones ("how we review pull requests").
Related
- Create your first skill: step-by-step tutorial
- Create commands: for text templates, not instructions