Borrowing it
Nothing to install: this file belongs to SilenceInsect/AIDocxWorkFlow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SilenceInsect/AIDocxWorkFlow/main/.cursor/skills/aidocx-s1-review/SKILL.mdgit clone --depth 1 https://github.com/SilenceInsect/AIDocxWorkFlowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/silenceinsect/aidocxworkflow/aidocx-s1-review)<a href="https://agentmods.dev/skills/silenceinsect/aidocxworkflow/aidocx-s1-review"><img src="https://agentmods.dev/badge/skills/silenceinsect/aidocxworkflow/aidocx-s1-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/silenceinsect/aidocxworkflow/aidocx-s1-review"><img src="https://agentmods.dev/badge/skills/silenceinsect/aidocxworkflow/aidocx-s1-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00173 | $0.04971 |
| Opus 5 | $0.00086 | $0.02485 |
| Sonnet 5 | $0.00035 | $0.00994 |
| Haiku 4.5 | $0.00017 | $0.00497 |
Grade A, and why
aidocx-s1-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDocxWorkFlow S1 — 需求评审
独立阶段：可单独调用。丢入材料 → 审查材料 → [合格] 开始评审产出 / [不合格] 生成失败报告。
阶段定位
S1 需求评审（AI：发现问题）
↓ S1 产出 clarification_checklist.md（含 P0/P1/P2 未闭环问题）
S1.5 需求澄清（人工：给出决策）
↓ S1.5 产出 exit_permission.json（含 can_proceed_to_s2 判定）
S2 需求拆解（AI：执行拆解）
S1 本质：AI 审查需求、发现问题、输出 4 份核心硬性产出（gm_commands.md / test_coverage.md / planning_acceptance.md / quality_loop_report.md）+ clarification_checklist.md（待人工决策的问题清单）。不直接给出答案，问题闭环交给 S1.5 人工决策。
4 份核心硬性产出不经过 S1.5，直接进入 S2。S1.5 只接收 clarification_checklist.md。
阶段入口
触发：/aidocx-s1-review + 需求文件，不接受纯文本粘贴
支持的文件格式：
| 格式 | 处理方式 | 产出 |
|---|---|---|
.docx / .doc |
run_s1_pipeline() 解析 + OCR + 图片归档 |
extracted_text.md + image_index.json + extracted_images/ + ocr_results/ |
.md |
直接进入评审，跳过 OCR | 直接进入质量闭环评审 |
.txt |
直接进入评审，跳过 OCR | 直接进入质量闭环评审 |
物料门禁失败（文件不存在 / 不可解析 / 解析后正文 < 50 字）：
- 不进入质量闭环评审
- 直接生成
fail_report_S1.md（仅含"失败原因 = 物料缺失"一段） - 停止流水线
执行步骤
步骤 1：物料门禁检查
from ai_workflow.requirement_reviewer_auto import check_material_gate
gate = check_material_gate(requirement_text)
# gate["gate_passed"]: True = 进入 S1 LLM 评审 / False = 物料门禁失败
步骤 2：识别 PURCHASE_STRONG 功能
扫描需求文档，识别含以下子项的功能：
| 子项 | 典型功能点 |
|---|---|
| 发奖 | 邮件 / 背包 / 资产生成 / 补发 / 补偿 |
| 排行 | 个人榜 / 团队榜 / 赛季榜 / 服务端权威榜 |
| 订单 | 充值 / 退款 / 对账 / 发票 / 风控拦截 |
| 兑换 | 商店 / 兑换码 / 补款 / 限时礼包 |
| VIP | VIP 等级 / 月卡 / 季卡 / 永久卡 / 状态机失效 |
| 战令 | 多档位发奖 / 经验计算 / 等级解锁 |
步骤 3：验证 3 段完整性
对于每个 PURCHASE_STRONG 功能，验证是否存在以下 3 段：
| 段 | 查找内容 |
|---|---|
| 程序自测点 | GM 命令 / 测试脚本 / 沙盒入口 |
| 测试覆盖 | 测试场景列表（正例/反例/边界/异常） |
| 策划验收 | 数值表比对 / 抽检比例 |
步骤 4：生成核心硬性产出
必须生成以下 4 份文件：
gm_commands.md— 程序自测点 GM 命令清单test_coverage.md— 测试覆盖矩阵planning_acceptance.md— 策划验收方案quality_loop_report.md— 质量闭环报告
步骤 5：按需生成中阶/高阶产出
| 产出类型 | 条件 | 文件 |
|---|---|---|
| 中阶优化 | 按需 | role_definitions.md / requirement_objects.md / clarification_checklist.md |
| 高阶质量 | 资深测试 | testability_assessment.md / edge_cases.md / review_issues.md |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 501 lines · 173 tokens per session scan A d186198cbbbc
aidocx-s1-review is a skill published in the GitHub repository SilenceInsect/AIDocxWorkFlow (2 stars, last pushed 1mo ago), licensed MIT. It adds 173 tokens to every session and 4,971 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…