joelhooks Add a skill
Use the installed write-a-skill workflow to create or revise a skill. Resolve source ownership first: standing fleet policy belongs to dark-wizard, runtime services to joelclaw, and project workflows to their project repository. External packs stay upstream-owned unless local curation is requested.
Infer the outcome and trigger from the request. Write concise frontmatter, the domain-specific procedure, its real boundaries, and references needed on demand. Preserve invocation metadata and working scripts. Do not copy global persona, model pins, or general tool manuals into every skill.
An explicit creation request authorizes drafting and checking the skill. Ask only for missing consequential scope. Test instruction changes with bounded comprehension cases and realistic dummy executions when behavior is uncertain. Keep fixtures isolated from real accounts and services.
Inspect installed links before changing them. Use the owning installer and verify that consumers resolve to the intended source. Never replace another session’s worktree or unrelated local edits. Commit only owned changes and record the actual source and installation checks. The former slog journal is retired; durable decisions belong in the project Brain.