update-skill

<% if (standards.skills) { -%>

Manage Skills (.agents/skills)

In this project, skills are the project's own .agents/skills/<name>/ folders (standards in the uac config), in the Agent Skills format. Codex, Cursor and Copilot read them as they are; uac generate copies them to Claude's skills folder.

Finding Existing Skills

List directories in .agents/skills/. Each is a skill with a SKILL.md; read its frontmatter to see what it does. A skill whose metadata has managed-by: universal-ai-config is uac's own: don't edit it, since uac seed meta-instructions overwrites it.

Deciding What to Do

• Create new: when the task/workflow is distinct from existing skills
• Update existing: when a skill covers similar ground but needs changes — modify its SKILL.md or supporting files
• Delete: remove the entire skill directory when a skill is obsolete

Creating a New Skill

1. Create .agents/skills/{skill-name}/: lowercase letters, digits and hyphens, at most 64 characters.
2. Create SKILL.md inside it with frontmatter and instructions.
3. Optionally add supporting files (references, scripts, assets) in the same folder, and reference them from SKILL.md.

Frontmatter Fields

Use the Agent Skills fields as the tools read them: name (matches the folder), description (required, at most 1024 characters: what it does and when to use it), license, compatibility, metadata (string values), allowed-tools. Tool-specific fields such as disable-model-invocation, user-invocable or argument-hint work where a tool knows them and are ignored elsewhere. No EJS and no per-target overrides: every tool reads the same file. uac warns when a skill breaks the Agent Skills spec.

Example

---
name: create-component
description: Scaffold a new React component with tests and styles. Use when asked to add a component.
argument-hint: "[component-name]"
---

Create a new React component named $ARGUMENTS:

1. Create the component file in src/components/
2. Add unit tests
3. Add a Storybook story
4. Export from the components index