doc-writer Skill
Guidelines for producing accurate and maintainable documentation for the Aspire documentation site. Use when writing or updating user guides, integration docs, tutorials, custom components used by docs, or documentation-related tests and validation on aspire.dev. Published by microsoft in aspire.dev.
Decision snapshot
Is this a fit?
Deployment, Documentation, Writing, Includes SKILL.md
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 doc-writer Skill?
Guidelines for producing accurate and maintainable documentation for the Aspire documentation site. Use when writing or updating user guides, integration docs, tutorials, custom components used by docs, or documentation-related tests and validation on aspire.dev. Published by microsoft in aspire.dev. 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
- Deployment
- Documentation
- Writing
- Deployment use cases
- Documentation use cases
Declared skill metadata
- Source file: .agents/skills/doc-writer/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 doc-writer Skill
- Use it for deployment.
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aspire.dev
- Skill file: .agents/skills/doc-writer/SKILL.md
What it does
Guidelines for producing accurate and maintainable documentation for the Aspire documentation site. Use when writing or updating user guides, integration docs, tutorials, custom components used by docs, or documentation-related tests and validation on aspire.dev.
Skill instructions
Documentation Writer Skill This skill provides guidelines for AI coding agents to help maintainers produce accurate and easy-to-maintain documentation for the Aspire project. The aspire.dev repository is the official documentation site for Aspire, and this skill helps ensure consistent, high-quality documentation. Documentation Overview Site Structure Location: src/frontend/src/content/docs/ Audience: Developers using Aspire for cloud-native application development Format: Astro with MDX files Build System: Astro (static site generator with Starlight theme) Documentation Categories src/frontend/src/content/docs/ ├── index.mdx Landing page ├── get-started/ Getting started guides │ ├── prerequisites.mdx │ ├── install-cli.mdx │ ├── first-app.mdx │ └── ... ├── app-host/ AppHost documentation ├── architecture/ Architecture concepts ├── dashboard/ Aspire Dashboard docs ├── deployment/ Deployment guides ├── diagnostics/ Diagnostics and telemetry ├── extensibility/ Extensibility guides ├── fun
Verified compatibility and discovery
Frequently asked questions
What is doc-writer?
doc-writer is a open-source AI agent skill with Copy skill directory. Guidelines for producing accurate and maintainable documentation for the Aspire documentation site.
Who is doc-writer best for?
doc-writer is best for reusing agent instructions, scripts, and references, deployment workflows, documentation workflows, writing workflows.
How do I install doc-writer?
Install or run doc-writer using Copy skill directory. Check doc-writer for the latest setup command.
Is doc-writer actively maintained?
doc-writer 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.
