context

Summarize, extract, and compare documents or repositories through a bounded routing runtime.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reading an entire document corpus or repository by hand is slow and error-prone. This Skill performs read-only, source-grounded summarization, extraction, comparison, and synthesis over bounded document sets or sealed repository roots, returning grounded content without mutating files or claiming governance authority. ## Core Features & Use Cases - Document mode: Submit bounded UTF-8 documents with label and content fields for mechanical extraction (context.documents.extract) or multi-source reasoning (context.documents.reason). - Repository mode: Provide a canonical repo_root and exact expected_repo_head for inventory, dependency tracing, or architectural synthesis (context.repository.extract / context.repository.reason). - Bounded routing contract: Send one JSON routing request per work unit to the co-packaged coordinator.py runtime, with quality_profile and effort_class tuned to the task depth. - Use Case: Ask the agent to trace control flow across a codebase or audit a set of log transcripts, and receive a grounded synthesis that you can spot-check against the original sources. ## Quick Start Ask the agent to summarize these documents or trace this repository using the context capability, providing either labeled document contents or the repository root with its expected head commit.

Frequently Asked Questions about context

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

FAQPage Schema
How do I summarize or compare multiple documents with an AI agent?▼

Provide each document as a bounded UTF-8 object with only a label and content field, then choose context.documents.extract for mechanical extraction or context.documents.reason for multi-source synthesis. The request is routed as one work unit per deliverable through the coordinator runtime.

How do I trace dependencies or control flow across a repository?▼

Use repository mode by supplying the canonical repo_root and the exact expected_repo_head, then select context.repository.extract for inventory and tracing or context.repository.reason for architectural synthesis. The runtime operates from the sealed repository root in read-only fashion.

Can this capability edit files or apply patches to my repository?▼

No. The context capability is strictly advisory and read-only. It never edits files, applies patches, creates governance evidence, or authorizes provider commands outside the co-packaged runtime.

What inputs are rejected by the context routing contract?▼

Prompt-only requests, hybrid document-plus-repository requests, document paths or globs, unextracted binary input, and source escapes are rejected. You must choose exactly one source mode with properly bounded inputs.

Does a successful routing result prove independent review or provider availability?▼

No. Planning reports route eligibility only, not live availability or authentication. Content availability and each work unit's execution_status are separate facts, and a routing result alone never establishes reviewer independence.