claude-software-3-0-marketplace / site
CLAUDE.md2 starsChanged 5 months agoMITView on GitHub
site/ is a generated projection of .claude-plugin/marketplace.json, produced by .claude/skills/add-plugin/scripts/sync-site.sh. It is never hand-edited. Byte-equality between the committed site/ and what the generator would produce today is enforced by tests/gates/18-pages-in-sync.sh. The gate runs on every push/PR via ci.yml. Published verbatim (no in-CI regeneration) to GitHub Pages by .github/workflows/pages.yml. sync-site.sh uses a pinned SITE_BUILD_DATE constant (never date) to keep the generator deterministic for byte-equality checks. The operator bumps it when re-publishing after content changes.
In this repository11 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude-plugin/CLAUDE.mdCLAUDE.md
- .claude/teams/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- add-pluginSkill
- list-pluginsSkill
- remove-pluginSkill
- update-pluginSkill
- vet-pluginSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Verify: bash tests/gates/run-all.sh (G18 must pass)
- Very specific: line 16
Commit both the manifest change and the updated site/ files together.
≈ “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.
Files
site/ — generated projection
site/ is a generated projection of .claude-plugin/marketplace.json, produced by
.claude/skills/add-plugin/scripts/sync-site.sh. It is never hand-edited.
Byte-equality between the committed site/ and what the generator would produce today is enforced by
tests/gates/18-pages-in-sync.sh. The gate runs on every push/PR via ci.yml.
Published verbatim (no in-CI regeneration) to GitHub Pages by .github/workflows/pages.yml.
How to update the site
- Edit the manifest (
.claude-plugin/marketplace.json) or the generator (sync-site.sh). - Regenerate:
bash .claude/skills/add-plugin/scripts/sync-site.sh - Verify:
bash tests/gates/run-all.sh(G18 must pass) - Commit both the manifest change and the updated
site/files together.
Contents
| File | Role |
index.html | Landing page — one card per plugin (or empty-state) |
sitemap.xml | Single-URL sitemap for the canonical root |
robots.txt | Allows all crawlers; points to sitemap |
assets/favicon.svg | Static brand mark (committed; not regenerated by the generator) |
Pinned build date
sync-site.sh uses a pinned SITE_BUILD_DATE constant (never date) to keep the generator
deterministic for byte-equality checks. The operator bumps it when re-publishing after content changes.
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
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.

