agentleFS
Sign inStart free
ccoalmccoalm/ccl-skills/packages/AGENTS.md

ccl-skills / packages

AGENTS.md6 starsChanged 3 months agoApache-2.0View on GitHub

packages/ holds everything this repository ships to other machines: the unified npm distribution (ccl-skills-npm) and the standalone OpenCode plugin source (opencode-plugin). The boundary is distributable, not npm package — a subdirectory belongs here when its content is copied or published to a host outside this checkout. - Do not put host-convention directories here. .claude-plugin/, .codex-plugin/, .opencode/ and opencode.json stay at the repository root because their location is pinned by the host, not by us. - This is not an npm…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Do not put host-convention directories here.

    line 11

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

packages Agent Contract

packages/ holds everything this repository ships to other machines: the unified npm distribution (ccl-skills-npm) and the standalone OpenCode plugin source (opencode-plugin). The boundary is distributable, not npm package — a subdirectory belongs here when its content is copied or published to a host outside this checkout.

Rules:

  • Do not put host-convention directories here. .claude-plugin/, .codex-plugin/, .opencode/ and opencode.json stay at the repository root because their location is pinned by the host, not by us.
  • This is not an npm workspace. The repository root has no package.json and no workspaces field; a non-package subdirectory here breaks no build.
  • Build steps copy source assets out of the repository. When a source path moves, update the copying script in the same change — a stale source path fails the build, but a stale destination name silently ships the wrong layout.
  • Installed artifact names are a separate contract from repository paths. agent-context/session-start.md ships as bootstrap.md on purpose: uninstall manifests and the installed plugin runtime key on that name.

Validation:

  • make npm-test, make npm-pack-verify, make npm-publish-dry
  • bash skills/skill-extraction-workflow/scripts/check-ccl-skills.sh .

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