author-skilllisted

Author a new skill for this repo end to end — take a topic, check for existing coverage, drill the official docs behind it, write a filled handoff brief to docs/handoffs/, then draft the SKILL.md and run the post-draft checks. Use when asked to write, author, create, or scaffold a new skill, or when a drift-audit new-skill candidate has been accepted. Encodes this repo's own conventions rather than generic skill advice — verb naming for behavioral skills and fabric-/pbir-/pbid- prefixes for platform ones, the description as the entire trigger mechanism, long detail split into references/, lint-frontmatter.py, and which tree a new skill belongs in and its deploy step. Drills before it writes and never encodes an unverified claim. Ends at a linted draft plus a fresh-session test plan; writes no test fixtures and does not commit — fixtures and validation are test-skill's, which reads the brief back off disk. To fold a session learning into guidance that already exists, use learn instead.
wardawgmalvicious/agent-config · ★ 1 · AI & Automation · score 80

Install: claude install-skill wardawgmalvicious/agent-config

# Author a skill Take a **topic** and end at a linted `SKILL.md` draft plus a runnable fresh-session test plan. The input is a subject, not a specification — deciding the name, the boundaries, and what the skill deliberately will not cover is the work, not a precondition for it. This skill is house-style. It encodes how *this* repo builds skills; the generic mechanics of the Agent Skills format are somebody else's job (see step 1). Paths below are relative to the repo root. This skill is project scope and fires only in sessions here, but a skill it authors in `skills/` deploys through `~/.claude/skills` — a real directory holding **one junction per skill** in that tree. **An edit is immediate; a new skill needs the linker once.** The asymmetry follows from those per-skill junctions. Editing an already-junctioned skill is live the moment it hits disk, for every session on this machine, committed or not. But a directory that did not exist at the last `scripts/link-claude.ps1` run has **no junction**, so a newly authored skill is invisible everywhere — absent from the listing, and `/<name>` answers `Unknown command`. Measured 2026-09-02: `land` was missing from a listing of 8 junctions immediately after its `SKILL.md` was written, and appeared only once the linker ran. On this machine the form is `./scripts/link-claude.ps1 -SkillGroups workflow,social`, **never bare** — see root `CLAUDE.md`. A **platform** skill is the exception that proves the rule: `fabric` and `powerbi`