shaping-work SKILL.md skillA
shaping-work from teambrilliant/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add teambrilliant/dev-skills/shaping-work@git:20261008.81e7416Pins git:20261008.81e7416 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- teambrilliant/dev-skills
- Path
skills/shaping-work/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261008.81e7416, committed Oct 8, 2026
- First version recorded
- Jul 7, 2026
- Size
- 19,209 bytes
- Repository stars
- 5
- License
- none declared
Shape rough ideas into clear, actionable work definitions. Use this skill whenever someone has an unstructured idea that needs to become a concrete work definition — feature requests, bug reports, PRDs, customer feedback, Slack threads, stakeholder asks, or vague "we should do X" statements. Trigger phrases include "shape this", "scope this", "write a PRD", "define this work", "turn this into a ticket", "flesh this out", "spec this out", "what should we build for X", "I have an idea for...…
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
# Shaping Work Shape ambiguous ideas into clear work definitions. Focus on clarity, not process theater. ## Principles - **No jargon** — write so anyone can understand - **Product-focused** — define *what*, not *how* to build it - **Right level of detail** — enough to act on, not a specification - **Flag unknowns with recommendations** — surface risks early, but always propose a resolution ## Process 1. **Understand the request** — Read the input (could be anything: a Slack thread, a rough idea, a customer complaint, a formal PRD, or a handoff from product-thinker). If intent is unclear, ask up to 3 targeted questions, then shape with stated assumptions. 2. **Understand the context** — If handed off from product-thinker, use the product context and analysis already gathered (don't re-explore). Otherwise, if working in a codebase, read `.tap/product.md` if it exists (current focus, bets, non-goals — what this work has to ladder up to), then CLAUDE.md or similar to understand what the application does (the product, not technical details). Also look for related context the request didn't mention: existing docs on the topic in `thoughts/shapes/`, `thoughts/plans/`… …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kxefjqowkvmnbcbe/4997058da90916beb4dbfa402efd24381fbc9833c7bb676d4285ba41f5222880.json
Then /plugin install shaping-work@markdownregistry-kxefjqowkvmnbcbe in Claude Code. It installs git:20261008.81e7416, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add teambrilliant/dev-skills/shaping-work@sha256:4997058da90916beThe line at the top of this page pins the label git:20261008.81e7416, 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.
[](https://markdownregistry.com/a/art_kxefjqowkvmnbcbe)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in teambrilliant/dev-skills/shaping-work since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of shaping-work from somewhere else? Ask it: where did my shaping-work come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 7 versions of this file, between Jul 7, 2026 and Oct 8, 2026, about one every 15 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.81e7416 latest | 2026-10-08 | 81e7416 | 19,209 B | A | view · diff |
| git:20261008.8e403b1 | 2026-10-08 | 8e403b1 | 19,419 B | A | view · diff |
| git:20260927.b9558d0 | 2026-09-27 | b9558d0 | 19,354 B | A | view · diff |
| git:20260807.eadd958 | 2026-08-07 | eadd958 | 17,233 B | A | view · diff |
| git:20260713.f906cdf | 2026-07-13 | f906cdf | 15,340 B | A | view · diff |
| git:20260711.4b8d7f9 | 2026-07-11 | 4b8d7f9 | 15,203 B | A | view · diff |
| git:20260707.e955c58 | 2026-07-07 | e955c58 | 13,253 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/shaping-work/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (19209 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
teambrilliant/dev-skills · 5 stars · license none declared · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kxefjqowkvmnbcbe GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/shaping-work GET https://markdownregistry.com/api/v1/blob/4997058da90916beb4dbfa402efd24381fbc9833c7bb676d4285ba41f5222880
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.