seemseam
- 106 skills
- 0 followers
- 4 hours ago last updated
- ▌ Ask 2 · seemseamDelegate work or request information from another CCB-managed agent using ask. Use when the user asks Grok to ask, delegate to, hand off to, consult, or send work to a named CCB agent, or when project memory requires CCB collaboration.
- ▌
- ▌
- ▌
- ▌
- ▌ Ccb Clear 2 · seemseamClear CCB managed agent conversation context with `ccb clear`. Use for `/ccb-clear`, `$ccb-clear`, `$ccb_clear`, or requests to reset one or more CCB agent contexts without deleting project state.
- ▌ Ccb Clear 3 · seemseam bundleClear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.
- ▌ Plan Tree · seemseam bundleUse when project work involves planning, roadmap discussion, requirement clarification, scope negotiation, implementation strategy, execution-readiness checks, progress tracking, handoff, decision/open-question/evidence management, or maintaining a Markdown planning tree. Helps turn short-lived plans into stable docs/plantree state with registered plan roots, baseline, roadmap/status, topics, decisions, history, ideas, and plan-to-landing traceability across sessions and agents.
- ▌ Autoflow Plan · seemseam bundleCreate a task plan with dual design. Use when starting a new task or running /tp.
- ▌ Autoflow Run · seemseam bundleExecute current step in AutoFlow workflow. Use when running /tr or continuing task execution.
- ▌ Roles · seemseam bundleManage lightweight role routing (executor/reviewer/documenter/designer) for all tasks. Use for /roles.
- ▌ Review · seemseam bundleDual review with Claude and Codex for quality verification. Use for step or task review.
- ▌ Fileops · seemseam bundleDelegate file I/O to Codex via FileOpsREQ protocol. Use when Claude needs Codex to modify files.
- ▌ Ask Codex · seemseam bundleSend structured prompt to Codex and parse JSON response. Use for direct Codex communication.
- ▌ Ask Gemini · seemseam bundleSend structured prompt to Gemini and parse JSON response. Use for direct Gemini communication.
- ▌ Dual Design · seemseam bundleParallel design by Claude and Codex with merge discussion. Use for step or task design.
- ▌ Mode Switch · seemseam bundleSwitch between plan and bypass modes. Use when changing Claude's execution mode.
- ▌
- ▌ Ccb Clear · seemseamClear conversation context for one or more mounted CCB agents using ccb clear. Use when the user invokes /ccb-clear, $ccb-clear, or $ccb_clear, or asks Grok to clear or reset CCB agent context without restarting agents or deleting project state.
- ▌ Ccb Compact · seemseamCompact CCB managed agent conversation context with `ccb compact`. Use when the user writes `$ccb-compact`, `$ccb_compact`, or asks to summarize one or more mounted agent contexts without restarting agents or deleting project state.
- ▌ Reconnect · seemseam bundleEnable or disable tmux-bound disconnect recovery for the current Codex thread. Use only for the explicit invocations `$reconnect on` or `$reconnect off` inside a Codex CLI running in tmux.
- ▌ Ccb Diagnose · seemseamDiagnose a named CCB agent by combining authoritative runtime and job lineage with deep read-only pane inspection, apply bounded recovery when evidence supports it, verify the result, and request authorization before submitting a redacted GitHub issue. Use for `$ccb_diagnose agentname`, `$ccb-diagnose agentname`, or reports that a CCB agent is stuck, disconnected, not continuing, not replying, or showing provider errors.
- ▌ Node Check · seemseamVerify one CCB worker node and reject hidden fallback, degradation, scope shrinkage, or missing evidence.
- ▌
- ▌ Bounded Work Item · seemseamExecute one bounded CCB work item and report evidence without changing workflow authority.
- ▌ Round Verification · seemseamVerify integrated round evidence and return a machine-readable round result for script import.
- ▌ Ccb Doc · seemseam bundleCreate 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.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Archi Diff · seemseamReview current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact.
- ▌ Archi Full · seemseamRun or read full-project architecture analysis and summarize structural weaknesses, hotspots, and maintainability risks.
- ▌ Archi Goal · seemseamProduce goal-driven architecture guidance for a specific boundary, refactor, subsystem, or maintainability objective.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Archi Advice · seemseamProduce architecture improvement advice from architecture evidence and source inspection.
- ▌ Ccb Execute · seemseam bundleExecute 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.
- ▌
- ▌ Ccb Config · seemseam bundlePrivate 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; non-self agents should delegate CCB config changes to ccb_self.
- ▌
- ▌ CI Failure Fix · seemseamFix 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.
- ▌ Role Research · seemseamPlan and run evidence-backed research before designing an Agent Role; use for broad role ideas, skill/tool discovery, source discovery, maintained example comparison, and research briefs that must cite inspected sources before Role source is written.
- ▌
- ▌ Role Blueprint · seemseamProduce a machine-checkable Agent Role blueprint before writing Role source; use after research, candidate scoring, or source ingestion to define Role id, aliases, catalog level, memory, skills, references, tools, adapters, permissions, provenance, validation plan, write scope, and single-role/multi-role/topology decision.
- ▌ Bug Fix Prove It · seemseamFix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.
- ▌ Ccb Self Chain · seemseamInternal 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, empty artifact, duplicate retry, or chain-stalled incidents because it includes mailbox and pane cross-checks.
- ▌ Code Context Scan · seemseamScan 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.
- ▌
- ▌ Archi Evidence Map · seemseamSelect 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, project-native checks, dependency analysis, SAST, and architecture fitness tools.
- ▌ Large File Control · seemseamPrevent large-file growth and mixed-responsibility edits. Use when adding significant logic to a large file, mixed-purpose module, or file with repeated conditionals.
- ▌ Test Backed Change · seemseamAdd or update behavior-focused tests for code changes and run appropriate verification. Use when behavior changes, logic is added, or existing behavior could regress.
- ▌ Archi Change Impact · seemseamReview 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 module or runtime boundaries.
- ▌ Architecture Review · seemseamUmbrella architecture review skill for hosts that only project one generic skill. Prefer focused archi-* methods when available.
- ▌ Ccb Clear Resume · seemseam bundleDiagnose 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 lineage/runtime evidence, and resume or resubmit the interrupted work with a compact handoff. Use for requests like "clear this agent then restore its task", "context is broken but continue the current job", "repair talk1/worker context and inherit current state", or "after clear, recover the task".
- ▌ Ccb Self Recover · seemseamRecover 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 going after provider/API failure.
- ▌ Fallback Discipline · seemseamControl error handling, defaults, retries, compatibility paths, and fallback behavior. Use before adding catch blocks, defaults, shims, optional values, retries, or graceful degradation.
- ▌ Role Source Ingest · seemseamAnalyze external skill, plugin, prompt, tool, or workflow source before converting it into an Agent Role; produce inventory, source classification, provenance, split decision, blueprint gate, and validation plan before writing Role source.
- ▌ Archi Decision Drift · seemseamReview 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 behavior.
- ▌ Ccb Self Diagnose · seemseamDiagnose 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 reply did not arrive, or what to check first.
- ▌ Repo Style Following · seemseamFollow existing repository style, commands, naming, file layout, test patterns, dependency conventions, and code shape. Use when implementing in an unfamiliar repo or module.
- ▌ Role Creation Audit · seemseamCreate, audit, repair, or explain Agent Role source for spec compliance and catalog readiness; use for Role authoring, Role source review, memory/skill/prompt optimization, catalog checks, and routing broad research or external source conversion through the dedicated research, candidate-score, blueprint, or source-ingest workflows before writing.
- ▌
- ▌ Role Candidate Score · seemseamScore and filter candidate sources before turning them into Agent Roles; use after role research when comparing skills, plugins, repositories, tools, prompts, or workflow sources for relevance, authority, license, host fit, security, testability, and Role-shape fit.
- ▌ Minimal Implementation · seemseamImplement the smallest safe repo-native code change for the requested behavior. Use for feature work, small refactors, and multi-file implementation tasks.
- ▌ Safe Dependency Change · seemseamGate dependency additions, removals, upgrades, and lockfile changes. Use before changing dependencies, package managers, SDKs, generated lockfiles, or install commands.
- ▌ Role Setup · seemseam bundleCheck, plan, apply, or repair role-scoped runtime setup for the current mounted Role. Use when the user asks to activate role tools, enable MCP/plugin/provider configuration, run role_setup, inspect isolation, verify private tool installation, or repair projection output. For uninstall or role config removal, route to the agent-roles or Host Adapter unmount lifecycle instead of deleting from inside the agent.
- ▌
- ▌ Archi Fitness Functions · seemseamPropose 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 criteria.
- ▌ Archi Module Boundaries · seemseamReview 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.
- ▌ Ccb Expert Reference · seemseamAnswer 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 feature is planned/implemented/released, where to find code/tests/docs, or how talk1's CCB developer/user manuals apply.
- ▌ Frontdesk Intake · seemseamConvert user conversation into macro workflow requests and present curated clarification or final artifacts.
- ▌ Archi Dependency Topology · seemseamReview 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 source-backed topology evidence.
- ▌ Archi Distributed Systems · seemseamReview 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.
- ▌ Planner Task Packet · seemseamDraft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.
- ▌ Ccb Comm Reply Recover · seemseamDiagnose 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 active-turn followup, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.
- ▌ Figma To Code · seemseamUse when Figma context, selected frames, variables, components, or screenshots should be mapped to local frontend implementation without copying private Figma state into Role source.
- ▌ Archi Tooling · seemseamManage and diagnose the CCB adapter's optional npm Archi CLI, bundled Hippo/llmgateway capabilities, and role tool readiness.
- ▌ Frontend Brief · seemseamUse when a frontend request is vague, new, screenshot-based, Figma-based, or needs audience, workflow, constraints, acceptance criteria, and verification scope before implementation.
- ▌ Ccb Workflow Orchestrate · seemseamPlan 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 work, or reload/restart affected panes so new mounted-agent instructions are loaded.
- ▌ Review Code Quality · seemseam bundleReview 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.
- ▌ Source Check Before API Use · seemseamCheck 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.
- ▌ Browser Quality · seemseamUse to validate a running frontend with browser evidence: visual QA, responsive screenshots, accessibility snapshots, console/network issues, layout collisions, and LCP/INP/CLS performance risks.
- ▌
- ▌ Ccb Mobile Relay Maintain · seemseamDiagnose 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 connect, pair, discover projects, open terminals, expose Provider controls, or when a user explicitly asks to activate, update, revoke, or repair a CCB Relay host or device.
- ▌ Demo Kb Curation · seemseamUse to curate link-only frontend demos, inspiration sources, pattern references, and component examples with source authority, license posture, tags, and do-not-copy boundaries.
- ▌ Visual Direction · seemseamUse when UI needs stronger visual quality, anti-generic design, brand fit, layout, typography, color, spacing, density, motion, or state-design direction.
- ▌ Mobile UX Flow · seemseamDesign native-feeling mobile flows. Use for mobile navigation, tabs, stacks, sheets, gestures, safe areas, keyboard behavior, haptics, permissions, onboarding, empty/error/loading/offline states, and platform-specific iOS or Android interaction polish.
- ▌
- ▌ Mobile App Brief · seemseamCreate a mobile app implementation brief. Use when starting a mobile app or feature, clarifying iOS and Android platform scope, choosing native versus cross-platform stack, or turning requirements, screenshots, Figma context, or rough ideas into a build plan.
- ▌ Orchestrator Capacity · seemseamPrivate CCB orchestrator skill for requesting, inspecting, using, and releasing dynamic loop capacity through `ccb loop capacity` only.
- ▌ Design System Tokens · seemseamUse for design tokens, theming, light/dark or multi-brand support, token drift, component-system alignment, Figma variables, or Style Dictionary/DTCG token workflows.
- ▌ Agy Frontend Delegate · seemseamUse when the user wants Google Antigravity CLI (`agy`) to attempt or compare a bounded frontend implementation in an isolated worktree, with diff review before merge.
- ▌ Component Composition · seemseamUse before building UI with local components, Storybook, shadcn, Radix, a private registry, or another component library; verifies available components, props, states, and composition choices.
- ▌ Mobile Device Quality · seemseamValidate mobile apps with simulator, emulator, device, accessibility, performance, crash, log, and form-factor evidence. Use for mobile QA, safe-area bugs, keyboard issues, gesture failures, layout clipping, jank, startup time, memory, network, and release-blocking defects.