create-skill
Skill10 starsChanged 3 months agoMITView on GitHub
Help create a new AI agent skill through collaborative Q&A
142 other projects use a version of this.
Adopted by
Most recently taken up by
- lancy69/skillstheir own version, first seen Nov 8, 2026
- CherryHQ/cherry-studiotheir own version, first seen Nov 8, 2026
- niilohlin/skillstheir own version, first seen Nov 8, 2026
- sankalpaacharya/skillstheir own version, first seen Nov 8, 2026
- zalogarcia/zalo-claude-code-setuptheir own version, first seen Nov 8, 2026
- serbyte-development/shellby-mcptheir own version, first seen Nov 8, 2026
Used with
Projects with it also use review-bugbot, migrate-to-skills and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
0mlkrizzz655335vSkillreview-bugbot
缺陷导向代码审查。用 Bugbot 子代理找 bug。
Also in 5 projects that use this
32103210Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
Also in 8 projects that use this
- 32103210Skill
update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Also in 8 projects that use this
PandelisZSkillupdate-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
Also in 7 projects that use this
yawningwhaleAISkillbuild-premium-website
Build a premium, animated marketing website (React + Vite + Tailwind + GSAP) for any industry. Use when the user asks to "build a website", "make a landing page for [business]", "build a marketing site", or wants a high-end animated company website. Adapts color, copy, services, and signature animation to the industry.
Also in 6 projects that use this
- yawningwhaleAISkill
instantly-campaign
Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.
Also in 5 projects that use this
- +1 more from 32103210
Other versions142 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 142
- microsoft/vscode★ 195ksame name
- CherryHQ/cherry-studio★ 53ksame name
- videojs/video.js★ 40ksame name
- BuilderIO/agent-native★ 7.6ksame name
- stagewise-io/stagewise★ 6.8ksame name
- dotnet/skills★ 5.9ksame name
- xstongxue/best-skills★ 2.9ksame name
- Lilac-Labs/gini-agent★ 1.9ksame name
- Open-Curiosity/gini-agent★ 1.9ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
132 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- instructions/claude.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- adr-authorSkill
- analyze-r-packageSkill
- bioc-howtoSkill
- bioc-pkg-devSkill
- bioc-pkg-finderSkill
- bioc-pkg-reviewSkill
- build-check-bioccheckSkill
- check-bioconductor-skillsSkill
- create-package-instructionsSkill
- document-skillSkill
- improve-code-coverageSkill
- migrate-datapkg-to-zenodoSkill
- security-audit-r-packageSkill
- update-package-instructionsSkill
- update-r-newsSkill
- validate-skillSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 132 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Start with open-ended questions:
- Very specific: line 45
If uncertain, suggest the closest match.
- Distinctive: line 49
Ask the user to walk through the steps.
- Very specific: line 53
Create a well-structured skill file following AGENTS.md and SKILL_STANDARD.md.
- Very specific: line 54
Do not duplicate SSOT guidelines.
- Very specific: line 63
Before updating repository documentation, invoke validate-skill on the new file.
- Distinctive: line 75
Skills are agent-agnostic: No platform-specific metadata in the file
- Distinctive: line 76
Describe what, not how: Use "read the file" not "use Read tool"
- Very specific: line 89
Run validate-skill before document-skill
“Common” is measured: kept by at least 6 in 10 of the 132 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
create-skill
Help create new AI agent skills through collaborative Q&A. Guides from rough ideas to structured skill files, focusing on intent over perfect formatting.
Usage
Invoke this skill when you want to create a new skill:
- "Help me create a new skill for [domain/purpose]"
Prerequisites
- You have a general idea of what you want the skill to do
- Working directory is the ai-agent-skills repository
Process
- Understand the user's intent through Q&A
- Determine domain and location
- Outline the process steps
- Generate the skill file
- Review and refine with user feedback
- Validate the skill against repository standards
- Update repository documentation
1. Understand the Intent
Start with open-ended questions:
- "What problem are you trying to solve?"
- "Who would use this skill?"
- "Can you give me an example of when you'd use this?"
- "What would be the typical input/output?"
2. Determine Domain and Location
Existing domains: meta, r-packages, bioconductor-how-tos
If uncertain, suggest the closest match. Convert purpose to kebab-case for the filename: "analyze R package" → analyze-r-package.
3. Outline the Process
Ask the user to walk through the steps. Capture major steps, key decisions, required inputs, expected outputs, and strategic code snippets (as guardrails). Help clarify and break down complex steps.
4. Generate the Skill File
Create a well-structured skill file following AGENTS.md and SKILL_STANDARD.md.
Do not duplicate SSOT guidelines; use references instead.
Fill in what's clear, use TODO markers for uncertainties, and prioritize clarity.
5. Review and Refine
Present a summary to the user, invite feedback ("Did I capture your intent correctly?"), and offer to iterate.
6. Validate the Skill
Before updating repository documentation, invoke validate-skill on the new file. Fix any CRITICAL issues. Only proceed to step 7 if validation passes.
7. Update Repository Documentation
Invoke document-skill by saying "Document the [skill-name] skill". It will automatically update SKILLS.md. Confirm completion with the user and suggest they test the skill.
Output Format
Generate a markdown file saved to skills/[skill-name]/SKILL.md. See SKILL_STANDARD.md for the required template and format.
Key Principles
- Skills are agent-agnostic: No platform-specific metadata in the file
- Describe what, not how: Use "read the file" not "use Read tool"
- Avoid duplication: Reference authoritative sources instead of copying content
Examples
Example 1: Creating from Scratch
User: "I want to make a skill that helps validate R package documentation"
Agent: Engages in Q&A to understand documentation aspects, timing, and actions.
Result: skills/validate-r-documentation/SKILL.md
Notes
- First draft doesn't need to be perfect—iteration expected
- Run
validate-skillbeforedocument-skill - Goal: lower the barrier to creating skills and sharing workflows
Related: See SKILL_STANDARD.md for technical format details. See AGENTS.md for how agent discovery works.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.