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.
记忆
know-enough
试用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. 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.
技能文档
Know Enough
Core rule
Know enough to act well — no less, no more. Retrieval must have an information objective.
Before each search, be able to complete:
I am looking for [information] because it could change [decision/action].
If you cannot complete that sentence, do not retrieve yet.
Procedure
- Define the next decision. What are you trying to decide, produce, or verify now?
- Inventory current knowledge. Separate known facts, assumptions, and material unknowns.
- Prioritize gaps. Retrieve only gaps that can materially change the next decision.
- Choose the source by role. Prefer an available knowledge-source registry. Distinguish:
- authoritative / normative;
- precedent / historical;
- observational / operational;
- reference / explanatory.
- Form focused queries. Search for the missing fact or evidence, not the whole topic.
- Evaluate results. Check relevance, authority, freshness, scope, and contradictions.
- Iterate only if needed. Reformulate, search another source, or call
reconcilewhen material evidence conflicts. - Stop when sufficient. Additional retrieval should be unlikely to change the next decision.
Retrieval budget
Default to the smallest useful search sequence. Expand only when:
- first results are ambiguous or weak;
- a material conflict appears;
- coverage is insufficient for the decision;
- a different evidence role is required, such as current policy plus precedent.
Output contract
Keep a compact knowledge state when the task is non-trivial:
Decision to support
Known
Missing but material
Sources consulted + role
What was learned
Remaining uncertainty
Sufficiency: ENOUGH / NOT ENOUGH
If NOT ENOUGH, say exactly what is missing and whether progress can safely continue.
Knowledge-source registry
Read references/knowledge-source-registry.md when multiple knowledge bases or retrieval tools exist.
Use references/knowledge-sources.example.yaml as a portable example.
If using Pi with a pi-rag-style retrieval extension, read references/pi-rag-integration.md.
Gotchas
- Do not retrieve everything because retrieval is available.
- Do not ask the user for a fact that an available source can cheaply establish.
- Do not treat semantic similarity as authority.
- Do not treat precedent as current policy.
- Do not keep researching after the decision is already robust to additional information.
- If the task is purely transformative and all required content is present, do not retrieve.
Composition
- Need historical analogs →
find-precedent. - Sources materially disagree →
reconcile. - Needed facts live in structured files →
ask-the-data. - Material claim must be supported →
evidence-first.
Stop condition
Stop when the next material decision can be made with explicit uncertainty and more retrieval is unlikely to change it.
相关技能
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. 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. 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. 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. 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.