菜单
Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.
Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.
Turn business data, KPI movement, or experiment results into a clear narrative using the what-so what-now what structure, audience calibration, and action-oriented insight. Use when leaders need a data-backed brief, dashboard storyline, or metric interpretation. Do not use for raw statistical modeling with no communication deliverable.
Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.
Draft clear, professional business emails from rough notes, context, or instructions. Handles cold outreach, internal updates, client responses, and escalation drafts. Use when the work is routine email writing with known context and audience. Do not use for sensitive legal notices, formal regulatory correspondence, or board-level communication without review.
Summarize meeting notes or transcripts into decisions, action items, owners, risks, and follow-up messages. Use after meetings when raw notes need a clean recap.
| name | codexkit-bug-hunt |
| description | Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior. |
| version | 1.0.0 |
| category | verification |
Use this skill when a report says something is broken and you need disciplined debugging rather than guesswork.
| Check | Question |
|---|---|
| Correctness | Are all pass/fail criteria applied against the correct standard or rule? |
| Completeness | Were all required dimensions or checklist items evaluated? |
| Context-fit | Does the verification scope match the actual risk level of the deliverable? |
| Consequence | If this passed verification but had a hidden flaw, what is the worst-case impact? |
