agentleFS
Sign inStart free
SerendipityOneIncSerendipityOneInc/ZooData-Skills/CLAUDE.md

ZooData-Skills

CLAUDE.md77 starsChanged 8 months agoMITView on GitHub

Before modifying or reviewing any skill, read and follow CONTRIBUTING.md, especially Skill Specification Ownership, then read the affected skill's SKILL.md and review its modules against the responsibility map declared there. Run the relevant consistency tests before completing the change. Skills are published to ClawHub manually via clawhub sync (the ClawHub key stays local — never in CI). A release is a repo-level milestone cut as a GitHub Release whose tag ends in -release (e.g. v1.2.3-release). This repo is public, so…

The file

We split this CLAUDE.md 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:

    Before modifying or reviewing any skill, read and follow CONTRIBUTING.md, especially Skill Specification Ownership, then read the affected …

    line 3
  2. Very specific:

    Keep this file as an instruction bridge.

    line 17
  3. Very specific:

    Follow docs/pr-description.md when writing or revising a PR description.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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 Code Repository Instructions

Before modifying or reviewing any skill, read and follow CONTRIBUTING.md, especially Skill Specification Ownership, then read the affected skill's SKILL.md and review its modules against the responsibility map declared there. Run the relevant consistency tests before completing the change.

Releasing / publishing

Skills are published to ClawHub manually via clawhub sync (the ClawHub key stays local — never in CI). A release is a repo-level milestone cut as a GitHub Release whose tag ends in -release (e.g. v1.2.3-release). This repo is public, so the Lark launch-tracking notification is run from hermes-workspace on this repo's behalf (no notification secrets live here). See docs/release-notify.md.

Keep this file as an instruction bridge. Do not copy skill-specific contracts, module policies, or runtime rules into it. Follow docs/pr-description.md when writing or revising a PR description.

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