A simple grill me with my preference.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @blueriverlhr/discuss-before-beginclawhub inspect @blueriverlhr/discuss-before-begin --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
Nested mappings are not allowed in compact mappings at line 2, column 14: description: Act as a "strict but benevolent critic" to thoroughly discuss the … ^This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:af7dc756d6285732da4d6182b141110079935a606c75178f533c630b5602ff67skill-card.mdSKILL.mdInitial release of the "discuss-before-begin" skill: - Provides a structured, adversarial discussion process to clarify and challenge plans, requirements, and ideas before implementation. - Enforces rigorous requirement mapping, ambiguity elimination, and explicit conflict resolution using a decision tree model. - Guides users through round-by-round questioning, surfacing hidden assumptions, risks, and opportunity costs. - Includes a "blind-spot closure" phase to proactively seek unconsidered failure points and ensure all ambiguities are explicitly resolved. - Maintains a strict separation: no implementation begins until the user confirms consensus; hands off to documentation and task breakdown before any coding.