scc-system-context

Retrieve evidence-backed system context from SCC-indexed repositories before planning or editing code.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/carterlasalle/scc --skill scc-system-context-carterlasalle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scc-system-context
Source: https://github.com/carterlasalle/scc/tree/main/plugins/omp/scc/skills/scc-system-context
Command: npx skills add https://github.com/carterlasalle/scc --skill scc-system-context-carterlasalle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coding agents often start tasks in unfamiliar repositories without understanding the architecture, forcing them to rediscover system structure through slow, error-prone search. This Skill provides on-demand access to the System Context Compiler's verified machine model of the repository, so planning and edits are grounded in evidence-backed facts rather than assumptions. ## Core Features & Use Cases - Session Startup Context: Call system_context for a fused view of the system atlas, API surface, coverage, and omissions with an adaptive token budget. - Task-Specific Context Packs: Use task_context, component_context, flow_context, and impact_context to drill into components, runtime flows, and cross-layer change impact before editing. - Staleness Verification: Run verify_context to detect stale facts and re-index with scc index so outdated information never enters trusted context. - Use Case: Before modifying a shared API contract, call impact_context on the touched files to see downstream consumers, invariants, and failure behavior, then honor those constraints in your change. ## Quick Start Ask the agent to call system_context at the start of your session, then request task_context with your specific goal before planning any code changes.

Frequently Asked Questions about scc-system-context

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

FAQPage Schema
How do I get system context before editing code in an unfamiliar repository?

Call system_context at session start for a fused view of the architecture, API surface, and coverage, then call task_context with your specific goal. This returns relevant components, flows, ownership, contracts, invariants, and tests before you plan edits.

What is the System Context Compiler and how does it help coding agents?

The System Context Compiler (SCC) compiles code, config, infrastructure, and runtime evidence into a verified machine model of a software system. It emits task-specific context packs so coding agents start with correct system understanding instead of rediscovering it through search.

Which SCC tool should I use for architecture deep-dives versus task planning?

Use system_atlas for Level 0 architecture views of components, flows, and ownership, and task_context for any repository-changing task before planning. For cross-layer changes, call impact_context on the files you will touch.

How do I check if the SCC system model is stale?

Call verify_context, which reports staleness warnings when files have changed on disk since indexing. If it reports staleness, re-index with scc index before trusting any facts, since stale facts are excluded from trusted context packs.

Can I trust inferred claims in SCC context packs?

Inferred claims are labeled with the INFERRED evidence status and should be treated as hypotheses, not facts. The trust hierarchy ranks repository and runtime evidence above System IR, task state, memory, and assumptions, and conflicts between sources are recorded rather than merged.