agentille-project
Skill1 starsChanged 20 days agoMITView on GitHub
Register the current repo with agentille and write its ./CLAUDE.md. Asks 7 short per-repo questions, appends the project to ~/.agentille/profile.json's projects[] and renders a per-repo CLAUDE.md using your voice settings. Optional; /agt works without it. Runs only when the user types /agentille-project; model invocation is disabled.
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- agentille-claude-mdSkill
- agentille-initSkill
- agtSkill
- stormSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run inside a repo to register it and seed its ./CLAUDE.md.
- Very specific: line 13
Profile: If ~/.agentille/profile.json is absent, continue with {} (voice lines are then omitted from the CLAUDE.md).
- Very specific: line 14
Existing
./CLAUDE.md: If present, ask: keep it or overwrite? - Distinctive: line 36
Never overwrite a file without explicit confirmation.
- Distinctive: line 37
Never change the profile's voice settings.
≈ “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.
Files
agentille-project — per-repo registration
Run inside a repo to register it and seed its ./CLAUDE.md. Never auto-trigger.
Steps
- Profile. If
~/.agentille/profile.jsonis absent, continue with{}(voice lines are then omitted from the CLAUDE.md). If it exists but is not valid JSON, stop and tell the user. - Existing
./CLAUDE.md. If present, ask: keep it or overwrite? Skip the render on keep (still register the project). Never overwrite without an explicit yes. - Ask once, in one message, each with a default:
- name (directory basename)
- description (one line)
- techStack (free-form list; offer what you detect from the repo)
- goals
- claudeUse — how Claude is used here
- constraints — rules Claude must respect
- integration — where finished work lands:
pr(open a PR),push(push my feature branch, no merge),local(no remote)
Register. Read-merge-write
~/.agentille/profile.json: append toprojects[], or replace the entry with the sameurlorpath(else the sameid). Touch nothing else in the file.urlis theoriginremote (git remote get-url origin, omit the key when there is none) andpaththe repo root: the mod's Bash guard looks a run's integration mode up by the repo a command targets, matched onurlorpath; an entry with only anidcounts for a repo with no remote and can only lower the mode.{ "id": "<slug>", "url": "<origin remote URL>", "path": "<repo root>", "name": "", "description": "", "techStack": [], "goals": "", "claudeUse": "", "constraints": "", "integration": "pr | push | local" }Slug: lowercase, non-alphanumeric to
-, trimmed; empty →project-<random>.- Render
./CLAUDE.mdfromclaude-md-template.md, pullingname,deliveryStyle,tone,neverDofrom the profile. - Write
./.agentille/config.jsonas{ "integration": "<chosen>" }(repo-local; it can only lower the mode your profile sets, never raise it:autocomes from the profile alone). Print the three paths and suggest adding.agentille/to.gitignoreif it should not be committed.
Hard rules
- Never overwrite a file without explicit confirmation.
- Never change the profile's voice settings; this skill is project-scoped.
- Never commit
~/.agentille/profile.json.
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.

