sharable-artifact
Skill6 starsChanged 3 months agoNo licenceView on GitHub
Build or revise a page a team reads on its own — a design preview, a status board, a reference on a format or a subsystem — as one self-contained HTML file published to a stable URL and republished in place. Use when asked to "write this up as a page", "make a design page", "publish a status board", "put the reference somewhere the team can read it", or when a write-up exists only in chat or in a file nobody will open. Beta — the conventions come from a handful of pages in one team; record friction through `engineering-journal`. Symptoms that this skill applies: a page whose sections renumber by hand, a figure cited as "below", a status row that says "fixed" when only the author says so, a number with no revision it was taken on, a figure whose labels overflow in the render, or a page that is white on white in dark mode.
In this repository26 other files it gives its agents.
- document-featureSkill
- recommend-skillsSkill
- seed-skill-templateSkill
- architecture-diagramSkill
- catchupSkill
- dataflow-diagramSkill
- engineering-journalSkill
- format-layout-diagramSkill
- review-exchangeSkill
- review-guideSkill
- rust-source-layoutSkill
- sweep-commentsSkill
- technical-proseSkill
- close-arcSkill
- define-scopeSkill
- discussSkill
- frame-problemSkill
- open-arcSkill
- open-inquirySkill
- plan-featureSkill
- propose-designSkill
- reconcile-vaultSkill
- record-decisionSkill
- submit-explorationSkill
- synthesizeSkill
- vault-searchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. About 0 are common, 22 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
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.