A tiny example skill. Use when you want to see how skill loading (progressive disclosure) works end to end.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Hello World Skill
This is the skill body. When the model calls the `skill` tool with
`{ "name": "hello-world" }`, everything below the frontmatter is injected into the
conversation, along with a sampled list of files in this directory.
## Steps
1. Read `scripts/greet.sh` in this skill's base directory.
2. Run it with the user's name.
3. Report the greeting back.
Relative paths (like `scripts/greet.sh`) are resolved against the base directory
printed in the tool output.
The line at the top of this page pins the label git:20260625.7a0333d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_4su2o3xt42f3r5wi
GET https://markdownregistry.com/api/v1/resolve?ref=muthuishere/toolnexus/hello-world
GET https://markdownregistry.com/api/v1/blob/993feea49f5ffb77c188526bc6a551c2180a8c688c1d9d354e4807e4dc51e409
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
muthuishere/toolnexus · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
muthuishere/toolnexus · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
muthuishere/toolnexus · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
muthuishere/toolnexus · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
muthuishere/toolnexus · .claude/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
muthuishere/toolnexus · .claude/skills/release/SKILL.md · Cut and verify a toolnexus release across all eight registries, with the guardrails that a green CI run does not give…
muthuishere/toolnexus · clojure/examples/clj-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
muthuishere/toolnexus · clojure/examples/cljgo-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
dcc-mcp/dcc-mcp-core · examples/remote-server/skills/hello-world/SKILL.md · Example skill - minimal greeting tool. Use only for testing standalone internal service connectivity and Skill…
dcc-mcp/dcc-mcp-core · examples/skills/hello-world/SKILL.md · Example skill — minimal greeting tool demonstrating the dcc-mcp-core skill system. Use only when testing a new skill…
anton-abyzov/vskill · test/verify/fixtures/tiny-skill-source/plugins/tiny-test-plugin/skills/hello-world/SKILL.md · A tiny test skill used by the 0853 verify-runtime harness. Says hello. No external calls. Use when the user asks for a…
