content-audit Skill
Audit RVAS delivery session content (tracks, challenges, docs, starter code) for correctness, hallucinations, outdated information, pacing, broken links, and convention violations, then fix what it finds. Verifies claims against official Azure and tooling docs on the internet. Use when asked to 'review the content', 'c Published by microsoft in frontier-ghcp-rvas.
What is content-audit Skill?
Audit RVAS delivery session content (tracks, challenges, docs, starter code) for correctness, hallucinations, outdated information, pacing, broken links, and convention violations, then fix what it finds. Verifies claims against official Azure and tooling docs on the internet. Use when asked to 'review the content', 'c Published by microsoft in frontier-ghcp-rvas. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Documentation
- Security review use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use content-audit Skill
- Use it for security review.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-ghcp-rvas
- Skill file: .github/skills/content-audit/SKILL.md
What it does
Audit RVAS delivery session content (tracks, challenges, docs, starter code) for correctness, hallucinations, outdated information, pacing, broken links, and convention violations, then fix what it finds. Verifies claims against official Azure and tooling docs on the internet. Use when asked to 'review the content', 'c
Skill instructions
Content Audit You are a technical editor and fact-checker for this RVAS delivery session repository. Your job is to find and fix real problems in the content: wrong facts, invented APIs or commands, stale version numbers, broken links, challenges that cannot be finished in the time given, and violations of the repo's own conventions. You verify claims against official documentation on the internet rather than trusting memory. This is an audit, not a rewrite. Change what is wrong or misleading. Leave correct, well-paced content alone. When to Use - A track, challenge, or doc needs a correctness pass before a workshop or release. - Someone suspects hallucinated commands, APIs, package names, or links. - Version numbers, SDKs, or Azure service names may have drifted out of date. - You need to confirm a challenge is realistically completable in its stated time. - Tracks, challenges, starter code, and the root README may be out of sync. Scope and Inputs Before starting, establish scope. If
Explore related resources
Frequently asked questions
What is content-audit?
content-audit is a open-source AI agent skill with Copy skill directory. Audit RVAS delivery session content (tracks, challenges, docs, starter code) for correctness, hallucinations, outdated information, pacing, broken links, and convention violations, then fix what it finds.
Who is content-audit best for?
content-audit is best for reusing agent instructions, scripts, and references, security review workflows, documentation workflows.
How do I install content-audit?
Install or run content-audit using Copy skill directory. Check content-audit for the latest setup command.
Is content-audit actively maintained?
content-audit may need a closer maintenance check before production use.
Auto-fetched from GitHub.
