hcom-spawn
召喚其他 client 的 Agent 透過 HCOM 協作時使用:叫一個 Codex 或 Claude 查資料、實作或互相審查,涵蓋模型與 effort 預設、啟動參數與核對、任務交代格式、存活與額度處理、以 tag 收尾。
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
召喚其他 client 的 Agent 透過 HCOM 協作時使用:叫一個 Codex 或 Claude 查資料、實作或互相審查,涵蓋模型與 effort 預設、啟動參數與核對、任務交代格式、存活與額度處理、以 tag 收尾。
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Use when setting up test infrastructure, adding tests, reorganizing test directories, or reviewing test structure. Triggers include creating test files, discussing test strategy, separating unit from integration tests, or when tests need external services like databases or Docker
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
agent 环境安全事件响应:分类→控制蔓延→取证留痕→恢复→复盘的分步处置流程,覆盖密钥泄露、提示注入触发、依赖投毒、未授权操作四类事件,每条处置附命令证据。DSH/agent 环境出现疑似安全事件需要按流程处置与复盘时用;日常开发与例行维护不用。
凭据/密钥暴露审计:gitleaks、trivy 全历史扫描命令与参数、告警误报分级判据、脱敏报告规范、按轮换→撤销→清除历史→CI 门禁排序的修复流程。任务涉及仓库内密钥/token/密码/私钥的检测、历史提交泄露排查、扫描告警真伪判定或泄露报告撰写时用;与凭据无关的常规代码审查不用。
仓库/软件安全审计总览:范围界定→资产清单→风险分级→逐项验证→报告模板的分阶段流程,按需转调 secret-scan、dependency-audit、supply-chain-review、prompt-injection-review 四个专项技能。用户要求整体审计仓库、规划审计步骤或汇总多类发现出报告时用;只查密钥/依赖等单一主题时直接加载对应专项技能,不用本总览。
新功能/新系统的轻量威胁建模:固定对象→划定范围与信任边界→资产清单→STRIDE 逐资产威胁表→攻击树(可选)→缓解与优先级,产出可进设计评审的威胁模型文档。为新功能/新改动做设计阶段安全评审、梳理信任边界或画攻击树时用;与安全边界无关的纯 bug 修复、已有成熟建模流程的团队不展开本流程。
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to \"improve accessibility\", \"a11y audit\", \"WCAG compliance\", \"screen reader support\", \"keyboard navigation\", or \"make accessible\".
Builds an abstraction ladder that moves a problem up ("why / to what end?") and down ("how / what specifically?") to locate the right altitude to work at, then marks one rung as the working level. Use when a problem is stated as a bare solution with an unstated purpose, as a vagu
Produces a clustered theme map that groups many raw notes, observations, quotes, or data points bottom-up into a small set of named, traceable themes (the KJ method). Use when a scattered pile of dozens to hundreds of existing items needs to become a few emergent themes, such as
Produces a structured after-action review by comparing what was expected against what actually happened, diagnosing why the gaps occurred, and converting them into specific owned sustain-and-change actions. Use when a project, launch, sprint, or incident has finished and you want
Catalog captured:2026-11-21