Use when source material must be transformed into a compact, evidence-aware model for learning, decisions, or an Obsidian concept note.
npx skills add https://github.com/Mark393295827/third-brain-v7-skills --skill cognitive-compile
<skill_contract>
<input>Source-grounded material, original question, learning or decision goal, audience, and destination.</input>
<output>An eight-part evidence-aware mental model separating facts, mechanisms, conflicts, hypotheses, decisions, and action.</output>
<done>Each material claim retains provenance and uncertainty, and one bounded next action answers the original question.</done>
<non_goals>Inventing missing claims, erasing contradictions or provenance, or treating interpretation as source fact.</non_goals>
Compile information into a decision-ready mental model. Compression must preserve provenance, uncertainty, contradiction, and the original question.
Provide: source material, original question, intended decision or learning goal, and preferred destination. Optional: existing wiki concepts to compare.
<intake>
Identify the source boundary, original question, audience, and required fidelity. Label direct source claims, external facts, and analyst inferences before synthesis.
</intake>
<unknowns_gate>
If the source is inaccessible, truncated, or missing the material needed to answer the question, return INSUFFICIENT_EVIDENCE. Ask one probe only when its answer changes the compile structure; otherwise proceed with explicit unknowns.
</unknowns_gate>
<execute>
Produce eight compact sections:
Prefer one durable concept note over several thin notes. Preserve source links or block references; do not rewrite immutable source notes.
</execute>
<evaluate>
Verify that every material conclusion traces to evidence or is labeled inference; the original question is answered; contradictions remain visible; and the action follows from the model. Remove summaries that merely restate the source without changing understanding.
</evaluate>
NEEDS_INPUT: the intended question or audience is absent and materially changes the output.INSUFFICIENT_EVIDENCE: the source cannot support the requested compile.VERIFY_FAILED: a conclusion lacks traceable evidence; downgrade it to hypothesis or remove it.Return status, result (the eight-section compile), evidence (source locators), unknowns, and next_action.
</skill_contract>
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take mark393295827/cognitive-compile from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.