repo-skill-creator
Skill5 starsChanged 9 days agoMITView on GitHub
Create and maintain repository skills for adonis-skills. Use when users ask to scaffold a new skill under skills/, generate agents/openai.yaml, run skill validation, refresh web index data, or standardize the skill authoring workflow.
In this repository44 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-symlink-initSkill
- code-inspector-initSkill
- commitSkill
- copywritingSkill
- css-tailwind-stylingSkill
- lingui-best-practicesSkill
- lingui-workflowSkill
- weekly-reportSkill
- agent-dispatchSkill
- agentic-review-handoffSkill
- agent-practice-auditSkill
- agent-skill-evaluationSkill
- agent-symlink-initSkill
- architecture-hardening-loopSkill
- ardot-mcpSkill
- branch-creatorSkill
- chrome-dev-mcpSkill
- code-inspector-initSkill
- code-plugin-architectureSkill
- commit-pushSkill
- commitSkill
- decision-first-technical-writingSkill
- design-systemSkill
- desktop-agent-activitySkill
- dev-environment-roi-auditSkill
- disk-tidySkill
- figma-mcpSkill
- file-tidySkill
- goal-gateSkill
- grill-autopilotSkill
- kimi-computer-useSkill
- lingui-workflowSkill
- local-web-surfaceSkill
- open-code-review-loopSkill
- prompt-studioSkill
- review-prompt-composerSkill
- task-completion-loopSkill
- uxc-facadeSkill
- web-performance-auditSkill
- weekly-reportSkill
- workflow-gateSkill
- worktree-tidySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 11 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
Create and maintain repository skills with intent-specific workflows.
- Very specific: line 16
If the user provides a skills/* path and indicates the skill is already generated/copied, run path-finalize mode directly without …
- Distinctive: line 18
Run auto-discover finalize-and-stage only when the user explicitly asks to prepare newly added skills for commit or to stage them.
- Distinctive: line 64
Use for “check”, “audit”, “validate”, or a bare invocation without a requested creation/finalize action:
- Distinctive: line 70
When source changes already exist and generated index freshness is part of the check, also run:
- Very specific: line 77
Do not call skills:new, skills:finalize:new, or git add in this mode.
- Distinctive: line 81
Run only when the user explicitly asks to finalize and stage newly added skills:
- Very specific: line 91
only accept slugs where skills/<slug>/SKILL.md itself is in A or ??
- Distinctive: line 94
stop immediately on first failure
- Distinctive: line 98
If no new skill is discovered:
- Distinctive: line 100
do not create a skill unless the user also requested creation
- Very specific: line 104
Do not auto-run pnpm skills:openai-yaml unless explicitly requested.
- Very specific: line 105
Do not auto-run local install/sync (skills:install:local, skills:test:local) unless explicitly requested.
- Very specific: line 106
Do not stage in create, finalize-path, or validate mode.
- Distinctive: line 107
Do not use git add -A; only stage skill-related files from this workflow.
- Distinctive: line 111
When executing this skill, always return:
- Distinctive: line 120
Use lowercase hyphen-case skill names.
- Very specific: line 121
Keep SKILL.md frontmatter valid with non-empty name and description.
- Very specific: line 123
Add optional directories (scripts/, references/, assets/) only when needed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo Skill Creator
Create and maintain repository skills with intent-specific workflows. Validation is read-only with respect to Git state; creation, finalization, staging, and runtime installation are separate actions.
Trigger Rules
- Classify the request as
create,finalize-path,validate, orfinalize-and-stagebefore running a command. - If the user provides a
skills/*path and indicates the skill is already generated/copied, run path-finalize mode directly without additional confirmation. - A request to check, audit, or validate existing skills runs validation only. It must not create a skill or modify the Git index.
- Run auto-discover finalize-and-stage only when the user explicitly asks to prepare newly added skills for commit or to stage them.
- A bare invocation with no path or action defaults to validation. If exactly one new
skills/<slug>/SKILL.mdis discoverable, report it as the likely finalize target, but do not stage or create anything implicitly.
For normal create or finalize, first read the repository instructions, command definitions, and required arguments. When these establish the applicable entry point and no failure has occurred, use that entry point without routinely pre-reading the initializer, finalizer, validator, indexer, or YAML generator implementation. Read the relevant implementation on demand for an actual failure, command ambiguity, an output that conflicts with the documented contract, or maintenance of that tooling. This does not restrict necessary source or safety checks, target ownership checks, or verification of the real finalize pipeline and generated outputs.
Mode A: Create New Skill
Primary command (recommended):
pnpm skills:newManual creation commands:
pnpm skills:init <skill-name> --path skills --resources scripts,references
pnpm skills:finalize -- skills/<skill-name>Mode B: Finalize Existing Skill by Path
For the selected finalize-path action, run from the current repository root. Relative and absolute targets must resolve to a direct child of this repository's skills/ directory:
pnpm skills:finalize -- <skill-path>Examples:
pnpm skills:finalize -- skills/code-inspector-init
REPO_ROOT="$(git rev-parse --show-toplevel)"
pnpm skills:finalize -- "$REPO_ROOT/skills/code-inspector-init"Finalize pipeline is fixed and must run in order:
pnpm skills:quick-validate skills/<skill-slug>pnpm skills:validatepnpm skills:index
This mode does not stage files.
Mode C: Validate Existing Skills
Use for “check”, “audit”, “validate”, or a bare invocation without a requested creation/finalize action:
pnpm skills:validateWhen source changes already exist and generated index freshness is part of the check, also run:
pnpm skills:index
git diff --checkDo not call skills:new, skills:finalize:new, or git add in this mode.
Mode D: Auto Discover + Finalize + Stage
Run only when the user explicitly asks to finalize and stage newly added skills:
pnpm skills:finalize:newBehavior contract:
- Discover newly added skill candidates from
git status --short --untracked-files=all:- include
A(index-added) and??(untracked) - only accept slugs where
skills/<slug>/SKILL.mditself is inAor??
- include
- Finalize each discovered slug in stable sorted order:
pnpm skills:finalize -- skills/<slug>- stop immediately on first failure
- Stage only related files after all finalize runs succeed:
git add skills/<slug>for each processed sluggit add apps/web/src/generated/skills-index-lite.json apps/web/src/generated/skills-detail-index.jsonfor whichever generated index files changed
- If no new skill is discovered:
- report that no new skill was found
- do not create a skill unless the user also requested creation
Scope Boundaries
- Do not auto-run
pnpm skills:openai-yamlunless explicitly requested. - Do not auto-run local install/sync (
skills:install:local,skills:test:local) unless explicitly requested. - Do not stage in create, finalize-path, or validate mode. Staging requires an explicit
finalize-and-stage/commit-preparation request. - Do not use
git add -A; only stage skill-related files from this workflow.
Output Contract
When executing this skill, always return:
- Commands executed (or planned commands in dry-run).
- Success/failure status.
- Detected/processed skill slugs and staged file paths, with
nonewhen the selected mode does not stage. - Next-step suggestion only when useful (for example, local agent testing via
pnpm skills:test:local).
Skill Rules
- Use lowercase hyphen-case skill names.
- Keep
SKILL.mdfrontmatter valid with non-emptynameanddescription. frontmatter.descriptionmust be English-only (ASCII characters only), and should clearly include when to use the skill.- Add optional directories (
scripts/,references/,assets/) only when needed. - Re-run validation and index generation after updates and before commit.
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
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.

