agent-project
Skill13 starsChanged 4 days agoMITView on GitHub
Set up repo AGENTS.md, shared skills/agents, host bridges, discovery, and vendor skills.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- fmind/dotword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- fmind/dot★ 13100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dot_agents/AGENTS.mdAGENTS.md
- skills/repository-docs/references/agents.mdAGENTS.md
- chezmoiSkill
- dot-developmentSkill
- dot-releaseSkill
- dot-skillsSkill
- dot-verifySkill
- acliSkill
- agent-evaluationSkill
- agent-frameworksSkill
- agent-harnessesSkill
- agent-protocolsSkill
- agySkill
- airflowSkill
- auth-statusSkill
- awsSkill
- bfSkill
- chrome-devtoolsSkill
- clipboardSkill
- cloud-runSkill
- code-securitySkill
- colabSkill
- databricksSkill
- diagrams-as-codeSkill
- dockerSkill
- documentation-siteSkill
- dot-cliSkill
- dprintSkill
- draft-docSkill
- draft-mailSkill
- duckdbSkill
- fmind-visualsSkill
- full-reviewSkill
- gcloudSkill
- ghSkill
- git-deliverySkill
- github-actionsSkill
- github-issuesSkill
- github-pull-requestSkill
- github-repositorySkill
- google-developerSkill
- gwsSkill
- hfSkill
- infra-as-codeSkill
- kaggleSkill
- kubernetesSkill
- lesson-learnedSkill
- mcp-setupSkill
- miseSkill
- model-providersSkill
- playwrightSkill
- project-scaffoldingSkill
- python-mlopsSkill
- python-stackSkill
- python-webSkill
- repository-docsSkill
- scheduled-jobsSkill
- skillifySkill
- <name>Skill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 20
Create the shared layer and bridges: follow host-setup.md to start AGENTS.md from the project template, add .agents/skills/ and the ignored …
- Very specific: line 21
Verify discovery: run dot agent context --check, read host-discovery.md for listing commands and native plugin catalogs, and distinguish …
- Very specific: line 22
Install vendor skills deliberately: follow the shared vendor-skill policy for source review, project scope, versioning, replacement, and …
≈ “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
Set Up Agents on a Project
Author the shared project instruction and skill layer once, then add only required host bridges. repository-docs owns instruction content; mcp-setup owns MCP configuration.
Workflow
- Inspect first: preserve existing AGENTS.md, host files, skills, and user settings; reuse a stack-specific instruction file when one exists.
- Create the shared layer and bridges: follow host-setup.md to start
AGENTS.mdfrom the project template, add.agents/skills/and the ignored.agents/prompts/inbox for task-prompts, then add the Claude Code skills link, optional configuration, and native custom-agent locations only for hosts the repository is used with. - Verify discovery: run
dot agent context --check, read host-discovery.md for listing commands and native plugin catalogs, and distinguish presence from demonstrated instruction following. - Install vendor skills deliberately: follow the shared vendor-skill policy for source review, project scope, versioning, replacement, and the current
skillsversus previewgh skillboundary. Select packages from each tool guide's Official Skills section and recheck the selected source before installation. - Keep current: route repository changes through repository-docs, including project-local skill references.
Task guides
<!-- guides:start -->- cross-harness-agents: Decide when a custom agent role pays off, write native definitions per host, and verify discovery.
<!-- guides:end -->Gotchas
- Keep one rule body: shared rules live in
AGENTS.md; never add a projectCLAUDE.mdorCLAUDE.local.md; Claude Code loads either instead ofAGENTS.md. - Review repository configuration first: review a repository's hooks, MCP servers, skills, plugins, and custom-agent definitions before enabling them.
Documentation
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.