Menu
SkillsMP has collected 84 skills from SeemSeam/agent-roles-spec. Open a skill to review its source and details.
Showing 40 of 84 collected skills.
Review a declared code change or code scope with evidence-backed findings and five independent quality scores. Use for pull requests, diffs, commits, patches, file sets, modules, bug fixes, refactors, and implementation-review requests.
Diagnose and recover a CCB agent whose provider context is corrupted, stale, overloaded, or semantically off-track when the user wants more than a plain clear: clear the agent only after safety checks, reconstruct the active task context from CCB…
Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, chain not continuing, rejected…
Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self;…
Answer CCB architecture, source-location, command, config, communication, release, test-evidence, manual, and "where is this implemented" questions with source-backed evidence. Use when a user asks how CCB works, how to use a CCB feature, whether a CCB…
Diagnose and safely maintain the CCB Mobile host service, LAN/tailnet/Cloudflare Tunnel/Relay routes, pairing and devices, Relay invitation or host activation, multi-project terminals, and capability-negotiated Provider controls. Use when Mobile cannot…
Internal CCB lineage repair for retry/resubmit/ack decisions when a job/message/attempt/reply/inbound-event/artifact id is already in hand. Prefer ccb-comm-reply-recover for user-visible "reply did not arrive", stuck busy/delivering, queued-behind-active,…
Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a…
Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work…
Plan and activate CCB multi-agent workflow orchestration from ccb_self. Use when the user asks to split work across mounted agents, assign analysis/implementation/review roles, adjust per-agent task memory, coordinate ask dispatch, deduplicate overlapping…
Manage and diagnose the CCB adapter's optional npm Archi CLI, bundled Hippo/llmgateway capabilities, and role tool readiness.
Produce architecture improvement advice from architecture evidence and source inspection.
Review architecture change impact, blast radius, migration sequencing, reversibility, rollback, and compatibility risk. Use for refactors, API/schema changes, dependency migrations, service splits, storage moves, large PRs, or changes whose effects may cross…
Review ADRs, design decisions, assumptions, and implementation consistency. Use when architecture risk involves stale ADRs, undocumented decisions, superseded assumptions, decision violations, migration rationale, or drift between code, docs, and current…
Review dependency topology, cycles, direction, and import/workspace graph risk. Use when architecture risk depends on dependency direction, circular dependencies, package graph shape, layering imports, workspace coupling, or replacing Architec with…
Review current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact.
Review distributed-system dataflow, service boundaries, failure modes, consistency, observability, and reliability tradeoffs. Use for microservices, queues, event flows, APIs, retries/timeouts, idempotency, data ownership, SLOs, or operational blast radius.
Select architecture and code-review evidence sources before an archi review. Use when the user asks which tools to use, wants less dependence on Architec, needs architecture/code review readiness, or needs a review plan across direct source reading,…
Propose and review architecture fitness functions, executable guardrails, and quality gates. Use when architecture findings should become repeatable checks, CI gates, dependency rules, architecture tests, ADR checks, Semgrep/CodeQL policies, or migration exit…
Run or read full-project architecture analysis and summarize structural weaknesses, hotspots, and maintainability risks.
Produce goal-driven architecture guidance for a specific boundary, refactor, subsystem, or maintainability objective.
Review module boundaries, layering, domain ownership, and DDD leakage. Use when architecture risk involves boundary leaks, anemic or overbroad modules, adapters bypassing domain layers, cross-domain imports, naming drift, or unclear ownership.
Umbrella architecture review skill for hosts that only project one generic skill. Prefer focused archi-* methods when available.
Private CCB orchestrator skill for requesting, inspecting, using, and releasing dynamic loop capacity through `ccb loop capacity` only.
Convert user conversation into macro workflow requests and present curated clarification or final artifacts.
Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.
Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.
Fix failing tests or CI by reading logs, identifying the smallest failing surface, making a minimal change, and rerunning targeted verification. Use when given CI logs, failing commands, or broken checks.
Scan relevant source, tests, commands, and existing project patterns before editing code. Use before non-trivial implementation, bug fixing, or refactoring when the right local pattern is unclear.
Control error handling, defaults, retries, compatibility paths, and fallback behavior. Use before adding catch blocks, defaults, shims, optional values, retries, or graceful degradation.
Prevent large-file growth and mixed-responsibility edits. Use when adding significant logic to a large file, mixed-purpose module, or file with repeated conditionals.
Implement the smallest safe repo-native code change for the requested behavior. Use for feature work, small refactors, and multi-file implementation tasks.
Follow existing repository style, commands, naming, file layout, test patterns, dependency conventions, and code shape. Use when implementing in an unfamiliar repo or module.
Gate dependency additions, removals, upgrades, and lockfile changes. Use before changing dependencies, package managers, SDKs, generated lockfiles, or install commands.
Check current official documentation before writing framework, library, CLI, or API code where version-specific correctness matters. Use when APIs are unfamiliar, recently changed, or user asks for current best practice.
Add or update behavior-focused tests for code changes and run appropriate verification. Use when behavior changes, logic is added, or existing behavior could regress.
Create or update project documentation according to CCB document routing rules. Use when Claude asks to write docs, route documents by the docs structure contract, or archive implementation details.
Source text: Chinese
Execute CCB implementation, explore, or consult tasks from Claude based on spec/docs, validate the result, and return a compact receipt. Use when Claude sends a CCB task with execute/explore/consult mode.
Source text: Chinese
重新分析 Requirement 原文和已生成人读设计/任务文档，修正理解漂移。
Source text: Chinese
记录用户对某个审查门、拆分草案或风险事项的明确批准。
Source text: Chinese