.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/iamcxa/kc-claude-plugins
home/skills/iamcxa/kc-claude-plugins
iamcxa avatar

iamcxa/kc-claude-plugins

35 skills

View on GitHub
$npx skills add iamcxa/kc-claude-plugins
SkillInstalls
break-point-probeUse when verifying that a fix actually reaches the bug's break-point in the real runtime path — not just at unit-test level.—decision-debateUse when presenting 2+ technical approaches, listing pros/cons, evaluating architecture or technology trade-offs, or when the user asks 'which should I choose'.—e2e-compileUse when compiling E2E flow YAML to standalone bash test scripts. Triggers on "/e2e-compile", "compile flow", "recompile flow".—e2e-debugUse when debugging frontend runtime bugs by injecting console.log, observing in browser, and auto-cleaning up.—e2e-dispatchUse when the user invokes /e2e-dispatch or asks for the E2E operations menu.—e2e-doc-syncUse when syncing E2E plugin documentation after skill/agent changes. Diff-aware scan, history enrichment, and live probe verification.—e2e-flowUse when generating, verifying, or smoke-testing E2E flow YAML from plans, specs, PRs, or mapped pages. Supports browser and CLI-only (Execute external) flows.—e2e-helpUse when users need help discovering E2E pipeline commands or want to report doc gaps. Triggers on "e2e help", "/e2e-help", "how do I e2e".—e2e-mapUse when creating or updating UI element mappings for E2E testing — capturing app structure or refreshing stale mappings.—e2e-skill-opsUse when debugging e2e-test/e2e-map/e2e-walkthrough failures, maintaining these skills, or evaluating execution results.—e2e-testUse when running browser E2E tests — executing flow files, batch-testing across sites, or recording runs with video.—e2e-walkthroughUse when walking through UI flows interactively with human guidance — visual QA, exploring features, or recording demos. Records video by default.—geminiUse when asked to 'gemini review', 'gemini challenge', 'ask gemini', or want an independent cross-model second opinion / adversarial review / consultation from…—kc-cache-insightManually cache an insight about a file or module to the context lake. Use when you want to preserve understanding about code you just explored.—kc-em-plan-reviewUse when reviewing a teammate's plan, Linear project/issue, design doc, or Slack-thread proposal AS the EM before build starts — applies Kent's EM lenses,…—kc-em-syncUse when syncing team context (initiatives, projects, members, cycles, customers, estimate scale) from Linear to local YAML cache.—kc-em-triageUse when triaging Linear issues as EM — exploring codebase, researching tech feasibility, decomposing oversized issues, posting structured implementation…—kc-nightwatchUse when running nightly plugin improvement cycle — forge validation, signal harvesting, north-star gap analysis, auto-fix and proposal generation.—kc-nightwatch-configUse when setting up, configuring, or managing kc-nightwatch scheduling and settings.—kc-nightwatch-reportUse when checking nightwatch status, viewing last run results, reviewing improvement history, or reviewing pending proposals.—kc-plugin-forgeUse when creating a new Claude Code plugin, auditing an existing plugin for quality, improving plugin skills with TDD, or verifying plugin agent configurations.—kc-plugin-forge-doc-syncUse when plugin documentation needs updating after feature changes, when verifying existing docs accurately reflect actual skill/agent behavior, or for…—kc-plugin-forge-helpUse when users need help with Plugin Forge commands, want to discover available routes, or report documentation gaps.—kc-plugin-forge-sanitize-checkUse before publishing a public plugin (especially before /kc-marketplace-sync) to grep for known leak patterns in the plugin's public reference files.—kc-pr-announceUse when a feature is complete with PR and demo artifacts (e2e walkthroughs, Loom, screenshots), and user wants to announce on Slack.—kc-pr-createUse when user says 'create pr', 'open pr', '建立 PR', '開 PR', '發 PR', '送審', or when implementation is complete and changes need a pull request on GitHub.—kc-pr-daemonUse when user says 'start daemon', 'stop daemon', 'daemon status', 'pr daemon', 'daemon config', 'daemon 掛了', 'daemon error', '啟動 daemon', '停止 daemon', 'daemon…—kc-pr-reorgUse when a feature branch has messy interleaved commits that need reorganization into logical groups before PR review.—kc-pr-reviewUse when reviewing a GitHub PR and posting inline review comments. Triggered by PR number, PR URL, 'review this PR', 'review current branch PR'.—kc-pr-review-resolveUse when a GitHub PR has review comments or automated feedback that needs triage, validation, and structured response before pushing fixes.—kc-project-pulseThis skill should be used when the user asks to "update project status", "write pulse update", "draft weekly update", "post project pulse", "project 更新", "寫…—kc-session-handoffUse when user says 'handoff', 'prepare handoff', '準備交接', or when context pressure is high and work state needs preservation before session ends.—kc-session-resumeUse when user says 'resume', 'continue', '繼續', 'pick up where I left off', or mentions a branch name to resume previous work.—kc-statusline-setupUse when the user wants to set up or check their Claude Code statusline with Anthropic usage quota display.—ui-verifyUse when verifying static UI differences — computed CSS values on specific DOM elements, design tokens, theme changes, layout dimensions, pseudo-element…—