skill-creation-guide
Guide the user through authoring a new agent skill — when a skill is worth creating, the SKILL.md format, progressive disclosure, and common pitfalls. Also covers discovering skill opportunities from the user's work patterns and generating a SKILL.md from a description. Trigger phrases include "create a skill", "write a skill", "make a skill", "new skill", "SKILL.md format", "how do skills work", "skill best practices", "convert this workflow into a skill", "what should I automate", and "find skill opportunities". Don't use it for invoking existing skills — only when authoring a new one or understanding the skill format.
Install
With your agent
Install OMGSkills skill "gleanwork/claude-plugins:skill-creation-guide" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gleanwork/claude-plugins /tmp/claude-plugins && ln -s /tmp/claude-plugins/plugins/glean/skills/skill-creation-guide ~/.claude/skills/skill-creation-guide
From README
Skill Creation Guide Help the user author effective agent skills — single SKILL.md files (in the open Agent Skills format) that auto-trigger by context and provide specialized guidance. The format is shared across hosts (Claude Code, Cursor, and others); only the location differs. This skill covers three things: deciding whether a skill is worth creating, discovering candidates from the user's work, and generating a well-formed skill. BE SKEPTICAL Not every idea makes a good skill. Evaluate before creating: Recurrence — Will this be used repeatedly? ✅ Weekly or more → create ⚠️ Monthly → reconsider, may not be worth it ❌ One-time → skip Automation — Can it actually be automated? ✅ Clear, repeatable process → create ⚠️ Needs significant judgment each time → reconsider ❌ Too context-dependent, each case unique → skip Value — Is the cumulative time saved significant? ✅ Meaningful savings per use → create ❌ Slower to invoke than doing manually → skip Duplication — Does it already exist?
More from this repo
catch-up
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a...
code-owners
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system,...
codebase-context
Gather architectural context about an internal system from code and documentation across the organization — use when...
