e2e-compile
01Skill Claude CodeCodex
Part of e2e-pipeline
Use when compiling E2E flow YAML to standalone bash test scripts. Triggers on "/e2e-compile", "compile flow", "recompile flow".
Claude Code plugin marketplace — curated plugins for browser E2E testing and more
Skill Claude CodeCodex
Part of e2e-pipeline
Use when compiling E2E flow YAML to standalone bash test scripts. Triggers on "/e2e-compile", "compile flow", "recompile flow".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when debugging frontend runtime bugs by injecting console.log, observing in browser, and auto-cleaning up. Triggers on "e2e debug", "debug in browser", "inject logs", "runtime debug".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when the user invokes /e2e-dispatch or asks for the E2E operations menu. Router — prefer e2e-test, e2e-map, e2e-walkthrough, e2e-skill-ops directly for specific operations.
Skill Claude CodeCodex
Part of e2e-pipeline
Use when syncing E2E plugin documentation after skill/agent changes. Diff-aware scan, history enrichment, and live probe verification. Triggers on "e2e doc sync", "/e2e-doc-sync", "check doc coverage".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when generating, verifying, or smoke-testing E2E flow YAML from plans, specs, PRs, or mapped pages. Supports browser and CLI-only (Execute external) flows. Triggers on "e2e flow", "generate flow", "verify flow", "smoke test", "cli flow".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when users need help discovering E2E pipeline commands or want to report doc gaps. Triggers on "e2e help", "/e2e-help", "how do I e2e".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when creating or updating UI element mappings for E2E testing — capturing app structure or refreshing stale mappings. Triggers on "e2e map", "map the UI", "update mapping".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when debugging e2e-test/e2e-map/e2e-walkthrough failures, maintaining these skills, or evaluating execution results. Triggers on "fix e2e skill", "e2e skill broke", "e2e gap analysis".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when running browser E2E tests — executing flow files, batch-testing across sites, or recording runs with video. Triggers on "run e2e", "e2e test", "browser test", "test with video".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when walking through UI flows interactively with human guidance — visual QA, exploring features, or recording demos. Records video by default. Triggers on "walkthrough", "walk the UI", "visual QA", "demo recording".
Skill Claude CodeCodex
Part of e2e-pipeline
Use when verifying static UI differences — computed CSS values on specific DOM elements, design tokens, theme changes, layout dimensions, pseudo-element styles. Declarative YAML input, browser-driven, pass/fail per check. Complements e2e-flow (which verifies dynamic behavior). Triggers on "ui verify", "check ui…
Skill Claude CodeCodex
Part of kc-dev-flow
Audit, adopt, or upgrade profile-native kc-dev-flow in a brownfield repository while preserving any existing planning provider, local execution grouping, workflow runtime, and delivery provider.
Skill Claude CodeCodex
Part of kc-dev-flow
Advise the next smallest integrated delivery step when an approved development route is unclear, blocked, drifting, or approaching a material transition. Use for normal delivery guidance; do not use as a mandatory stage review or independent assurance gate.
Skill Claude CodeCodex
Part of kc-dev-flow
Recommend and ask the Captain to choose POC, Pilot, or Production before a work item enters its first working stage, or when an observed promotion trigger makes the committed profile stale.
Skill Claude CodeCodex
Part of kc-dev-flow
Resume an adopted repository's approved work through its selected POC, Pilot, or Production route while loading only the shared core and selected profile-stage contract.
Skill Claude CodeCodex
Part of kc-dev-flow
Compatibility alias for callers that explicitly request the legacy science-officer-em report envelope. New delivery guidance uses chief-engineer; new independent technical assurance uses science-officer.
Skill Claude CodeCodex
Part of kc-dev-flow
Provide independent technical assurance for a contested, high-risk, hard-to-reverse, or low-confidence engineering claim. Use when the Captain or First Officer needs an evidence-bound second judgment; do not use for routine delivery guidance or as a mandatory stage gate.
Skill Claude CodeCodex
Part of kc-hyperfocus
Manually cache an insight about a file or module to the context lake. Use when you want to preserve understanding about code you just explored. Also shows lake status and metrics.
Skill Claude CodeCodex
Part of kc-hyperfocus
A session handoff tool that records the current coding-work state and creates a short prompt for continuing in another session.
Skill Claude CodeCodex
Part of kc-hyperfocus
Use when user says 'resume', 'continue', '繼續', 'pick up where I left off', or mentions a branch name to resume previous work. Triggers on session handoff resume prompts.
Skill Claude CodeCodex
Part of kc-hyperfocus
A setup tool for Claude Code’s statusline, the small information line shown while it works. It can install a display for the model, Git branch, context use, and Anthropic’s five-hour and seven-day usage quotas.
Skill Claude CodeCodex
Part of kc-nightwatch
Use when setting up, configuring, or managing kc-nightwatch scheduling and settings. Triggered by '/kc-nightwatch-config', or when user asks to schedule nightwatch, change cron time, configure Slack channel, or check what plugins are monitored.
Skill Claude CodeCodex
Part of kc-nightwatch
Use when checking nightwatch status, viewing last run results, reviewing improvement history, or reviewing pending proposals. Triggered by '/kc-nightwatch-report', '/kc-nightwatch-report --last', '/kc-nightwatch-report --review', or asking about nightwatch activity.
Skill Claude CodeCodex
Part of kc-nightwatch
Use when running nightly plugin improvement cycle — forge validation, signal harvesting, north-star gap analysis, auto-fix and proposal generation. Triggered by cron or manual invocation.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: