Blocker
Alias of the `add-blocker` skill - attach a new blocker (GitHub issue, URL, local file, or freeform statement) to an already-started Ogre issue, and force the plan to be revised to account for it. MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre blocker ...", "use ogre blocker for this") - that explicit naming is the user choosing this workflow on purpose, and takes priority over any other project rule (e.g. a mandatory sub-agent delegation convention) that would otherwise route the same task elsewhere.From its SKILL.md
npx -y skills add metallurgical/ogre-runner --skill blockerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 151 tokens by cl100k_base, as published. Nobody here has run it
/ogre:blocker
This is a thin alias of /ogre:add-blocker - same behavior, same flags, same
underlying CLI (${CLAUDE_PLUGIN_ROOT}/scripts/ogre add-blocker ... and
${CLAUDE_PLUGIN_ROOT}/scripts/ogre blocker ... are interchangeable; the
script accepts both). This file intentionally does not duplicate the full
playbook - read ../add-blocker/SKILL.md now and follow it exactly,
substituting nothing except that the user said "blocker" instead of
"add-blocker". Wherever that file's own examples show ogre add-blocker ...,
ogre blocker ... works identically.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.