raguets

Part of the Overpowered skill suite. Acquire the minimum sufficient knowledge needed to make the next material decision: identify knowledge gaps, choose the right authoritative or contextual sources, retrieve selectively, assess sufficiency, and stop when more retrieval is unlikely to change the outcome. Use when organization-specific, historical, current, or otherwise missing knowledge could materially affect the task and retrieval/RAG/search tools are available.

Part of the Overpowered skill suite. Generalize and package a qualified or otherwise proven repeatable workflow into a portable Agent Skill with concise instructions, progressive disclosure, trigger-focused metadata, gotchas, and evals. Use after real execution evidence exists—especially for a Skill Academy capability ready to graduate; do not use as the hot-generation mechanism during a task or merely to save a conversation.

Part of the Overpowered skill suite. Route knowledge-work and enterprise-automation tasks through the smallest relevant combination of Overpowered skills, and invoke gear-up only when a material execution capability is genuinely missing. Use when multiple suite skills may apply or when starting a non-trivial task involving organizational knowledge, conflicting evidence, evolving artifacts, business rules, process automation, risky side effects, verifiable completion, or an uncovered capability gap.

Part of the Overpowered skill suite. Explain material semantic differences between versions or snapshots and assess why they matter. Use for policies, procedures, contracts, requirements, datasets, configurations, APIs, schemas, reports, or other evolving artifacts when the user cares about impact rather than a raw line diff.

Part of the Overpowered skill suite. Turn sufficient evidence into a clear decision when multiple viable options remain. Use when trade-offs matter and the agent must decide, recommend a cheap discriminating test, or explicitly defer because unresolved uncertainty makes commitment unsafe.

Part of the Overpowered skill suite. Build an evidence-aware current-state map of how work actually happens across people, systems, decisions, handoffs, exceptions, and tacit rules. Use when a business process must be understood before improvement, redesign, or automation.

Part of the Overpowered skill suite. Answer reproducible questions from structured data files such as Excel, CSV, JSON, TSV, or Parquet by discovering useful inputs, reading data dictionaries, loading durable relations when helpful, inspecting schema, querying only what is needed, and returning traceable results. Use when the answer is in tabular/structured files rather than prose documents.

Part of the Overpowered skill suite. Expose material assumptions, hidden premises, and unresolved unknowns in a plan, analysis, design, or decision. Use before committing to work when an incorrect assumption could change the approach; avoid turning trivial low-impact unknowns into bureaucracy.

Part of the Overpowered skill suite. Transform a described human/business process into an executable automation design by separating deterministic steps, agentic reasoning, existing systems, and human gates; define triggers, data, decisions, exceptions, controls, and verification. Use when the goal is to automate a process, not merely understand it or interview the user about it.

Part of the Overpowered skill suite. Independently determine whether a claimed task outcome is actually complete by reconstructing completion criteria and checking fresh evidence. Use before declaring work done, accepted, migrated, reconciled, fixed, or delivered; not as a general planning loop.

Part of the Overpowered skill suite. Simulate a workflow, migration, bulk update, automation, or other side-effecting operation before committing changes. Use when effects are broad, costly, irreversible, externally visible, or difficult to audit; skip when the action is trivially reversible and low risk.

Part of the Overpowered skill suite. Require evidence proportional to material claims and clearly separate evidence, inference, and uncertainty. Use for research, analysis, recommendations, reports, audits, or decisions where unsupported confidence would be harmful; do not use for purely creative or stylistic tasks.

Part of the Overpowered skill suite. Find and compare relevant historical cases—contracts, proposals, projects, incidents, decisions, designs, or exceptions—to inform a current problem without treating similarity as authority. Use when the question is effectively 'have we dealt with something like this before?' or reusable prior work may exist.

Part of the Overpowered skill suite. Pressure-test a rule, decision table, SOP, requirement, or business process by finding edge cases and alternative branches that would break a happy-path specification. Use before automation or formalization when hidden exceptions could change behavior; focus on material exceptions, not imaginative trivia.