Axıs
随笔
技能目录

vellum

Vellum

Router for turning experience into agent assets. Picks the right artifact, then writes the smallest file that works.

Decide First (Artifact Router)

User wants Build Location rule
Reusable procedure invoked by trigger phrases skill dir with SKILL.md personal or project skills/<name>/
Always-on or file-scoped guidance, <50 lines rule file rules/ with description + globs or alwaysApply
Run logic around agent events (before/after tool, shell, subagent) hook (command preferred, prompt for policy) hooks.json + hooks/<name>.sh, narrowest event, JS-regex matcher
Isolated specialist with own system prompt subagent .md agents/<name>.md with name + description
Old .mdc (description only, no globs/alwaysApply) or .md command migrate to skill copy body verbatim, add name/description

One concern per file. If the draft covers two concerns, split it.

SKILL.md Shape

---
name: kebab-case-max-64
description: WHAT it does + WHEN to use it, third person, with trigger terms
---
# Title
## Quick start (essential steps only)
## Additional resources
- [topic guide](references/topic-guide.md)  <!-- placeholder: replace with real files -->

Rules: body <200 lines here (hard cap 500); references one level deep only; forward verbs match file names.

Description Guide

  • Third person: "Reviews diffs for..." not "I can help".
  • Include WHAT + WHEN + 2-4 trigger terms that do not collide with sibling skill descriptions.
  • One disable-model-invocation: true for explicit-only skills (/shell-style, onboarding, router skills).

Degrees of Freedom

Fragility Form
Many valid approaches prose instructions
Preferred pattern, variation ok template / checklist
Must be exact script + validation command

Prefer scripts over generated code when consistency matters.

Anti-Patterns

  • Windows paths (scripts\helper.py); use scripts/helper.py.
  • Option soup ("use A or B or C"); give one default + escape hatch.
  • Time-sensitive claims; put legacy under "Old patterns".
  • Mixed terms; pick one term per concept.
  • Vague names (helper, utils); use processing-pdfs.

Workflow

  1. Discovery: purpose, location, triggers, output shape, examples. Ask once, in one question.
  2. Design: name, description, section outline, supporting files needed.
  3. Implementation: dirs, SKILL.md, references, scripts (executable, command -v checked).
  4. Verification: line budget, description test, one-level refs, discovery test.

Additional Resources