bodencrouch/mission-runtime (mission)

This skill should be used whenever the user states a broad, outcome-shaped objective rather than a narrow single task — phrases like "take ownership of", "make this reliable", "improve performance", "make it fast", "fix Linux setup", "clean up this codebase", "get this production-ready", "make the tests solid", or any instruction that describes a desired end state of a project rather than one bounded deliverable — including hedged phrasings like "could you maybe look at making this more reliable". Also triggers on "start a mission", "run this as a mission", or "/mission". A bounded micro-task with one named deliverable ("rename this variable", "fix this typo") is not a mission — just do it. The skill converts sparse intent into an operating contract, writes the full brief for every specialist it commissions, and runs a persistent plan–execute–verify–replan loop until a substantive stopping condition is reached.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/bodencrouch/mission-runtime

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

1 critical finding reported by cisco-skill-scanner, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.