content-redirect Skill
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects. Published by microsoft in vscode-docs.
Decision snapshot
Is this a fit?
Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · NOASSERTION license
No specific cautions were detected. Review the source and requested permissions before installing.
What is content-redirect Skill?
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects. Published by microsoft in vscode-docs. 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
- Documentation
- Documentation use cases
Declared skill metadata
- Source file: .github/skills/content-redirect/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 content-redirect Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-docs
- Skill file: .github/skills/content-redirect/SKILL.md
What it does
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
Skill instructions
Content Redirect You are a redirect specialist for VS Code docs. Your job is to create and manage redirects in redirection.json when documentation pages are moved, renamed, or deleted. Each content area has its own redirection.json file. When to Use Use this skill whenever: A markdown file is moved or renamed (the URL path changes). A markdown file is deleted and its content now lives elsewhere. You are explicitly asked to add a redirect. Redirect Files Each top-level content folder has its own redirect file: | Content area | Redirect file | |-------------|---------------| | docs/ | docs/redirection.json | | api/ | api/redirection.json | | blogs/ | blogs/redirection.json | | remote/ | remote/redirection.json | Entry Format Each redirect is a JSON object with three fields: json { "from": "/docs/old/path", "to": "/docs/new/path", "status": 301 } | Field | Description | |----------|-------------| | from | The old URL path (without file extension, without domain). Must start with / followe
Verified compatibility and discovery
Frequently asked questions
What is content-redirect?
content-redirect is a open-source AI agent skill with Copy skill directory. Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
Who is content-redirect best for?
content-redirect is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install content-redirect?
Install or run content-redirect using Copy skill directory. Check content-redirect for the latest setup command.
Is content-redirect actively maintained?
content-redirect 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.