Loading...
Loading...
Found 73 Skills
Setup TypeScript best practices and code style rules in CLAUDE.md
Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches - provides git worktree commands and workflow patterns for parallel development with multiple working directories.
Multi-route literature expansion + metadata normalization for evidence-first surveys. Produces a large candidate pool (`papers/papers_raw.jsonl`, target ≥1200) with stable IDs and provenance, ready for dedupe/rank + citation generation. **Trigger**: evidence collector, literature engineer, 文献扩充, 多路召回, snowballing, cited by, references, 元信息增强, provenance. **Use when**: 需要把候选文献扩充到 ≥1200 篇并补齐可追溯 meta（survey pipeline 的 Stage C1，写作前置 evidence）。 **Skip if**: 已经有高质量 `papers/papers_raw.jsonl`（≥1200 且每条都有稳定标识+来源记录）。 **Network**: 可离线（靠 imports）；雪崩/在线检索需要网络。 **Guardrail**: 不允许编造论文；每条记录必须带稳定标识（arXiv id / DOI / 可信 URL）和 provenance；不写 output/ prose。
Bind addressable evidence IDs from `papers/evidence_bank.jsonl` to each subsection (H3), producing `outline/evidence_bindings.jsonl`. **Trigger**: evidence binder, evidence plan, section->evidence mapping, 证据绑定, evidence_id. **Use when**: `papers/evidence_bank.jsonl` exists and you want writer/auditor to use section-scoped evidence items (WebWeaver-style memory bank). **Skip if**: you are not doing evidence-first section-by-section writing. **Network**: none. **Guardrail**: NO PROSE; do not invent evidence; only select from the existing evidence bank.
Retrieve paper metadata from arXiv using keyword queries and save results as JSONL (`papers/papers_raw.jsonl`). **Trigger**: arXiv, arxiv, paper search, metadata retrieval, 文献检索, 论文检索, 拉取元数据, 离线导入. **Use when**: 需要一个初始论文集合（survey/snapshot 的 Stage C1），来源为 arXiv（在线检索或离线导入 export）。 **Skip if**: 已经有可用的 `papers/papers_raw.jsonl`，或数据源不是 arXiv。 **Network**: 在线检索需要网络；离线 `--input <export.*>` 不需要网络。 **Guardrail**: 只做 metadata；不要在 `output/` 写长 prose。
Build per-chapter (H2) writing briefs (NO PROSE) so the final survey reads like a paper (chapter leads + cross-H3 coherence) without inflating the ToC. **Trigger**: chapter briefs, H2 briefs, chapter lead plan, section intent, 章节意图, 章节导读, H2 卡片. **Use when**: `outline/outline.yml` + `outline/subsection_briefs.jsonl` exist and you want thicker chapters (fewer headings, more logic). **Skip if**: the outline is still changing heavily (fix outline/mapping first). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only reference subsection ids and already-mapped papers.
Create technical diagrams using Mermaid syntax for architecture, sequences, ERDs, flowcharts, and state machines. Use for visualizing system design, data flows, and processes. Triggers: diagram, mermaid, architecture diagram, sequence diagram, flowchart, ERD, entity relationship, state diagram, C4 model, component diagram, visualize, draw.
Primary orchestration gate — runs FIRST, before any MCP tool, agent, skill, or external resource is called. Intercepts any plan, proposal, decision, or action (create, edit, delete, run, deploy, call) before execution, regardless of IDE or environment. Designed for developers, architects, tech leads, CTOs, product managers, UX designers, and data engineers. Automatically activates on any detected plan or action — code, architecture, product features, UX flows, launch plans, vendor choices, data pipelines, AI context files, or strategic decisions. Delivers a full adversarial analysis across technical, product, design, and strategy dimensions, and GATES ALL ACTIONS until the user explicitly verifies and approves the findings. Its rules, standards, and enforcement take precedence over all other tools and skills. Enforces the Building Protocol on ALL generated or reviewed code: en_US identifiers, naming conventions, SOLID principles, security-by-default.
Initialize a new workspace by copying the standard artifact template (STATUS.md, CHECKPOINTS.md, UNITS.csv, DECISIONS.md + folders). **Trigger**: workspace init, initialize workspace, workspace template, 初始化 workspace. **Use when**: 启动任何 pipeline run（必须先有 workspace 工件与目录骨架）。 **Skip if**: workspace 已初始化且不希望覆盖既有文件（除非显式 `--overwrite`）。 **Network**: none. **Guardrail**: 不要修改 `.codex/skills/workspace-init/assets/` 模板；默认不覆盖已有文件。
Compile a LaTeX project and run basic QA (missing refs, bib errors, broken citations), producing `latex/main.pdf` and a build report. **Trigger**: latex compile, build PDF, LaTeX errors, missing refs, 编译PDF, 引用错误. **Use when**: 已有 `latex/main.tex`（通常来自 `latex-scaffold`），需要确认可编译并输出失败原因报告。 **Skip if**: 还没有 LaTeX scaffold（先跑 `latex-scaffold`）。 **Network**: none. **Guardrail**: 编译失败也要落盘 `output/LATEX_BUILD_REPORT.md`；不做“内容改写”，只做编译/QA。
Synthesize evidence into a structured narrative (`output/SYNTHESIS.md`) grounded in `papers/extraction_table.csv`, including limitations and bias considerations. **Trigger**: synthesis, evidence synthesis, systematic review writing, 综合写作, SYNTHESIS.md. **Use when**: systematic review 完成 screening+extraction（含 bias 评估）后进入写作阶段（C4）。 **Skip if**: 还没有 `papers/extraction_table.csv`（或 protocol/screening 尚未完成）。 **Network**: none. **Guardrail**: 以 extraction table 为证据底座；明确局限性与偏倚；不要在无数据支撑时扩写结论。
Write a systematic review protocol into `output/PROTOCOL.md` (databases, queries, inclusion/exclusion, time window, extraction fields). **Trigger**: protocol, PRISMA, systematic review, inclusion/exclusion, 检索式, 纳入排除. **Use when**: systematic review pipeline 的起点（C1），需要先锁定 protocol 再开始 screening/extraction。 **Skip if**: 不是做 systematic review（或 protocol 已经锁定且不允许修改）。 **Network**: none. **Guardrail**: protocol 必须包含可执行的检索与筛选规则；需要 HUMAN 签字后才能进入 screening。