agentleFS
Sign inStart free
fmindfmind/dot/skills/agent-project/SKILL.md

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

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
  1. Very specific:

    Create the shared layer and bridges: follow host-setup.md to start AGENTS.md from the project template, add .agents/skills/ and the ignored …

    line 20
  2. Very specific:

    Verify discovery: run dot agent context --check, read host-discovery.md for listing commands and native plugin catalogs, and distinguish …

    line 21
  3. Very specific:

    Install vendor skills deliberately: follow the shared vendor-skill policy for source review, project scope, versioning, replacement, and …

    line 22

≈ “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

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

  1. Inspect first: preserve existing AGENTS.md, host files, skills, and user settings; reuse a stack-specific instruction file when one exists.
  2. Create the shared layer and bridges: follow host-setup.md to start AGENTS.md from 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.
  3. 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.
  4. Install vendor skills deliberately: follow the shared vendor-skill policy for source review, project scope, versioning, replacement, and the current skills versus preview gh skill boundary. Select packages from each tool guide's Official Skills section and recheck the selected source before installation.
  5. 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 project CLAUDE.md or CLAUDE.local.md; Claude Code loads either instead of AGENTS.md.
  • Review repository configuration first: review a repository's hooks, MCP servers, skills, plugins, and custom-agent definitions before enabling them.

Documentation

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