Agent skill · Documentation

create-skill

Turn a repeatable AI prompt or workflow into a structured, shareable skill for the affiliate-skills GitHub repository. Use this skill when the user wants to create a new skill, write a SKILL.md, convert a prompt to a skill, share a skill via the GitHub repo, or document an AI workflow. Also trigger for: "create a skill", "write a skill", "make this a skill", "turn this into a skill", "publish skill", "add skill to list", "write SKILL.md", "skill from prompt", "document this workflow", "package this as a skill".

Affitorgithub.com/AffitorGitHub ↗
claude-codecursorMIT
Install
npx skills add Affitor/affiliate-skills --skill create-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 17 KB
Bundled scripts: none
Version: 1.0.0
Declared author: affitor
Requires: Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
Path: skills/meta/create-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 586
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# List Affitor Skill Turn a repeatable AI prompt or workflow into a structured, shareable skill for the [affiliate-skills GitHub repository](https://github.com/Affitor/affiliate-skills). The output is a complete SKILL.md file that works in any AI agent — shared via `npx skills add Affitor/affiliate-skills` so anyone can install it. ## Stage This skill belongs to Stage S8: Meta ## When to Use - User has a prompt they keep reusing and wants to turn it into a shareable skill - User wants to create a new skill for the affiliate-skills repository - User wants to write a SKILL.md file in the standard format - User says "make this a skill" or "write a skill for X" - User wants to package an AI workflow so others can replicate it ## Input Schema ``` { raw_prompt: string # (required) The prompt, workflow description, or detailed explanation of what the skill does failure_modes: string # (optional) What goes wrong when the output is bad — helps write better Instructions and Error Handling niche: string # (optional) Category hint, e.g., "content", "research", "seo" examples: string # (optional) Example input/output pairs the user already has } ``` ## Workflow ### Step 1: Understand What the P

What's inside
Steps it walks through
  1. Stage
  2. When to Use
  3. Input Schema
  4. Workflow
  5. Step 1: Understand What the Prompt Actually Does
  6. Step 2: Determine Skill Metadata
  7. Step 3: Write the SKILL.md
  8. Step 4: Write the README Description
  9. Step 5: Assemble Output
  10. Step 6: Self-Validation
  11. Output Schema
  12. Output Format
  13. Output 1: SKILL.md File
  14. Output 2: README / Registry Description
More from affiliate-skills
All skills →
About this skill
What does the create-skill skill do?

Turn a repeatable AI prompt or workflow into a structured, shareable skill for the affiliate-skills GitHub repository. Use this skill when the user wants to create a new skill, write a SKILL.md, convert a prompt to a skill, share a skill via the GitHub repo, or document an AI workflow. Also trigger for: "create a skill", "write a skill", "make this a skill", "turn this into a skill", "publish skill", "add skill to list", "write SKILL.md", "skill from prompt", "document this workflow", "package this as a skill".

How do I install it?

Run `npx skills add Affitor/affiliate-skills --skill create-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Affitor/affiliate-skills, a repository with 586 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going