From e2a6c498a4e62629a7a75483ace3f81c323f98db Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 27 Jan 2026 20:38:10 +0000 Subject: [PATCH] docs: clarify firstloop vs local skill creation workflow Add decision tree and quick reference table to manage-skills SKILL.md to help users understand whether to create a GitHub issue (for shared skills) or create directly in .claude/skills/ (for local project skills). Fixes #8 Co-authored-by: firstloop-jake --- plugins/core/skills/manage-skills/SKILL.md | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/plugins/core/skills/manage-skills/SKILL.md b/plugins/core/skills/manage-skills/SKILL.md index ae5a27b..ee28927 100644 --- a/plugins/core/skills/manage-skills/SKILL.md +++ b/plugins/core/skills/manage-skills/SKILL.md @@ -5,6 +5,31 @@ description: Create and improve Claude Skills with proper structure, frontmatter # Managing Claude Skills +## Before Creating a Skill + +### Where does this skill belong? + +**Firstloop shared skill** (default assumption): +- Skills for `core` or `monotemplate` plugins +- Improvements to existing shared skills +- → Create a GitHub issue in `firstloophq/claude-code-plugins` (see [meta-skill-management.md](meta-skill-management.md)) + +**Local project skill**: +- Project-specific workflows +- Custom skills for a single codebase +- User explicitly requests a "local skill" +- → Create directly in `.claude/skills//SKILL.md` + +### Quick Reference + +| Scenario | Action | +|----------|--------| +| "Create a skill for monotemplate" | GitHub issue | +| "Improve the crud skill" | GitHub issue | +| "Add a docker skill to the plugin" | GitHub issue | +| "Create a local skill for this project" | Create in `.claude/skills/` | +| "Add a skill just for this repo" | Create in `.claude/skills/` | + ## Creating Skills ### Quick Start