questionably-ultrathink-skill_skill

This skill orchestrates isolated fact-checked reasoning for complex problems, ensuring rigorous verification and unbiased final answers.
  • Shell

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill snowmead/questionably-ultrathink --skill questionably-ultrathink-skill

  • SKILL.md22.6 KB

Overview

This skill orchestrates rigorous, high-assurance reasoning for complex problems by combining Atom-of-Thought decomposition with isolated fact verification. It structures problems into independent atoms, generates claims and verification questions, then runs verifiers in isolation before synthesizing a verified final answer.

How this skill works

The orchestrator builds a DAG of atomic questions, then a claim generator produces claims and pre-creates verifier files (questions only). Independent verifier agents research each verification question with zero context about the claims. A verification maintainer cross-checks verifier outputs against claims and synthesizes a final answer. Background execution lets you run verifiers in parallel to improve throughput.

When to use it

  • Complex multi-part questions requiring systematic decomposition
  • Architecture, security, or high-stakes technical decisions
  • When you must verify facts independently and avoid confirmation bias
  • Debugging issues that need isolated evidence and traceable verification
  • Requests containing triggers like “be thorough”, “verify”, or “are you sure”

Best practices

  • Always ask clarifying questions first if intent, scope, or success criteria are unclear
  • Select the analysis rigor upfront (Standard, Thorough, High-Stakes) based on consequences
  • Run claim generators in parallel but block until claims.md exists to get claim counts
  • Spawn verifiers as background tasks so independent atoms can progress concurrently
  • Keep task IDs and monitor verifier files (look for an “# Answer” section) rather than relying on shared context

Example use cases

  • Evaluating trade-offs and verified facts for a cloud security architecture decision
  • Breaking a complex debugging problem into atoms and independently verifying root-cause hypotheses
  • Producing a traceable, evidence-backed final answer for compliance or policy analysis
  • Running parallel verification for multiple independent design options to speed decision-making
  • High-stakes code review where independent fact-checking prevents bias in conclusions

FAQ

Isolation prevents bias contamination: verifiers answer only the verification question without seeing the claim, so their research is independent and harder to game.

When should I use background execution?

Use background execution when verifier tasks for different atoms are independent and you want pipeline parallelism to improve throughput while other atoms are prepared or maintained.

What determines progression through the pipeline?

State is file-driven: presence and content of question.md, claims.md, verifiers/*.md (with answers), and answer.md determine what to run next.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
questionably-ultrathink-skill skill by snowmead/questionably-ultrathink | VeilStrat