---
name: velin-ai-skill-authoring
description: Author VelinStyle skills with contract fields; reuse existing skills before NEW.
---
# Skill Authoring

## Purpose
Authors new skills with registry-first metadata quality gates.

## Domain
B · category `ai-workflows`

## Capabilities
- `build.meta`

## Permission
`write` · **requiresApproval: true**

## Allowed actions
- READ
- PLAN
- WRITE

## Forbidden actions
- APPLY
- ROLLBACK
- ACCEPT
- DEFER
- NOTE
- ACKNOWLEDGE
- CATALOG
- MANIFEST
- CLASSIFY
- invent-target

## Stop conditions
- SR-11

## Agent role / risk
Author · risk `high`

## Reuse (mandatory before build)

Follow `velin-reuse-gate` (BP-R01…R04):

1. **SEARCH** existing VelinStyle skills, components/Web Components, utilities, tokens, and patterns.
2. **EXISTING?** If a fit exists, document it.
3. **COMPATIBLE?** If yes → **REUSE** (or EXTEND). If no → document the incompatibility.
4. **NEW** only with evidenced gap — never "create because needed".
5. Skipping reuse on non-greenfield work → **STOP** (SR-12).

## Workflow
1. SEARCH registry for existing skill (exact/capability).
2. Prefer REUSE/EXTEND; NEW only with gap evidence (BP-R03).
3. Include domains, permission, allowed/forbidden actions, stopConditions.
4. Never invent Core migrate/rewrite engine behavior in prose.

## Anti-patterns
- Creating a duplicate skill when an ID already matches.

## Inputs / Outputs
- Inputs: markdown, docs, meta-json
- Outputs: markdown, registry-json
