agentleFS
Sign inStart free
Catherine1401Catherine1401/agent-skills/skills/skill-creator-pj/SKILL.md

skill-creator-pj

Skill2 starsChanged 54 days agoMITView on GitHub

Create or update an agent skill scoped to a single project's own skill directory (.claude/skills or .codex/skills), not this repo's portable skills. Use for project-local skills; not portable skills, policies, plugins, or project implementation.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and apply ../skill-creator/SKILL.md.

    line 6
  2. Distinctive:

    Always write skill content in English, without exception.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
  • Read and apply ../skill-creator/SKILL.md; the project-specific constraints below override its location defaults.
  • Always write skill content in English, without exception.
  • Respect the user's chosen project-local location and preserve an existing skill's location. For new skills, default to .claude/skills/<name>/SKILL.md for Claude Code or .codex/skills/<name>/SKILL.md for Codex, inside the current project; do not use a user-level skill directory.
  • Validate the skill and run relevant project checks. Do not register the generated project skill in this repo's manifest.yaml, add distribution adapters, or run this repo's tests/test-install.sh for it; those apply only to this repo's portable skills.
  • Only .claude entries sync across machines, through the private projects checkout (~/agent-skills-projects, or AGS_PROJECTS_DIR); .codex/skills never syncs. When the target path is a symlink into that checkout, write through the link without replacing it. Never copy project skill content into this repo. Committing or pushing the projects checkout needs the user's approval.

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.

Check your setup, free