handy-skills
CLAUDE.md2 starsChanged 23 days agoApache-2.0View on GitHub
Office workflows, source understanding, and developer-facing productivity skills. Learning copies, downloaded repositories, process notes, raw outputs and generated eval workspaces belong outside the checkout, normally in a task-specific temporary directory. Delete them when no longer needed. Preserve runtime skills/**/references/ and maintained fixtures/examples. - Update the owning repository; keep sibling projects independent and link rather than copy their skills. - Keep localized pairs, declared source versions and catalog.yml consistent; the catalog is the public version record. English uses the base name…
In this repository13 other files it gives its agents.
- arbSkill
- bro-whatSkill
- debloatSkill
- fitSkill
- security-and-hardeningSkill
- source-briefSkill
- word-ahaSkill
- arb-cnSkill
- debloat-cnSkill
- fit-cnSkill
- principle-thin-wrapper-cnSkill
- source-brief-cnSkill
- word-aha-cnSkill
The file
We split this CLAUDE.md into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Update the owning repository.
- Very specific: line 30
Keep localized pairs, declared source versions and catalog.yml consistent.
- Very specific: line 34
Run ./tools/validate-all.sh for public package checks.
- Very specific: line 35
Run ./tools/validate-all.sh --local-qa only for available local QA.
- Distinctive: line 38
Commit and publish only within user authorization.
- Distinctive: line 40
Treat credentials, local installs and caches as local-only.
- Very specific: line 42
Keep qa/, docs/, analysis material and generated reports local.
≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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
handy-skills
Office workflows, source understanding, and developer-facing productivity skills.
Repository ownership
| Repository | Owns |
concept-skills | Software concepts, semantic modeling, knowledge organization, and visual learning. |
cloud-concept-skills | Huawei Cloud operations, billing, controlled provisioning, and account onboarding. |
handy-skills | Office workflows and source notes. |
Directory contract
| Directory | Contract |
skills/en/<name>/, skills/zh-CN/<name>-cn/ | Self-contained install payloads, including required references/, assets and runtime scripts. |
qa/ | Private local validation, fixtures and reports; ignored by Git and absent from public checkouts. |
catalog.yml | Tracked discovery metadata used by QA and publishing tools. |
docs/ | Concise local notes and examples; ignored by Git and never required by QA or distribution. |
tools/, .githooks/, .github/ | Repository tooling, local commit/push gates and CI. |
Learning copies, downloaded repositories, process notes, raw outputs and generated eval workspaces
belong outside the checkout, normally in a task-specific temporary directory. Delete them when no
longer needed. Preserve runtime skills/**/references/ and maintained fixtures/examples.
Change and release rules
- Update the owning repository; keep sibling projects independent and link rather than copy their skills.
- Keep localized pairs, declared source versions and
catalog.ymlconsistent; the catalog is the public version record. English uses the base name andlanguage: en; Chinese adds-cnandlanguage: zh-CN. Pairedtranslation_ofvalues name each other. Translate prose while preserving commands, safety gates and observable behavior. The repositoryVERSIONand per-skill catalog versions have separate scopes. - Run
./tools/validate-all.shfor public package checks; it must work withoutqa/. Run./tools/validate-all.sh --local-qaonly for available local QA; no behavioral or live-service result is implied by public checks. - Set
git config core.hooksPath .githooksonce per checkout. Ignore rules and commit/push/CI hygiene checks keep local-only files out of Git, including files added with force. - Commit and publish only within user authorization. ClawHub receives English payloads only; GitHub retains both languages. Verify remote contents before announcing a release.
- Treat credentials, local installs and caches as local-only. Keep only the current release notes; rewriting Git history or deleting remote releases requires explicit user authorization.
- Keep
qa/,docs/, analysis material and generated reports local; exclude them even when force-added.
Office-specific rules
- Preserve explicit-only invocation where declared. Update marketplace grouping and the README with changes to the bilingual pair; do not ship QA or development reports inside payloads.
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.

