rpi-research Skill
Research-only RPI playbook that gathers task evidence, writes dated research artifacts under .copilot-tracking/research/ or a caller's trusted evidence root, and hands off planning-ready findings. Use when the user needs evidence, alternatives, or task framing first. Published by microsoft in hve-core.
Decision snapshot
Is this a fit?
Research, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is rpi-research Skill?
Research-only RPI playbook that gathers task evidence, writes dated research artifacts under .copilot-tracking/research/ or a caller's trusted evidence root, and hands off planning-ready findings. Use when the user needs evidence, alternatives, or task framing first. Published by microsoft in hve-core. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Research
- Research use cases
Declared skill metadata
- Declared license: MIT
- Source file: .github/skills/rpi/rpi-research/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use rpi-research Skill
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/hve-core
- Skill file: .github/skills/rpi/rpi-research/SKILL.md
What it does
Research-only RPI playbook that gathers task evidence, writes dated research artifacts under .copilot-tracking/research/ or a caller's trusted evidence root, and hands off planning-ready findings. Use when the user needs evidence, alternatives, or task framing first.
Skill instructions
RPI Research Goal Produce a dated, human-readable primary research artifact that helps the end user understand the result, challenge the evidence, suggest changes, and make any required decision without planning, implementing, or reviewing. Lead with the summary, material discoveries, findings, and alternatives; keep supporting context with the finding that needs it. Preserve the canonical evidence, decision state, and planning-readiness record beneath that reader-first synthesis. Each executed research cycle completes wider, deeper, and contrarian waves in that order. The artifact, not the chat response, is the durable source of truth. Use templates/research.md as the primary-artifact skeleton. Read references/research.md for detailed research-posture selection, the three-wave cycle, extension registry, optional helpers, participation protocol, evidence contract, and response guidance. Follow the shared conventions in copilot-tracking.instructions.md. When the invoking agent or the us
Verified compatibility and discovery
Frequently asked questions
What is rpi-research?
rpi-research is a open-source AI agent skill with Copy skill directory. Research-only RPI playbook that gathers task evidence, writes dated research artifacts under .copilot-tracking/research/ or a caller's trusted evidence root, and hands off planning-ready findings.
Who is rpi-research best for?
rpi-research is best for reusing agent instructions, scripts, and references, research workflows.
How do I install rpi-research?
Install or run rpi-research using Copy skill directory. Check rpi-research for the latest setup command.
Is rpi-research actively maintained?
rpi-research may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
