菜单
Create or update a Savitar provenance log entry for clean-room work. Use when a feature depends on external documentation, parity targets, third-party products, or public APIs and the repo needs an auditable record of what was consulted.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Plan or revise Savitar architecture, ADRs, contracts, system boundaries, phase sequencing, or multi-surface integration. Use when scoping features, defining interfaces, or breaking work into clean-room milestones.
Add or change a Savitar model route, MCP server, transport, browser automation feature, or memory workflow. Use when implementing new integrations, extending contracts, or wiring new capabilities into the runtime.
Design or refine the Savitar persona. Use when defining speech patterns, public bio, reply style, identity consistency, or human-conversational behavior across CLI, messaging, and web surfaces.
Review Savitar for security risks. Use when working on public web UI, Google auth, messaging transports, remote execution, MCP/tool safety, secret handling, or prompt-injection-resistant workflows.
Test or validate Savitar runtime changes. Use when adding unit tests, doctor checks, CI coverage, regression validation, or release-readiness checks.
Design or extend Savitar messaging transports and the shared gateway. Use when working on Discord, WhatsApp, iMessage, message normalization, delivery flows, or channel identity policy.
| name | savitar-provenance |
| description | Create or update a Savitar provenance log entry for clean-room work. Use when a feature depends on external documentation, parity targets, third-party products, or public APIs and the repo needs an auditable record of what was consulted. |
| argument-hint | Describe the feature or workstream that needs a provenance entry |
./assets/entry-template.md into a new file under docs/provenance/.