cca2a
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: cca2a
description: > Use when this capability is needed. Explanation-only skill. Documents the pattern so a new ses…
category: other
runtime: no special runtime
---
# cca2a output preview
## PART A: Task fit
- Use case: > Use when this capability is needed. Explanation-only skill. Documents the pattern so a new session can grok it once instead of the user re-deriving it for 30 turns. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “What to read when / The idea in one paragraph” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> Use when this capability is needed. Explanation-only skill. Documents the pattern so a new session can grok it once instead of the user re-deriving it for 30 turns. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “What to read when / The idea in one paragraph” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “What to read when / The idea in one paragraph”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: cca2a
description: > Use when this capability is needed. Explanation-only skill. Documents the pattern so a new ses…
category: other
source: tomevault-io/skills-registry
---
# cca2a
## When to use
- > Use when this capability is needed. Explanation-only skill. Documents the pattern so a new session can grok it once…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “What to read when / The idea in one paragraph” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "cca2a" {
input -> user goal + target files + boundaries + acceptance criteria
context -> What to read when / The idea in one paragraph
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} CCA2A — Claude Code Agent-to-Agent
Explanation-only skill. Documents the pattern so a new session can grok it once instead of the user re-deriving it for 30 turns.
Canonical files (read these, not template copies):
Entry points:
.claude/BOOT.md— session entry point (one page).CLAUDE.md— workspace spec, links to all of the below.
Eight bookkeeping files (rows are history; specific fields are state; never delete a row; method hierarchy: APPEND preferred → Edit-field after prior Read → Write prompts for confirmation):
History / dashboards:
.claude/board/LATEST_STATE.md— current contract inventory..claude/board/PR_ARC_INVENTORY.md— APPEND-ONLY per-PR arc..claude/board/STATUS_BOARD.md— deliverable-level dashboard..claude/board/INTEGRATION_PLANS.md— versioned plan index.
Kanban / audit (priority + scope tags on every entry):
.claude/board/EPIPHANIES.md— date-prefixed insight log. Status: FINDING / CONJECTURE / SUPERSEDED..claude/board/ISSUES.md— Open + Resolved bugs / regressions. Double-entry: issue captured on discovery; Resolution appends on close. Priority P0-P3, Scope @agent Ddomain: . .claude/board/IDEAS.md— Open + Implemented + Rejected speculation. Triple-entry: idea captured, shipped appended, plan-update logged. Priority + Scope..claude/board/TECH_DEBT.md— Open + Paid knowingly-deferred work. Priority + Scope + Introduced-by-PR + Payoff-estimate.
Agent ensemble + orchestration:
.claude/agents/BOOT.md— orchestration spec + Knowledge Activation + Handover Protocol..claude/agents/README.md— function inventory of all agents.
Governance + hooks:
.claude/settings.json— team-shared governance (ask-on-Edit for the two strictest bookkeeping files, deny on destructive ops, SessionStart + PostCompact hooks)..claude/hooks/session-start.sh/post-compact.sh— inject bootload context at turn 0 / after compaction.
Active plans:
.claude/plans/<name>-v<N>.md— indexed viaINTEGRATION_PLANS.md. Old versions stay with Status annotation; new versions prepend.
What to read when
- New session on this workspace:
.claude/BOOT.mdfirst, then the three mandatory reads it lists. - Understanding the A2A two-layer model: concepts.md.
- Comparing to official Claude Code conventions: divergence.md.
- Concrete recipe: code awareness in ~90 s via prompt↔PR ledger: procedure-bookkeeping.md. Three-pass Haiku→Opus→main-thread pipeline. First deployment: PR #213 (lance-graph, 41 prompts) + PR #110 (ndarray, 25 prompts) on 2026-04-19, both ~90 s wall clock.
The idea in one paragraph
Every new session pays a 30-turn rediscovery tax rebuilding context about what types exist, which conventions are locked, what work is queued. CCA2A is the scaffold that cuts that to 3-5 turns: two mandatory knowledge files that state current inventory and decision history, one agent ensemble file that routes subagents, one hook that injects critical state after compaction. Append-only governance on the history files so drift can't erode the arc.
Source: AdaWorldAPI/lance-graph — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review