agentleFS
xmartlabsxmartlabs/agent-skills/CLAUDE.md

agent-skills

CLAUDE.md2 starsChanged 18 days agoMITView on GitHub

Public collection of AI tooling from Xmartlabs. Two kinds of thing live here: - skills/: standalone Agent Skills, installed with npx skills add. They share one test suite in tests/ (bash tests/run-all.sh, with tests/helper.sh), and a skill may ship a GitHub Action under actions/<name>/ that runs it in CI. - plugins/: Claude Code plugins, listed in .claude-plugin/marketplace.json (the xmartlabs marketplace). Each plugin keeps everything it needs, docs, tests and release tooling included, inside its own directory. Rules for the whole…

The file

We split this CLAUDE.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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Never push to main. Every change lands through a PR.

    line 15

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

CLAUDE.md

Public collection of AI tooling from Xmartlabs. Two kinds of thing live here:

  • skills/: standalone Agent Skills, installed with npx skills add. They share one test suite in tests/ (bash tests/run-all.sh, with tests/helper.sh), and a skill may ship a GitHub Action under actions/<name>/ that runs it in CI.
  • plugins/: Claude Code plugins, listed in .claude-plugin/marketplace.json (the xmartlabs marketplace). Each plugin keeps everything it needs, docs, tests and release tooling included, inside its own directory.

Rules for the whole repository:

  • Never push to main. Every change lands through a PR. Tags are the only refs pushed directly, and they are namespaced by tool (tribunal/v110, tribunal-rust-v0.1.3).
  • Everything is written in English.
  • This repository is public. No file may carry anything from a private codebase: no client names, people, domains, file paths, identifiers or commit ids, not in tests or comments either. Use neutral names (acme/web-app, user dev, src/widgets.ts); a real repository a check runs against comes from the operator, as a flag. Private test data stays outside the repository (/review-harness-data/ is ignored for that reason). Before merging anything ported from private work, run node scripts/check-private-data.mjs with the private checkouts it came from (see its header).

Keeping the tools independent:

  • A plugin lives in plugins/<name>/ and reads nothing outside it; shared code is copied, not imported. The skills are organised by their own team: they share tests/, and an action in actions/<name>/ may read its skill in skills/<name>/. An action for a plugin may read that plugin and the plugins it runs with (actions/tribunal/ reads plugins/tribunal/ and plugins/homosapiens/), and keeps its own tests in its directory.
  • Names are unique across the whole repository. npx skills add lists the skills in skills/ and the skills inside every plugin of the marketplace, so a plugin skill and a standalone skill cannot share a name.
  • A plugin skill that only works inside its plugin (it needs the plugin's agents, scripts or workflows) sets metadata: internal: true in its frontmatter, which hides it from npx skills add. review-pr does.
  • A workflow that belongs to one tool triggers only on that tool's paths (on.pull_request.paths). Do not make a path-filtered job a required status check: a PR that does not touch those paths never runs it and stays blocked.
  • Releases and tags carry the tool's name as prefix. A release that is not the newest stable version of anything should be a prerelease, so it does not become the repository's "latest" release. Installers download by exact tag, never by "latest".
  • Root-level config (.claude/settings.json hooks, .gitignore) is shared by everyone who works here, so each entry must act only on its own tool's paths, as the two tribunal hooks do.

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.