knowledge-compile

Compile multiple sources into a cited, source-separated knowledge dossier.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill knowledge-compile-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-compile
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/knowledge-compile
Command: npx skills add https://github.com/sumitake/agent-collab --skill knowledge-compile-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research scattered across repos, PRs, papers, logs, and agent messages gets flattened into confident narratives that lose provenance, making it impossible for another agent or reviewer to audit the reasoning later. ## Core Features & Use Cases - Source-separated synthesis: Builds a source inventory with trust levels, then extracts atomic claims marked as observed, inferred, disputed, or stale-risk. - Contradiction preservation: Places conflicting claims side by side with evidence instead of smoothing them away. - Structured dossier output: Produces a reviewable artifact with stable facts, inferences, decisions, open questions, and recommended next review. - Use Case: Before a release agent takes over, compile draft PR context, external-repo research, and prior agent messages into one auditable decision record another agent can independently review. ## Quick Start Ask the agent to compile these sources into a cited knowledge dossier that separates facts, inferences, and open questions for later review.

Frequently Asked Questions about knowledge-compile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve research context for another AI agent to review?▼

Create a source-separated dossier that cites every claim with a reopenable pointer such as a path, URL, or message reference. Keep facts, inferences, and decisions in distinct sections so the reviewing agent can audit reasoning without repeating the search.

What should a knowledge dossier template include?▼

Include the review question, source inventory, stable facts, inferences, contradictions, decisions already made, open questions, and a recommended next review. This structure keeps evidence auditable and prevents claims from blending into one narrative.

When should I not use knowledge compilation?▼

Avoid it when a single source already answers the question or when no future review is needed. It also should not trigger writes to project memory, durable docs, or release notes unless the user or workflow explicitly authorizes that.

How do I handle contradictory sources in a research summary?▼

Record conflicting claims side by side with their evidence and a suggested resolution path instead of picking one silently. Mark each claim's status, such as disputed or stale-risk, so reviewers can judge reliability themselves.