using-agent-skills

Selects and routes tasks to applicable repository skills before agent execution.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill using-agent-skills-jose-polanco-oxte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/using-agent-skills
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill using-agent-skills-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working in this repository need a consistent way to discover which local skills exist and which ones apply to a given task, avoiding invented skill references and missed mandatory workflows. ## Core Features & Use Cases - Skill Selection Contract: Defines a mandatory six-step process for identifying the task type, inspecting the local skill catalog, and loading only relevant SKILL.md files. - Routing Catalog: Maps situations like planning, requirements changes, audits, and subsystem work (Rust, C#, WinUI, graphics, CI/CD) to the correct top-level skills and sub-skills. - Verification and Boundaries: Enforces a verification contract per selected skill and prevents plan skills from being activated for ordinary non-trivial tasks. - Use Case: When asked to modify the Rust DSP engine, the agent consults this skill, selects the rust skill and its applicable sub-skills, records the selection, and runs the required verification before making changes. ## Quick Start Ask the agent to select the applicable repository skills for your task before it begins any consequential work.

Frequently Asked Questions about using-agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose which agent skills apply to a task?▼

Identify the task type, affected subsystem, and requested outcome, then inspect the local skill catalog under .agents/skills/. Select the smallest set of relevant skills, load each SKILL.md completely, and record why each applies.

What skills exist in this repository for coding tasks?▼

The catalog includes routing skills for rust, csharp, dotnet, winui, graphics, windows, scripting, localization, build-full, and ci-cd. Each top-level skill routes to applicable sub-skills that are loaded on demand.

When should the plan skills be activated?▼

Plan skills activate only when the user explicitly asks to author a plan or execute a provided plan. Ordinary non-trivial requests use the relevant direct skills instead; overly broad tasks should prompt the user to authorize plan authoring.

Can an agent reference a skill that is not in the repository?▼

No. The skill explicitly forbids referencing or invoking skill names not present in the repository. If a missing skill would materially change the implementation, the agent must stop and report the gap.

What verification is required after selecting a skill?▼

Every selected skill must produce a concrete verification result. Project changes follow the testing rules in .agents/rules/testing.md, while documentation changes require validating paths, references, scripts, and links.