agentleFS
zjp1997720zjp1997720/zhijian-skills/AGENTS.md

zhijian-skills

AGENTS.md787 starsChanged 4 months agoMITView on GitHub

This repository is the only editable source for the public Zhijian Skills portfolio. Before committing a Skill change: The Registry is the single machine-readable source for Skill paths, versions, validation, capabilities, Harness support, and documentation. Mirror metadata is forbidden.

The file

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

10 rules. About 1 is common, 7 are distinctive, and 2 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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:

    Treat main as a protected integration branch.

    line 7
  2. Very specific:

    Before publishing, record and re-check the live remote SHA.

    line 8
  3. Distinctive:

    Do not create or update standalone Skill repositories.

    line 12
  4. Common:

    Never publish credentials, personal absolute paths, customer data, caches, generated previews, reports, browser profiles, or dependency …

    line 16
  5. Distinctive:

    Never force-push or rewrite published Portfolio history or Tags.

    line 20
  6. Distinctive:

    Before committing a Skill change:

    line 24
  7. Distinctive:

    Run the repository-owned Skill validator.

    line 26
  8. Distinctive:

    Run that Skill's declared deterministic tests.

    line 27
  9. Distinctive:

    Run its isolated install check.

    line 28
  10. Distinctive:

    Run Portfolio contract tests when Registry or governance code changes.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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

Zhijian Skills Repository Instructions

Repository role

This repository is the only editable source for the public Zhijian Skills portfolio.

  • Treat main as a protected integration branch. Start each task from the live origin/main SHA on a short-lived branch, push only that branch, and merge through a PR.
  • Before publishing, record and re-check the live remote SHA. A .git/zhijian-needs-sync.json marker blocks commits, pulls, and pushes until the checkout is clean and exactly synchronized to origin/main.
  • skills/<name>/ is the install payload and must remain self-contained.
  • Human documentation lives in docs/skills/<name>/.
  • Per-Skill release notes live in docs/changelogs/<name>.md.
  • Do not create or update standalone Skill repositories. Every public Skill is released only from this Portfolio.

Safety

  • Never publish credentials, personal absolute paths, customer data, caches, generated previews, reports, browser profiles, or dependency directories.
  • Candidate Skill code runs without release credentials.
  • Release and repository-admin credentials stay separate.
  • Unknown source drift blocks the affected Skill.
  • Never force-push or rewrite published Portfolio history or Tags.

Verification

Before committing a Skill change:

  1. Run the repository-owned Skill validator.
  2. Run that Skill's declared deterministic tests.
  3. Run its isolated install check.
  4. Run Portfolio contract tests when Registry or governance code changes.

The Registry is the single machine-readable source for Skill paths, versions, validation, capabilities, Harness support, and documentation. Mirror metadata is forbidden.

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.