skill-creation
Create, improve, and manage Droid skills. Use when the user wants to: - Create new skills from scratch or from session learnings - Improve existing skills based on user preferences - Analyze sessions to identify patterns worth codifying - Understand best practices for agentic skill design This is a meta-skill for self-improvement and continuous learning.
- Installs
- 135
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/factory-ai/factory-plugins --skill skill-creation- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads skill-creation automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Skill creation
This skill helps you build new skills and improve existing ones. Think of it as the skill that teaches you how to learn.
Why bother with skills?
Every time you solve a problem, that knowledge usually dies with the session. Skills fix that. They're how you turn "I figured this out once" into "I know how to do this."
A few reasons to extract skills:
- You won't have to re-discover the same solution next month
- Other sessions (and other users) benefit from what you learned
- Complex workflows become repeatable instead of fragile
The basic format
Skills live in a folder with a SKILL.md file:
.factory/skills/my-skill/
└── SKILL.md
The file has YAML frontmatter and markdown content:
---
name: my-skill
version: 1.0.0
description: |
What this skill does.
When to use it.
---
# My skill
Instructions go here.
The description matters a lot. It's how the agent decides whether to load your skill for a given task. Be specific about the problems it solves.
When to create a skill
Not everything deserves to be a skill. Skills are for complex or long workflows that someone might need to repeat or share. If it's a simple one-off task, a skill is overkill.
The right level of specificity matters. A skill for "debugging in a codebase" is useful if there's a lot of common failure modes that agents might encounter. A skill for "debugging the login flow" is probably too narrow. Find the balance between general enough to reuse and specific enough to be helpful.
Ask yourself:
- Did I have to dig around to figure this out?
- Would I be annoyed if I had to solve this again from scratch?
- Is there something here that isn't obvious from the docs?
If yes to any of those, probably worth extracting. If it was straightforward or you just followed a tutorial, skip it.
Skills can also encode preferences and best practices. Maybe a user always logs into a specific platform when doing data analysis. Maybe there's a gotcha the team keeps hitting. If you notice you're consistently doing something the user has to correct or adjust, that's worth including.
Extracting skills from sessions
Use the session-navigation skill to dig through past sessions and find patterns worth extracting. Look for things that came up multiple times, solutions that took real effort to figure out, or workflows you keep repeating.
Once you've found something, generalize it. Replace specific paths with patterns, note the prerequisites, call out assumptions. The skill should work for similar situations, not just the exact case you found.
Skill design tips
When writing the skill, use the human-writing skill. Skill docs that read like marketing copy are harder to follow.
Start small. A skill that does one thing well beats a skill that tries to cover everything. You can always compose multiple skills together.
Include verification. How do you know the skill worked? Add a check at the end:
## Verify it worked
Run `npm test` and make sure nothing broke.
Check that the new file exists at `src/config.ts`.
Document the failures too. What doesn't work? What should you avoid? This saves future pain:
## What not to do
Don't run this on a dirty git working directory.
The `--force` flag will overwrite without asking.
Keep it fresh. Skills rot. Dependencies change, APIs update, better approaches emerge. If a skill stops working or feels outdated, update it or delete it.
Where skills live
| Location | Who sees it |
|---|---|
.factory/skills/ | Everyone on the project (commit it to git) |
~/.factory/skills/ | Just you, across all projects |
Project skills are good for team conventions. Personal skills are good for your own workflows.
Improving existing skills
Signs a skill needs work:
- Users ask follow-up questions after it runs
- It fails on edge cases that keep coming up
- There's a better approach now than when it was written
To find patterns:
# Which sessions used this skill?
rg -l "skill-name" ~/.factory/sessions/*.jsonl
# Where did things go wrong?
rg "error|failed|retry" ~/.factory/sessions/*.jsonl -C 3
When you update a skill, bump the version. If it's a breaking change (different output, different inputs), bump the major version.
Research notes
Some of this comes from academic work on agents that learn:
Voyager showed that agents can build up skill libraries over time, with each skill composed from simpler ones.
CASCADE demonstrated that skills can be shared between agents, not just stored for one agent's use.
SEAgent found that learning from failures is as valuable as learning from successes.
Reflexion showed that verbal feedback (explaining what went wrong in plain language) beats numeric scores for improving agent behavior.
The loop
- Work on something
- Notice when you learn something non-obvious
- Extract it as a skill
- Use the skill next time
- Improve the skill based on how it goes
- Repeat
FAQ
What does the skill-creation skill do?
Create, improve, and manage Droid skills. Use when the user wants to: - Create new skills from scratch or from session learnings - Improve existing skills based on user preferences - Analyze sessions to identify patterns worth codifying - Understand best practices for agentic skill design This is a meta-skill for self-improvement and continuous learning.
How do I install skill-creation?
Run npx skills add https://github.com/factory-ai/factory-plugins --skill skill-creation in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/skill-creation/ (personal) or .claude/skills/skill-creation/ (project).
Which AI agents can use skill-creation?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is skill-creation safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains skill-creation?
It is published by factory-ai in factory-ai/factory-plugins, and it is an official skill from the maker of the technology it covers. It has 135 recorded installs.
More from factory-ai/factory-plugins
no-use-effect
factory-ai/factory-plugins
Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs with useEffect, or when an agent adds useEffect "just in case." Provides the five replacement patterns and the useMountEffect escape hatch.
human-writing
factory-ai/factory-plugins
Remove signs of AI-generated writing from text to make it sound more natural and human-written. Use when editing or reviewing any form of document including: markdown, technical docs, emails, blog posts, PRDs, or any dedicated writing content. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
simplify
factory-ai/factory-plugins
Review changed code for reuse, quality, and efficiency, then fix any issues found.
frontend-design
factory-ai/factory-plugins
Open the skill to read its SKILL.md instructions.
visual-design
factory-ai/factory-plugins
Image generation and presentations. Use when: - User asks for images: logos, icons, app assets, diagrams, flowcharts, architecture diagrams, patterns, textures, photo edits, restorations - User needs a presentation or slide deck Covers nanobanana CLI for image generation and Slidev for presentations.
security-review
factory-ai/factory-plugins
Open the skill to read its SKILL.md instructions.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available