メニュー
Research and monitoring protocol for Rust projects: dependency health, security advisories, competitive parity, innovation research, issue filing. Used by the rust-researcher agent.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate a continuous improvement cycle: spawn rust-live-tester for live testing, rust-researcher for dependency monitoring and research, rust-arch-analyst for code quality and architecture review, and rust-security-analyst for vulnerability scanning. Aggregates findings and produces a cycle summary.
Initialize a Rust project for the rust-agents plugin: scaffold .local/ working directories, .claude/rules/ project rules, testing knowledge base, and .gitignore. Run once when starting a new project.
Vulnerability and security-hardening audit protocol for Rust projects. Activates expert knowledge across dependency advisories, unsafe code, secret exposure, injection and input validation, cryptography misuse, authentication and authorization, panic-based denial of service, and supply-chain trust. Called by rust-security-analyst at startup via Skill(...). When invoked directly as /security-audit [focus], the current session runs the audit without spawning subagents.
Reference for stable Rust APIs added in versions 1.89 through 1.97 (August 2025 - July 2026). Use this skill whenever writing, reviewing, or refactoring Rust code — especially when you notice patterns that were verbose before newer APIs existed, when MSRV allows it, or when the user mentions modernizing Rust code, upgrading MSRV, or using "the latest Rust features". Also trigger when reviewing Rust code for improvements, migrations, or when a user asks "can this be simpler in modern Rust?" Proactively suggest newer APIs when you see patterns like manual UTF-8 truncation, path extension manipulation, advisory file locking via external crates, ignoring `retain` removal results, verbose `try_into().unwrap()` for fixed arrays, `compare_exchange` loops for atomic update, `cfg_if` crate usage, matching `0`/`1` to `bool`, `assert!(matches!(...))` in tests, or hand-rolled bit-manipulation idioms like `1 << (BITS - 1 - x.leading_zeros())`.
Debug Rust issues using a multi-agent investigation team. Workflow: debugger + live-tester (conditional) investigate root cause in parallel → security review always, architect and perf reviews conditionally → code reviewer consolidates findings → results presented to user. Requires rust-agents plugin and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Orchestrate Rust development using agent teams with peer-to-peer communication. Use when: 'create rust team', 'start team development', 'launch agent team', 'team workflow', 'collaborative development'. Requires rust-agents plugin and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
| name | research-protocol |
| description | Research and monitoring protocol for Rust projects: dependency health, security advisories, competitive parity, innovation research, issue filing. Used by the rust-researcher agent. |
| argument-hint | [dependencies|research|parity|full] |
Monitor the project's dependency health, track the competitive landscape, and surface new techniques that could benefit the project. File GitHub issues for every actionable finding.
Focus: $ARGUMENTS (default: full — all phases)
Read all reference files before starting:
sdd agent before filingCargo.toml dependency versions.local/testing/ and .local/specs/dependencies, full)cargo outdated --workspace # Version drift
cargo deny check advisories # Security advisories (RUSTSEC)
Update priority and issue filing — see Research Protocol.
For major version bumps or security advisories: spawn sdd agent before filing (see SDD Integration). Routine patch/minor updates: file directly.
research, full)Search for new techniques relevant to the project's domain:
For each finding:
sdd agent to produce a spec (all research findings require a spec)parity, full)Identify reference projects in the same domain, review their recent changelogs, and assess capability gaps. See Research Protocol for the full scan procedure.
Parity gap severity:
Update .local/testing/playbooks/competitive-parity.md after each scan.
Before finishing:
.local/testing/process-notes.md