Authoring skills

​

Anatomy of a skill

skills/figma-agent/<skill-name>/SKILL.md

​

Frontmatter

---
name: accessibility-audit
description: "Audits a design against WCAG 2.2 AA basics that are checkable in Figma: color contrast, text sizing, tap/click target size, focus order, and presence of alt-text-equivalent labels for meaningful icons. Use before a design is considered done."
---

​

Standard sections

• Purpose — one paragraph, plain intent.
• Operating Role — how the skill behaves in Figma (selection-first, evidence-backed, no broad redesign unless asked).
• Supported Context — what the skill uses (selection, page, prototype settings, comments, connectors, code).
• Activation Boundary — when to run it.
• Required Inputs — what the user must supply, and what may be inferred.
• Fast Defaults — the useful-first-pass behavior when context is incomplete.
• Workflow — the numbered steps the skill executes.
• Figma Execution Limits — scoped edits, ambiguity handling, and behaviors the skill must not claim.
• Guardrails — quality-critical behaviors that must not drift.
• Finding Quality Rules — how to phrase findings, evidence, and severity.

​

Scaffold a new skill

uv run python scripts/init_skill.py my-new-skill
# edit skills/figma-agent/my-new-skill/SKILL.md

​

Validate

uv run python scripts/validate_skills.py
uv run python tests/test_skills_catalog.py
uv run ruff check .
uv run ruff format --check .

npx skills@latest add qredence/skills --list

​

Repository conventions

• Use uv for Python commands and ruff for formatting and linting.
• Keep README content user-focused. Maintenance details belong in AGENTS.md.
• Do not add plugin-manager stubs, duplicate agent rules, or archived SKILL.md files.