sentinel

Generate tool boundary declarations from an approved routing report. Use when the developer says "boundary", "load tools", "apply routing", "generate boundaries", or after approving a routing report. CRITICAL ROUTING RULE: This skill runs AFTER /sentinel:routing — it requires docs/tool-routing-report.md with status:approved. If no approved routing report exists, tell the user to run /sentinel:routing first. Never run boundary before routing. When NOT to use: For scanning/classifying which skills a project needs, use /sentinel:routing instead. Boundary does not decide which tools to include — it only generates boundary declarations for tools already approved in the routing report. Input: an approved docs/tool-routing-report.md (generated by /sentinel:routing). Output: .claude/rules/tool-boundary.md containing per-tool capability/limitation declarations, chain patterns, and failure behaviors. Preserves manual edits marked with <!-- manual -->. Edge cases: if routing report exists but is not approved, STOPs with guidance. If tool-boundary.md already exists, updates it (preserving manual sections).

Invoke OpenAI Codex CLI (GPT-5.4) non-interactively to get a second opinion, critique, or real-time web search from within a Claude Code session. Use when the user says "ask codex", "call codex", "get codex's opinion", "second opinion from codex", "codex review", or wants to consult Codex on code, architecture, or any technical question. CRITICAL ROUTING RULE: When the user wants Codex to perform a web search (current info, latest versions, recent news), ALWAYS use this skill (--search flag) — never codex:rescue, which cannot do web search. Input: natural-language question, optionally with code context, via stdin heredoc. Output: plain-text analysis from a temp file (or structured JSON via --output-schema). Requires codex-cli installed (`codex` binary in PATH, auth via `codex login`).

Generate a structured progress.yaml session entry with typed Candidates for the compaction promotion pipeline, and optionally a durable session report under docs/sessions/. Use at the end of a session, after completing a task, or when the user says "progress", "log session", "what did we learn", "save lessons". Produces entries that compaction can process into CLAUDE.md (rules) and ARCHITECTURE.md (facts).

Scan global skills against project context and produce a tool routing report for developer review. Use when initializing a project, onboarding new tools, or when the developer says "routing", "scan tools", "which skills do I need", "update tool inventory". Produces docs/tool-routing-report.md and STOPS for human approval before any skills are moved.

Produce submission-ready documents with compliance lint and format rendering. Use when "export", "sentinel-export", "compliance check", "clean for submission", or when the user wants to render project docs to md/pdf/pptx/docx with AI writing pattern detection.