Favicon of documentation

documentation Skill

AI Agent SkillDocumentationPowerShellOpen source

Canonical documentation capability for audit, drift, validate, and author modes in hve-core. Published by microsoft in hve-core.

Decision snapshot

Is this a fit?

Best for

Security review, Documentation, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

2 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is documentation Skill?

Canonical documentation capability for audit, drift, validate, and author modes in hve-core. 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.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
77/100

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
  • Security review
  • Documentation
  • Security review use cases
  • Documentation use cases

Declared skill metadata

  • Source file: .github/skills/hve-core/documentation/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use documentation Skill

  • Use it for security review.
  • Use it for documentation.

Built with

PowerShellCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/hve-core
  • Skill file: .github/skills/hve-core/documentation/SKILL.md

What it does

Canonical documentation capability for audit, drift, validate, and author modes in hve-core.

Skill instructions

documentation Overview This skill provides the shared documentation capability used by the Documentation agent. It centralizes the durable knowledge for audit, drift, validate, and author flows in a single package so thin wrappers can load mode-specific guidance instead of embedding capability prose inline. Mode map The Documentation agent should load the relevant skill sections by mode: | Mode | Primary load targets | Notes | |------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| | audit | references/conventions.md, references/coverage-method.md, references/validation-toolchain.md, references/content-sensitivity.md | Replaces the former Doc Ops workflow with a skill-driven audit loop. | | drift | references/conventions.md, references/code-doc-mapping.md, refe

Verified compatibility and discovery

Frequently asked questions

What is documentation?

documentation is a open-source AI agent skill with Copy skill directory. Canonical documentation capability for audit, drift, validate, and author modes in hve-core.

Who is documentation best for?

documentation is best for reusing agent instructions, scripts, and references, security review workflows, documentation workflows.

How do I install documentation?

Install or run documentation using Copy skill directory. Check documentation for the latest setup command.

Is documentation actively maintained?

documentation may need a closer maintenance check before production use.

Share:

Stars
1,263
Forks
229
Last commit
2 months ago
Last verified
Aug 27, 2026
Metadata fetched
Aug 27, 2026
Repository age
10 months
License
MIT

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.

Alternatives to documentation