$ loading_
Standardize formatting and writing style for project Markdown documentation.
The material indicates this is a prompt-only Markdown style guide with no keys, no remote endpoints, and no declared execution or data access capabilities, so overall risk is low. Supply-chain confidence is somewhat limited because, although it is open-source on GitHub, community adoption and maintenance signals are weak.
The material explicitly states that no keys or environment variables are required; there is no indication of token collection, storage, or delegated credential use, so credential exposure and misuse risk is low.
No remote endpoints or network behavior are declared, and the content is limited to documentation formatting and writing rules; based on the material, there is no visible path for user data exfiltration.
This is a prompt-only/style-guide skill, and the material does not describe spawning local processes, running scripts, invoking system commands, or any other code execution capability.
The skill description only constrains wording and structure when generating or editing Markdown documents; it does not declare permissions to read, write, or traverse local files, or access external data sources.
The source is an open-source GitHub repository, which materially lowers risk because the code/content is in principle auditable; however, the license is undeclared, it has 0 stars, and maintenance status is unknown, so there is some supply-chain uncertainty due to limited maturity and maintenance signals.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "documentation-style" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/documentation-style/SKILL.md 2. Save it as ~/.claude/skills/documentation-style/SKILL.md 3. Reload skills and tell me it's ready
Please rewrite this README following the documentation-style rules. Standardize heading levels, list formatting, callout styles, and tone while preserving all original information.
A README with consistent formatting, clear structure, and project-aligned documentation style.
Please edit this installation guide to match the documentation-style rules. Improve paragraph organization, step phrasing, and Markdown formatting without changing the technical meaning.
A more readable installation document with clear steps and consistent Markdown formatting.
Please review and revise this project knowledge base article, using documentation-style to standardize terminology, heading names, link style, and example formatting.
A maintainable knowledge base article with consistent terminology and unified style.
This guide defines standards for all documentation generated in the project.
#<number> in free text (e.g., "#1 priority", "#3 option"). Azure DevOps automatically converts #<number> into a work item link. Use "first", "third option", or rephrase the sentence.For diagram design, review, tool selection (Mermaid vs Draw.io), and platform rendering rules, use the diagram-design skill.
Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Systematically triage failures and fix broken builds or unexpected runtime issues.
Guide users to co-author docs, proposals, and specs through iterative refinement.
Turn Markdown into production-ready documentation sites in seconds.
Generate a structured .instructions.md file for project rules or conventions.
Format Chinese Word documents into polished, consistent, professional layouts quickly.
Convert Markdown into styled Word documents with customizable formatting and layout.
Collaboratively manage project docs, decisions, todos, pitfalls, and interfaces with AI.