workshop-craft SKILL.md skillA
workshop-craft from frolad/tars is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add frolad/tars/workshop-craft@git:20261104.96c9a51Pins git:20261104.96c9a51 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- frolad/tars
- Path
skills/workshop-craft/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261104.96c9a51, committed Nov 4, 2026
- Size
- 11,364 bytes
- Repository stars
- 3
- License
- MIT
Define a complex task with the user and write its blueprint, the split into pipelines and iterations, for workshop-forge to build from.
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
sttp and sttp-software-engineering apply. workshop-craft is the definition stage of a large task. It does the recon, grills the user, and writes the task's blueprint, under `.blueprints/<slug>/` in a git repository: the scope, the knowledge, the blockers, the split into pipelines and categories, and planned iterations. workshop-forge then builds from it, one reviewed iteration at a time. workshop-craft is not a full spec and not a full plan. workshop-forge always follows it, so the user stays in the loop and the plan emerges while workshop-forge runs. The blueprint holds what workshop-forge needs to start: no user stories, no full list of iterations up front, no interface contracts beyond the one handover line of a release point. workshop-craft writes only markdown files, in the blueprint's folder. It writes no code and touches nothing in git: no branch, no worktree, no ignore rule. Git setup after workshop-craft, and putting `.blueprints` under git, are the user's decisions. A project's glossary and ADRs, when it has them, change only at the end of a pipeline, through workshop-glossary's merge. ## Before the first question …
Read the whole file at its exact version.
How to install
mdr add frolad/tars/workshop-craft@sha256:1d6f2ba8075b4bdfThe line at the top of this page pins the label git:20261104.96c9a51, 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_or7jc3kafy437eus)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 4, 2026.
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 (11364 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
frolad/tars · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_or7jc3kafy437eus GET https://markdownregistry.com/api/v1/resolve?ref=frolad/tars/workshop-craft GET https://markdownregistry.com/api/v1/blob/1d6f2ba8075b4bdf920462eac4a17c7e497c9e3fbe8713763e95bc7a6ba7b4e7
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.