guide-maintenance Skill
Maintain the OpenVMM Guide and its code-sync mapping. Load when: (1) adding, removing, or moving Guide pages, (2) adding new device crates or CLI args that need doc coverage, (3) updating the doc-code-sync mapping table, or (4) auditing Guide freshness against code changes. Published by microsoft in openvmm.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is guide-maintenance Skill?
Maintain the OpenVMM Guide and its code-sync mapping. Load when: (1) adding, removing, or moving Guide pages, (2) adding new device crates or CLI args that need doc coverage, (3) updating the doc-code-sync mapping table, or (4) auditing Guide freshness against code changes. Published by microsoft in openvmm. 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
- Testing
- Testing use cases
Declared skill metadata
- Source file: .github/skills/guide-maintenance/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 guide-maintenance Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/openvmm
- Skill file: .github/skills/guide-maintenance/SKILL.md
What it does
Maintain the OpenVMM Guide and its code-sync mapping. Load when: (1) adding, removing, or moving Guide pages, (2) adding new device crates or CLI args that need doc coverage, (3) updating the doc-code-sync mapping table, or (4) auditing Guide freshness against code changes.
Skill instructions
Guide Maintenance Skill Procedures for keeping the OpenVMM Guide (Guide/src/) in sync with the codebase. The doc-code-sync mapping table is maintained in this skill file; .github/instructions/doc-code-sync.instructions.md contains the instructions and heuristics that are automatically loaded during Copilot code review on .rs and Cargo.toml files. --- Adding a New Guide Page 1. Choose the right location | Content type | Path pattern | |-------------|-------------| | Emulated device reference | reference/emulated/<DeviceCategory/<device.md | | VMBus device reference | reference/devices/vmbus/<device.md | | Virtio device reference | reference/devices/virtio/<device.md | | Device backend reference | reference/backends/<category.md | | Architecture deep-dive | reference/architecture/openvmm/ or reference/architecture/openhcl/ | | CLI / management | reference/openvmm/management/ | | Developer tool | devguide/devtools/<tool.md | | Test framework | devguide/tests/ | 2. Create the page - Follow
Verified compatibility and discovery
Frequently asked questions
What is guide-maintenance?
guide-maintenance is a open-source AI agent skill with Copy skill directory. Maintain the OpenVMM Guide and its code-sync mapping. Load when: (1) adding, removing, or moving Guide pages, (2) adding new device crates or CLI args that need doc coverage, (3) updating the.
Who is guide-maintenance best for?
guide-maintenance is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install guide-maintenance?
Install or run guide-maintenance using Copy skill directory. Check guide-maintenance for the latest setup command.
Is guide-maintenance actively maintained?
guide-maintenance 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.
