- Home
- Skills
- Aaronontheweb
- Dotnet Skills
- Skills Index Snippets
skills-index-snippets_skill
- Shell
643
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill aaronontheweb/dotnet-skills --skill skills-index-snippets- SKILL.md4.5 KB
Overview
This skill creates and maintains compact AGENTS.md / CLAUDE.md snippet indexes that route tasks to the correct dotnet-skills skills and agents. It supports both human-readable and compressed Vercel-style snippets so downstream assistants can reliably invoke skills by ID. Use it to remove routing ambiguity and improve retrieval-led reasoning for .NET development tasks.
How this skill works
The skill reads the plugin registry and skill/agent frontmatter to build a task->skill routing index. It outputs either a readable markdown block or a compressed single-line snippet that downstream repos can paste into their AGENTS.md / CLAUDE.md. The snippets instruct assistants to prefer retrieval-led reasoning, list routing categories, and optionally define lightweight quality gates and specialist agents.
When to use it
- When adding, removing, or renaming skills or agents in the plugin registry
- After updating plugin metadata or skill frontmatter names
- When creating copy/paste snippets for downstream repositories
- To provide a compact always-on router so assistants choose the right skill
- When you want a compressed index to save context footprint
Best practices
- Reference skills and agents by their frontmatter IDs, not filesystem paths
- Keep the snippet a router only—avoid embedding long documentation
- Use the compressed format for small context budgets and readable format for developer-facing docs
- Include quality gates for heavy or LLM-authored changes (optional)
- Regenerate snippets after any registry or name changes and validate with the marketplace script
Example use cases
- Add a new efcore-patterns skill and insert it under the Data category in the snippet
- Switch to the compressed Vercel-style block to reduce token usage for hosted assistants
- Create an AGENTS.md in a downstream repo that routes ASP.NET tasks to aspire-service-defaults
- Include dotnet-slopwatch as a post-refactor quality gate for large changes
- Regenerate snippets automatically as part of CI after plugin.json updates
FAQ
Use the plugin registry and each skill/agent frontmatter name field as the source of truth.
Should I use readable or compressed snippets?
Use readable snippets for human-maintained docs and compressed snippets when you need minimal context footprint for downstream assistants.