shynlee04/hivemind-plugin/hf-l2-use-authoring-skills

Claude Code and agent skill by shynlee04/hivemind-plugin

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

This skill should be used when the user asks to "create a skill", "audit this skill", "refactor skills", "doctor agent skills", "check skill quality", "fix frontmatter", "skill pattern selection", "TDD for skills", "cross-platform skill compatibility", or "score skill quality".

Install

npx vskill@latest install shynlee04/hivemind-plugin/hf-l2-use-authoring-skills

SKILL.md

The Iron Law

NO SKILL WITHOUT TRIGGER PHRASES IN THE DESCRIPTION

<files_to_read> .opencode/skills/use-authoring-skills/references/01-skill-anatomy.md .opencode/skills/use-authoring-skills/references/02-frontmatter-standard.md .opencode/skills/use-authoring-skills/references/03-three-patterns.md .opencode/skills/use-authoring-skills/references/05-skill-quality-matrix.md .opencode/skills/use-authoring-skills/scripts/validate-gate.sh .opencode/skills/use-authoring-skills/scripts/validate-skill.sh .opencode/skills/use-authoring-skills/scripts/check-overlaps.sh .opencode/get-shit-done/references/thinking-models-execution.md </files_to_read>

The description is the ONLY thing the agent sees before deciding to load a skill. If it doesn't contain specific phrases a user would say, the skill is invisible. Dead on arrival.

Not "the description should be good." The description IS the skill. Without it, nothing else matters.

What agents actually rationalize
What agents sayReality
"The description is clear enough"It says "provides guidance for skill development." Agent will never load it.
"I'll add trigger phrases later"Later never comes. The skill sits dead until someone audits it.
"The references are too long, I'll summarize"References ARE the value. SKILL.md points to them. Summarizing = losing knowledge.
"This skill needs another skill to work"Standalone contract. Push to load, don't require. If it can't work alone, it's not a skill — it's a chapter.
"The script stub exits 0 so validation passes"A stub that always passes is a lie. Remove it or make it real.
"I'll keep the dead reference, it might be useful later"Dead references are debt. The agent will try to load them, fail, and move on.

HIERARCHY ENFORCEMENT — Run This FIRST

This skill is LAYER 4 in the loading chain (domain execution). Before any action:

  1. Verify hierarchy chain:

``bash bash scripts/verify-hierarchy.sh use-authoring-skills `` This checks that meta-builder exists and routed to this skill.

  1. Register this skill as loaded:

``bash bash scripts/register-skill.sh use-authoring-skills ``

  1. Prerequisites:
  • meta-builder must exist (routing source)
  • Background skills should already be loaded by upstream skills

If hierarchy check fails → STOP. This skill should only be loaded after meta-builder routing.

Use Authoring Skills

MANDATORY FIRST STEP — Run This Before Anything Else

Every time this skill loads, run the preflight validator immediately:

bash
bash scripts/validate-gate.sh <create|edit|audit> "<user-request>" <skill-dir>
  • <create> — building a new skill from scratch or from a document
  • <edit> — modifying an existing skill
  • <audit> — reviewing/grading an existing skill
  • <user-request> — the user's exact words in quotes
  • <skill-dir> — directory where the skill lives (default: .)

If this exits non-zero, you are BLOCKED. Fix the reported issue and re-run. Do not proceed to any other step until Gate 0 passes.

Step-by-Step Checklist (Follow In Order)

Copy this checklist into task_plan.md and check off each item as you complete it. You may not skip steps.

- [ ] STEP 1: Run validate-gate.sh — must exit 0
- [ ] STEP 2: Run decision tree below — pick ONE path
- [ ] STEP 3: Load the ONE matching reference file (not all)
- [ ] STEP 4: Ask questions if unclear (max 3, question tool only)
- [ ] STEP 5: Write frontmatter — run validate-skill.sh
- [ ] STEP 6: Write body — follow agentskills.io principles (see below)
- [ ] STEP 7: Run validate-skill.sh — if FAIL, fix and repeat STEP 7
- [ ] STEP 8: Run check-overlaps.sh — if FAIL, fix and repeat STEP 8
- [ ] STEP 9: Dispatch critic subagent for review — if FAIL, fix and repeat STEP 9
- [ ] STEP 10: Final validate-gate.sh re-run — must exit 0

Decision Tree — Pick Your Path

User says... → Load
─────────────────────────────────────────────────────────
"create a skill" / "make a skill" → references/03-three-patterns.md
"create a skill like this @file" → references/03-three-patterns.md (template path)
"audit this skill" / "review skill" → references/05-skill-quality-matrix.md
"fix triggers" / "skill not loading" → references/11-description-optimization.md
"improve this skill" / "refactor" → references/07-iterative-refinement.md
"skill overlaps with..." → references/08-conflict-detection.md
"write evals for skill" → references/10-eval-lifecycle.md
"write scripts for skill" → references/09-script-authoring.md
"make skill work on X platform" → references/06-cross-platform-activation.md
"doctor" / "what's wrong with..." → references/12-anti-deception.md

Rule: Load only ONE reference file from the decision tree. Do not load all references.

agentskills.io Principles (Apply During STEP 6)

These are the core design principles from agentskills.io. Apply them when writing skill content:

  1. Procedures over declarations — Teach HOW to do something, not WHAT something is. Use imperative verbs: "Run this script", "Check the output", "If X, do Y". Avoid: "This skill handles...", "The agent should...".
  1. Defaults, not menus — Pick one approach as the primary path. Mention alternatives in one sentence. Do not present 5 options and ask the agent to choose. Example: "Use bash scripts/validate-skill.sh to validate. For Python-only skills, pytest is an acceptable alternative."
  1. Match specificity to fragility — Be prescriptive for fragile steps (file formats, YAML syntax, tool invocation). Be flexible for creative steps (body content, examples). Frontmatter format = prescriptive. Example scenarios = flexible.
  1. Checklists for multi-step workflows — Any workflow with 3+ steps must be a checklist with [ ] items. Agents check items off as they go.
  1. Validation loops — Every significant action follows: do → validate → fix → repeat. Never declare done without running the validator.
  1. Bundle scripts in scripts/ — Reusable validation, initialization, and cleanup logic lives in scripts/. Reference them from SKILL.md, don't inline shell commands.

Validation Loop (STEP 7–9)

After writing skill content, enter this loop:

LOOP START:
1. Run: bash scripts/validate-skill.sh <skill-dir>
2. If exit code ≠ 0:
- Read the FAIL messages
- Fix each issue
- Go to step 1
3. Run: bash scripts/check-overlaps.sh <skill-dir>
4. If exit code ≠ 0:
- Read overlap warnings
- Resolve conflicts
- Go to step 3
5. Dispatch critic subagent:
- Task: "Review this skill against agentskills.io principles"
- Pass: skill-dir path + the agentskills.io principles from this file
- If critic reports issues → fix them → go to step 1
6. All checks passed → exit loop
LOOP END

Maximum iterations: 5. If the loop hasn't passed after 5 iterations, stop and report what's blocking.

Question Enforcement (STEP 4)

When intent is unclear:

  • Maximum 3 questions per session. Not 4. Not "just one more."
  • Use the question tool only. Do not ask questions in plain text output.
  • Wait for answers before proceeding to implementation.
  • If still unclear after 3 questions, proceed with the most reasonable default and document the assumption in task_plan.md.

Gate System

GateWhenCriteriaEnforcement
G1: IntentBefore any workUser intent in task_plan.md Goal fieldvalidate-gate.sh checks Goal non-empty
G2: StructureBefore writing bodySKILL.md frontmatter has name + descriptionvalidate-skill.sh checks frontmatter
G3: PatternBefore body contentPattern (P1/P2/P3) selected in task_plan.mdvalidate-gate.sh checks pattern field
G4: QualityBefore declaring doneQuality score ≥ 3/5 on all 5 dimensionsgate-enforce.sh G4 runs scoring
G5: ValidationFinal stepvalidate-skill.sh + check-overlaps.sh both passvalidate-gate.sh re-run
G6: Subagent ReviewAfter G5Critic subagent review passesManual dispatch + loop

Run enforcement: bash scripts/validate-gate.sh <action> "<request>" <dir> — exits non-zero if blocked.

Worked Example: Document → Skill Conversion

Input: User provides a 200-line markdown command file to convert into a skill.

STEP 1: bash scripts/validate-gate.sh create "Convert this command file into a skill" . → exits 0, creates task_plan.md.

STEP 2: Decision tree → "create a skill like this @file" → load references/03-three-patterns.md.

STEP 3: Pattern decision: focused how-to guide → P2 (balanced depth). Record in task_plan.md.

STEP 4: Questions if needed (max 3 via question tool).

STEP 5: Write frontmatter:

yaml
---
name: hf-l2-use-authoring-skills
description: Synthesizes Repomix-packed codebase analysis into structured research reports with citations. Use when the user asks to analyze a codebase deeply, create research reports from Repomix output, or synthesize findings from multiple code sources.
---

Run bash scripts/validate-skill.sh . → passes.

STEP 6: Write body following agentskills.io principles (procedures, defaults, checklists).

STEP 7–9: Validation loop → validate-skill.sh → check-overlaps.sh → critic subagent → all pass.

STEP 10: bash scripts/validate-gate.sh create "Convert this command file into a skill" . → exits 0.

Output: Complete skill at target directory with references/ and scripts/.

Anti-Patterns — With Detection

Anti-PatternDetectionCorrection
Phantom dependencies — referencing skills that don't existgrep -r "skill(" SKILL.md references/ → verify each existsRemove or create the missing skill
Identity crisis — P1 router with P3 depth contentCount lines: >300 in SKILL.md = likely P3 masqueradingSplit into thin SKILL.md + reference files
Unenforceable gates — claims "programmatic" with no scriptsls scripts/ → must have validate-gate.sh + validate-skill.shCreate enforcement scripts or remove gate claims
Template TDD mismatch — forcing RED phase on template conversionCheck task type: if "convert document" → skip REDUse template-driven workflow
Banned field usage — compatibility in frontmattergrep "compatibility:" SKILL.mdRemove per agentskills.io spec
Skipping validation loop — declaring done without running validatorsCheck task_plan.md: STEP 7–9 uncheckedRun the loop before claiming complete

Platform Adaptation

PlatformSkill LocationHook FormatNotes
OpenCode.opencode/skills/<name>/SKILL.mdopencode.json hooksUse skill tool to load
Claude Code.claude/skills/<name>/SKILL.md.claude/hooks/Same frontmatter spec
Codex.codex/skills/<name>/SKILL.md.codex/hooks/May need allowed-tools field
Cursor.cursor/skills/<name>/SKILL.md.cursor/rules/Frontmatter may vary

Always write frontmatter per agentskills.io spec — it is the lowest common denominator.

Scripts

All 8 scripts passed audit — each has real validation logic, exits non-zero on failure, and contains no placeholder/TODO text. Unlike stub scripts (which exit 0 always), these enforce actual constraints.

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 91 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
51
Repository forks
17
Repository npm downloads, 7 days
48
7-day trend score
30

Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 17 Jun 2026, 4 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/shynlee04/hivemind-plugin/hf-l2-use-authoring-skills/badge)](https://verified-skill.com/skills/shynlee04/hivemind-plugin/hf-l2-use-authoring-skills)

Something wrong with this skill or its page? Tell us.