verify-bidirectional
SolidA skill that immediately updates the baseline and reflects it in the next session when the user raises a counter-argument to an AI recommendation. Triggered by "is that right?", "re-examine this", "something seems off here". Explicit /verify-bidirectional call also possible.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- chrono-meta
- Repository
- chrono-meta/forge-harness
- Created
- 3 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ref-sp-agents-verification-discipline
Portable verification discipline that counters jumping to answers, sycophancy, and overconfidence: enumerate candidate approaches or root causes, route verification by confidence and stakes, prune on evidence, abstain explicitly when nothing can settle a claim. Use when: choosing between approaches or root causes, acting on an unverified claim or assumption, responding when the user challenges or contradicts a conclusion, deciding how much verification a risky or irreversible action needs, or calibrating stated confidence in answers, reviews, and reports.
double-check
Use whenever the user asks to double-check, cross-check, verify, recheck, sanity-check, or confirm prior analysis or results — including "are you sure", "are you confident", "is this true", "still true?", "prove it", "triple check", "check against" some artifact, "look again", "repeat the analysis", or "repeat your findings in full". Re-derives the answer from source artifacts and returns it standalone in the original request's structure — never a revision log of the prior turn. Also invoke before re-running any analysis whose output the user has already seen once. To repair a chat where a diff-shaped answer already happened, use the `double-check-align` skill.
bs-check
Use before telling a client or stakeholder "this is fixed", before deploying changes to a production site or service, before activating or modifying a live automation/workflow, before claiming an integration works end-to-end, before quoting pricing or API behavior in a comparison, or before running a destructive infrastructure command. Also use when the user says "confidence check", "how confident are you", "validate this", "pressure-test this", "/bs-check", or whenever a confident-sounding claim has not been directly validated by a query, observation, comparison, or quotable source. ALSO covers design-time reasoning audits via subcommands - "bs-check premise" (are we solving the right problem? premise acceptance - Socratic + Steelman), "bs-check approach" (did we commit too fast? - Burden of Proof, Cold Start, Alternatives, Pre-mortem), "bs-check fresh" (all 9 patterns, fresh-context sub-agent). Trigger phrases for those - challenge this, push back, devil's advocate, poke holes, steelman this, are we solving