agentleFS
CarbeneAICarbeneAI/Forge/.claude/skills/Createskill/SKILL.md

Createskill

Skill9 starsChanged 6 months agoMITView on GitHub

MANDATORY skill creation framework for ALL skill creation requests. USE WHEN user wants to create, validate, update, or canonicalize a skill, OR user mentions skill creation, skill development, new skill, build skill, OR user references skill compliance, skill structure, or skill architecture.

Files
SKILL.md

Createskill

MANDATORY skill creation framework for ALL skill creation requests.

Authoritative Source

Before creating ANY skill, READ: ${PAI_DIR}/skills/CORE/SkillSystem.md

Canonical example to follow: ${PAI_DIR}/skills/Blogging/SKILL.md

TitleCase Naming Convention

All naming must use TitleCase (PascalCase).

ComponentFormatExample
Skill directoryTitleCaseBlogging, Daemon, CreateSkill
Workflow filesTitleCase.mdCreate.md, UpdateDaemonInfo.md
Reference docsTitleCase.mdStyleGuide.md, ApiReference.md
Tool filesTitleCase.tsManageServer.ts
Help filesTitleCase.help.mdManageServer.help.md

Wrong (NEVER use):

  • createskill, create-skill, CREATE_SKILL
  • create.md, update-info.md, SYNC_REPO.md

Workflow Routing

When executing a workflow, output this notification directly:

Running the **WorkflowName** workflow from the **Createskill** skill...
WorkflowTriggerFile
CreateSkill"create a new skill"workflows/CreateSkill.md
ValidateSkill"validate skill", "check skill"workflows/ValidateSkill.md
UpdateSkill"update skill", "add workflow"workflows/UpdateSkill.md
CanonicalizeSkill"canonicalize", "fix skill structure"workflows/CanonicalizeSkill.md

Examples

Example 1: Create a new skill from scratch

User: "Create a skill for managing my recipes"
→ Invokes CreateSkill workflow
→ Reads SkillSystem.md for structure requirements
→ Creates skill directory with TitleCase naming
→ Creates SKILL.md, workflows/, tools/
→ Generates USE WHEN triggers based on intent

Example 2: Fix an existing skill that's not routing properly

User: "The research skill isn't triggering - validate it"
→ Invokes ValidateSkill workflow
→ Checks SKILL.md against canonical format
→ Verifies TitleCase naming throughout
→ Verifies USE WHEN triggers are intent-based
→ Reports compliance issues with fixes

Example 3: Canonicalize a skill with old naming

User: "Canonicalize the daemon skill"
→ Invokes CanonicalizeSkill workflow
→ Renames workflow files to TitleCase
→ Updates routing table to match
→ Ensures Examples section exists
→ Verifies all checklist items

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.