From 672fd25890bd980ace9369f9ba08bcf3a1fb0e97 Mon Sep 17 00:00:00 2001
From: Defame1297 <gitea@rkdr.net>
Date: Mon, 22 Jun 2026 18:50:00 +0000
Subject: [PATCH] feat(kyberforge): replace write-skill with spec-compliant
 skill-write and add skill-audit
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Rewrote the skill authoring factory skill from scratch against the agentskills.io
specification. Renamed write-skill → skill-write (name now matches directory per spec).

skill-write:
- Full scaffold via new-skill.sh (annotated templates for SKILL.md, README.md,
  scripts/, references/, assets/)
- validate.sh checks all spec constraints deterministically (name format/length,
  description length, placeholder detection, line count, script rules)
- SKILL.md body includes description rules, body discipline, patterns, and scripts
  guidance with "why" rationale throughout
- Templates usable standalone by agents and humans

skill-audit:
- Structural validation (via validate.sh) + seven qualitative dimensions
- Produces PASS/FAIL/SUGGESTION punch list with per-FAIL fix proposals
- Report-only: does not apply fixes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../kyberforge/skills/skill-audit/README.md   |  29 +++
 .../kyberforge/skills/skill-audit/SKILL.md    | 112 +++++++++++
 .../kyberforge/skills/skill-write/README.md   |  63 ++++++
 .../kyberforge/skills/skill-write/SKILL.md    | 151 +++++++++++++++
 .../skill-write/assets/templates/README.md    |  53 ++++++
 .../skill-write/assets/templates/SKILL.md     | 101 ++++++++++
 .../assets/templates/assets/README.md         |  29 +++
 .../assets/templates/references/README.md     |  31 +++
 .../assets/templates/scripts/README.md        |  47 +++++
 .../skills/skill-write/scripts/new-skill.sh   |  87 +++++++++
 .../skills/skill-write/scripts/validate.sh    | 179 ++++++++++++++++++
 .../skills/write-skill/CATEGORIES.md          |  16 --
 .../skills/write-skill/META-TEMPLATE.md       |  27 ---
 plugins/kyberforge/skills/write-skill/META.md |  16 --
 .../skills/write-skill/SKILL-TEMPLATE.md      |  93 ---------
 .../kyberforge/skills/write-skill/SKILL.md    |  98 ----------
 .../skills/write-skill/evals/eval.yaml        |  69 -------
 17 files changed, 882 insertions(+), 319 deletions(-)
 create mode 100644 plugins/kyberforge/skills/skill-audit/README.md
 create mode 100644 plugins/kyberforge/skills/skill-audit/SKILL.md
 create mode 100644 plugins/kyberforge/skills/skill-write/README.md
 create mode 100644 plugins/kyberforge/skills/skill-write/SKILL.md
 create mode 100644 plugins/kyberforge/skills/skill-write/assets/templates/README.md
 create mode 100644 plugins/kyberforge/skills/skill-write/assets/templates/SKILL.md
 create mode 100644 plugins/kyberforge/skills/skill-write/assets/templates/assets/README.md
 create mode 100644 plugins/kyberforge/skills/skill-write/assets/templates/references/README.md
 create mode 100644 plugins/kyberforge/skills/skill-write/assets/templates/scripts/README.md
 create mode 100755 plugins/kyberforge/skills/skill-write/scripts/new-skill.sh
 create mode 100755 plugins/kyberforge/skills/skill-write/scripts/validate.sh
 delete mode 100644 plugins/kyberforge/skills/write-skill/CATEGORIES.md
 delete mode 100644 plugins/kyberforge/skills/write-skill/META-TEMPLATE.md
 delete mode 100644 plugins/kyberforge/skills/write-skill/META.md
 delete mode 100644 plugins/kyberforge/skills/write-skill/SKILL-TEMPLATE.md
 delete mode 100644 plugins/kyberforge/skills/write-skill/SKILL.md
 delete mode 100644 plugins/kyberforge/skills/write-skill/evals/eval.yaml

diff --git a/plugins/kyberforge/skills/skill-audit/README.md b/plugins/kyberforge/skills/skill-audit/README.md
new file mode 100644
index 0000000..7491031
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-audit/README.md
@@ -0,0 +1,29 @@
+# skill-audit
+
+Audit a skill directory against the agentskills.io specification. Runs structural validation then a qualitative review across description quality, body discipline, formatting, file structure, and internal consistency.
+
+## What it does
+
+1. Runs `validate.sh` from `skill-write` for structural checks (name format, description length, line count, placeholder detection, script rules)
+2. Reads all files in the skill directory
+3. Applies qualitative checks across seven dimensions
+4. Outputs a PASS/FAIL/SUGGESTION punch list with a specific fix proposal for every FAIL
+
+## Usage
+
+```
+/skill-audit
+```
+
+Provide the path to the skill directory to audit when invoking.
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `SKILL.md` | Skill instructions for agents |
+| `README.md` | This file |
+
+## Dependencies
+
+Requires `skill-write` to be installed at `plugins/kyberforge/skills/skill-write/` for the structural validation step. If not present, the agent performs structural checks manually.
diff --git a/plugins/kyberforge/skills/skill-audit/SKILL.md b/plugins/kyberforge/skills/skill-audit/SKILL.md
new file mode 100644
index 0000000..2e4db4b
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-audit/SKILL.md
@@ -0,0 +1,112 @@
+---
+name: skill-audit
+description: >
+  Audit a skill directory against the agentskills.io specification — structural
+  checks plus qualitative review of description quality, body discipline, formatting,
+  file structure, and internal consistency. Produces a PASS/FAIL/SUGGESTION punch
+  list with a specific fix proposal for every FAIL. Use when the user wants to
+  review a skill they wrote, says "audit this skill", "check if my skill follows
+  best practices", "review my SKILL.md", or wants to know if a skill is ready to
+  ship — even if they don't use the word "audit". Do not use to run evals, fix
+  application code bugs, or perform general code review unrelated to skill quality.
+allowed-tools: Bash Read
+metadata:
+  category: factory
+---
+
+## Step 1 — Structural validation
+
+Locate the `validate.sh` script from `skill-write`:
+
+```bash
+bash plugins/kyberforge/skills/skill-write/scripts/validate.sh <skill-dir>
+```
+
+If `validate.sh` is not found, note it and proceed — perform the checks it would cover manually.
+
+List every FAIL from the structural check in the punch list before continuing.
+
+## Step 2 — Read all skill files
+
+Read every file in the skill directory: `SKILL.md`, `README.md` (if present), all files in `scripts/`, `references/`, and `assets/`. Do not skip files — internal consistency checks require the full picture.
+
+## Step 3 — Qualitative audit
+
+Work through each dimension. Cite file and line number for every finding.
+
+### Description
+
+- **Imperative phrasing**: does it use "Use when..." not "This skill..."?
+- **Specificity**: are capabilities stated precisely ("parses OpenAPI specs") or vaguely ("helps with APIs")?
+- **Indirect triggers**: does it cover cases where the user doesn't name the domain directly?
+- **Near-miss exclusions**: are "Do not use when..." clauses present if a near-miss skill could steal activations?
+- **Length**: under 1024 characters?
+
+### Body discipline
+
+For each sentence in the body, apply: *"Would the agent get this wrong without this sentence?"* Flag any that answer "no" as padding.
+
+- **Defaults not menus**: every decision point gives one default + one escape hatch, not a list of options
+- **Why rationale**: include/exclude rules explain why, not just what
+- **Control calibration**: prescriptive for fragile or critical sequences; flexible where multiple approaches are valid
+
+### Patterns
+
+Check each pattern is appropriate and correctly formed:
+
+- **Gotchas**: placed near the top; each entry is a specific fact that defies a reasonable assumption — not a general tip
+- **Prescriptive sequence**: inner code fences escaped as `\`\`\`` when nested inside a markdown block
+- **Checklists**: used for multi-step workflows, not single steps
+- **Conditional references**: specific trigger stated ("If X, read `references/file.md`") — not a generic "see references/"
+- **Output templates**: present when the agent must produce a specific format; absent otherwise
+
+### File structure
+
+- Only spec-defined directories present: `scripts/`, `references/`, `assets/`
+- No non-spec files (e.g. META.md, extra config files)
+- Optional directories contain real content — not just unfilled placeholder READMEs
+- `README.md` present and accurately describes the skill and its files
+
+### Formatting
+
+- Heading levels consistent: H2 for main sections, H3 for subsections
+- Code blocks fenced with a language tag where applicable (`bash`, `markdown`, `python`)
+- Consistent whitespace: blank line between sections, consistent list indentation
+- No broken relative paths in file references
+
+### Scripts
+
+- No interactive TTY prompts (`read`, `input()`, `readline`)
+- `--help` exposed with concise usage
+- Data to stdout, diagnostics to stderr
+- Idempotent ("create if not exists")
+- Meaningful exit codes documented in `--help`
+- `--dry-run` present for destructive operations
+
+### Internal consistency
+
+- SKILL.md steps match what scripts actually do
+- `README.md` file table lists every file that exists — no missing entries, no stale entries
+- Placeholder READMEs in `scripts/`, `references/`, `assets/` consistent with what SKILL.md says about each directory
+
+## Step 4 — Report
+
+Output a punch list grouped by dimension:
+
+```
+PASS/FAIL/SUGGESTION  <finding> — <file>:<line>
+```
+
+Follow with a priority table:
+
+| Priority | Severity | Finding | File:Line |
+|----------|----------|---------|-----------|
+
+Then for each FAIL, a fix proposal:
+
+```
+FAIL: <finding>
+Fix:  <exact change — quote before/after where applicable>
+```
+
+Do not apply fixes. Report and propose only.
diff --git a/plugins/kyberforge/skills/skill-write/README.md b/plugins/kyberforge/skills/skill-write/README.md
new file mode 100644
index 0000000..27d8ed7
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/README.md
@@ -0,0 +1,63 @@
+# skill-write
+
+Author a new skill conforming to the [agentskills.io](https://agentskills.io) specification.
+
+## What it does
+
+1. Scaffolds a full skill directory from annotated templates
+2. Guides filling in `SKILL.md` and supporting files
+3. Validates the result against the spec
+
+## Before you start
+
+This skill produces its best output when you arrive with rich context:
+
+- Run `/grill-me` to resolve design decisions (scope, triggers, patterns)
+- Collect domain research, examples, and reference docs
+- Know the skill name (kebab-case) and destination path
+
+## Usage
+
+Invoke via your agent tool with `/skill-write`, or follow the steps in `SKILL.md` manually.
+
+**Agent invocation:**
+```
+/skill-write
+```
+
+**Manual (human) workflow:**
+```bash
+# 1. Create the scaffold
+bash scripts/new-skill.sh <skill-name> <destination-dir>
+
+# 2. Fill in the templates at <destination-dir>/<skill-name>/
+
+# 3. Validate
+bash scripts/validate.sh <destination-dir>/<skill-name>
+```
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `SKILL.md` | Skill instructions for agents |
+| `scripts/new-skill.sh` | Copies annotated templates to the destination |
+| `scripts/validate.sh` | Validates a skill directory against the spec |
+| `assets/templates/SKILL.md` | Annotated SKILL.md template |
+| `assets/templates/README.md` | Annotated README template for the new skill |
+| `assets/templates/scripts/README.md` | Placeholder for bundled scripts |
+| `assets/templates/references/README.md` | Placeholder for reference docs |
+| `assets/templates/assets/README.md` | Placeholder for static assets |
+
+## Placement
+
+Skills can be installed in two locations:
+
+| Type | Path |
+|------|------|
+| Direct (available immediately) | `~/.agents/skills/<name>/` |
+| Plugin (installed via marketplace) | `plugins/<plugin>/skills/<name>/` |
+
+## Spec reference
+
+[agentskills.io specification](https://agentskills.io/specification.md)
diff --git a/plugins/kyberforge/skills/skill-write/SKILL.md b/plugins/kyberforge/skills/skill-write/SKILL.md
new file mode 100644
index 0000000..8a403a9
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/SKILL.md
@@ -0,0 +1,151 @@
+---
+name: skill-write
+description: >
+  Author a new skill following the agentskills.io specification — scaffold the
+  directory structure from annotated templates, fill in SKILL.md and supporting
+  files, then validate the result. Use when the user wants to create a new skill
+  from scratch, says "write a skill for X", "build a skill that does Y", or
+  "create a SKILL.md for Z", or wants to make a workflow repeatable or shareable
+  as a reusable command. Performs best when preceded by a grill session and
+  domain research. Do not use to update an existing well-formed skill, write
+  evals, or author agent definition files.
+allowed-tools: Bash Read Write
+metadata:
+  category: factory
+---
+
+## Prerequisites
+
+Run `/grill-me` on the skill's design and research the target domain first.
+Share those outputs in this conversation: grill context, research docs, examples, constraints.
+
+**Before touching the filesystem, verify you have:**
+- [ ] A clear purpose — what specific task will this skill handle?
+- [ ] Trigger scenarios — when should an agent activate it, including indirect cases?
+- [ ] Skill name (kebab-case) and destination path
+
+If any are missing, stop and ask the user before proceeding.
+
+## Step 1 — Scaffold
+
+Run the copy script with the skill name and destination directory:
+
+```bash
+bash scripts/new-skill.sh <skill-name> <destination-dir>
+```
+
+Examples:
+```bash
+bash scripts/new-skill.sh my-tool ~/.agents/skills/
+bash scripts/new-skill.sh data-analyzer plugins/myplugin/skills/
+```
+
+This creates `<destination-dir>/<skill-name>/` with annotated templates ready to fill in.
+
+## Step 2 — Fill in SKILL.md
+
+Open `<destination-dir>/<skill-name>/SKILL.md`. Replace every `FILL IN:` placeholder.
+
+### Frontmatter
+
+**`name`** — already set by the scaffold script. Must exactly match the directory name.
+
+**`description`** — carries the entire triggering burden. Rules:
+- Imperative: "Use when..." not "This skill..."
+- Specific about capabilities ("parses and validates OpenAPI specs", not "helps with APIs")
+- Include indirect triggers: "even if the user doesn't mention X explicitly"
+- Add "Do not use when..." only if a near-miss skill exists that could steal activations
+- Hard limit: 1024 characters — count before finalizing
+
+**Optional fields** — uncomment and fill in or remove entirely:
+- `license` — include when distributing the skill externally
+- `compatibility` — include if the skill requires specific tools, runtimes, or network access
+- `metadata` — key-value map; use `author`, `version`, `category`
+- `allowed-tools` — space-separated pre-approved tools; reduces permission prompts
+
+### Body — include only what the agent lacks
+
+Ask of every sentence: "Would the agent get this wrong without it?" Cut anything that answers "no."
+
+**Include:**
+- Non-obvious sequences or ordering constraints — the agent may skip or reorder steps without this
+- Domain conventions the agent cannot infer from general knowledge — this is the core value a skill adds
+- One default per decision point, plus one escape hatch — never a menu; menus cause the agent to pause or pick arbitrarily
+- Gotchas — facts that defy reasonable assumptions; the agent will get these wrong every time without them
+
+**Exclude:**
+- Concepts the agent already knows (what JSON is, how HTTP works) — adds tokens without changing behavior
+- Exhaustive option lists — pick a default; the agent doesn't benefit from choosing
+- Steps the agent handles independently — over-specifying leads agents to follow unproductive paths
+- Restatements of the description — it's already in context; repeating it wastes the token budget
+
+### Patterns
+
+**Gotchas** — highest value; place near the top:
+```markdown
+## Gotchas
+- <Fact that defies a reasonable assumption>
+- <Non-obvious naming discrepancy or hidden constraint>
+```
+
+**Default with escape hatch** (not a menu):
+```markdown
+Use <X> for <task>. For <edge case>, use <Y> instead.
+```
+
+**Prescriptive sequence** (when order is critical or fragile):
+```markdown
+Run exactly:
+\`\`\`bash
+<command>
+\`\`\`
+Do not modify flags.
+```
+
+**Checklist** (multi-step workflows):
+```markdown
+- [ ] Step 1: ...
+- [ ] Step 2: ...
+```
+
+**Conditional reference** (progressive disclosure — load only when needed):
+```
+If <condition>, read `references/<file>.md`.
+```
+
+### Size budget
+
+Keep `SKILL.md` under 500 lines. When approaching the limit:
+- Move reference material to `references/<topic>.md` and load it conditionally
+- Bundle repeated executable logic into `scripts/` rather than reinventing each run
+
+## Step 3 — Add scripts (if needed)
+
+Place executable scripts in `scripts/`. Rules for agentic scripts:
+
+- **No interactive prompts** — agents run non-interactive; blocking on TTY input hangs indefinitely. Accept all input via flags, env vars, or stdin.
+- **Expose `--help`** — concise usage output; keep it short (it enters the agent's context)
+- **Structured output** — data (JSON, CSV) to stdout; diagnostics and progress to stderr
+- **Idempotent** — "create if not exists"; agents may retry on failure
+- **Meaningful exit codes** — `0` success, non-zero failure; document in `--help`
+- **Dry-run support** — add `--dry-run` for destructive operations
+
+If no scripts are needed, delete `scripts/README.md` and the `scripts/` directory.
+
+## Step 4 — Add references and assets (if needed)
+
+**`references/`** — additional documentation loaded on demand. One topic per file.
+Reference conditionally from SKILL.md: `If <condition>, read references/<file>.md`.
+
+**`assets/`** — static resources: templates, schemas, lookup tables.
+Reference by relative path from SKILL.md.
+
+If not needed, delete the placeholder READMEs and their directories.
+
+## Step 5 — Validate
+
+```bash
+bash scripts/validate.sh <destination-dir>/<skill-name>
+```
+
+All checks must pass before the skill is considered done.
diff --git a/plugins/kyberforge/skills/skill-write/assets/templates/README.md b/plugins/kyberforge/skills/skill-write/assets/templates/README.md
new file mode 100644
index 0000000..42548a6
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/assets/templates/README.md
@@ -0,0 +1,53 @@
+# SKILL_NAME
+
+<!-- FILL IN: One sentence describing what this skill does. -->
+
+## What it does
+
+<!-- FILL IN: 2–4 sentences. What task does this skill handle?
+     What does the agent produce or accomplish when it runs? -->
+
+## Before you start
+
+<!-- FILL IN: List any prerequisites the user should have ready.
+     Examples: research docs, a grill session, specific input files, credentials.
+     Delete this section if the skill has no meaningful prerequisites. -->
+
+## Usage
+
+Invoke via your agent tool:
+
+```
+/SKILL_NAME
+```
+
+<!-- FILL IN: Add any required or common arguments.
+     If the skill takes no arguments, delete the code block above and just keep the slash command. -->
+
+<!-- OPTIONAL: Manual (human) workflow — include if the skill bundles scripts a human can run directly.
+
+**Manual workflow:**
+```bash
+# FILL IN: step-by-step commands
+```
+-->
+
+## Files
+
+<!-- FILL IN: List the files in this skill directory and their purpose.
+     Remove rows for directories that don't exist in your skill.
+     Example rows are provided — replace with your actual files. -->
+
+| File | Purpose |
+|------|---------|
+| `SKILL.md` | Skill instructions for agents |
+| `scripts/` | FILL IN: what the scripts do |
+| `references/` | FILL IN: what reference docs are here |
+| `assets/` | FILL IN: what static resources are here |
+
+<!-- OPTIONAL: Spec reference — include if this skill implements or follows an external standard.
+
+## Spec reference
+
+[FILL IN: Spec name](FILL IN: URL)
+-->
diff --git a/plugins/kyberforge/skills/skill-write/assets/templates/SKILL.md b/plugins/kyberforge/skills/skill-write/assets/templates/SKILL.md
new file mode 100644
index 0000000..cbda594
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/assets/templates/SKILL.md
@@ -0,0 +1,101 @@
+---
+# SKILL.md — agentskills.io skill definition
+# Fill in all FILL IN: placeholders. Remove comment blocks that don't apply.
+
+name: SKILL_NAME
+# Required. Must exactly match the parent directory name.
+# Valid characters: lowercase letters, numbers, hyphens.
+# Invalid: uppercase, leading/trailing/consecutive hyphens.
+# Max length: 64 characters.
+# Examples: my-tool, data-analyzer, pdf-processor
+
+description: >
+  FILL IN: What does this skill do? State capabilities specifically
+  (e.g. "parses and validates OpenAPI specs", not "helps with APIs").
+  Use when FILL IN: when should an agent activate this skill?
+  Include indirect triggers: even if the user doesn't mention X explicitly.
+  Do not use when FILL IN: near-miss exclusions — remove this line if none apply.
+
+# license: MIT
+# Optional. License name (e.g. MIT, Apache-2.0) or relative path to a bundled
+# license file. Include when distributing this skill. Omit for private/internal use.
+
+# compatibility: Requires python3 >= 3.10 and uv
+# Optional. 1–500 characters. State tool requirements, runtime versions,
+# and network access needs. Omit for skills with no special environment requirements.
+
+# metadata:
+#   author: your-name
+#   version: "1.0"
+#   category: general
+# Optional. Arbitrary key-value map. Common keys: author, version, category.
+# No restrictions on keys or values.
+
+# allowed-tools: Bash Read Write
+# Optional (experimental — support varies by client).
+# Space-separated list of pre-approved tools.
+# Use when tool usage is known and bounded, to reduce permission prompts.
+---
+
+<!-- ============================================================
+  SKILL BODY
+
+  Include only what the agent lacks:
+    - Domain conventions the agent cannot infer from general knowledge
+    - Non-obvious sequences or ordering constraints
+    - One default per decision point + one escape hatch (never a menu)
+    - Gotchas — facts that defy reasonable assumptions
+
+  Omit:
+    - Concepts the agent already knows
+    - Exhaustive option lists
+    - Steps the agent handles independently
+    - Restatements of the description
+
+  Size budget: under 500 lines / 5000 tokens.
+  Move reference material to references/ and load it conditionally.
+  Bundle repeated executable logic into scripts/.
+
+  Delete this comment block before shipping.
+============================================================ -->
+
+<!-- OPTIONAL: Gotchas section — highest-value content. Place near the top.
+     Add facts that defy reasonable assumptions or non-obvious constraints.
+
+## Gotchas
+
+- FILL IN: fact that defies a reasonable assumption
+- FILL IN: non-obvious naming discrepancy or hidden constraint
+-->
+
+<!-- OPTIONAL: Multi-step workflow checklist.
+
+## Workflow
+
+- [ ] Step 1: FILL IN
+- [ ] Step 2: FILL IN
+- [ ] Step 3: FILL IN
+-->
+
+<!-- OPTIONAL: Output format template — use when the agent must produce a specific format.
+
+## Output format
+
+Use this structure:
+
+```markdown
+# [FILL IN: Title]
+
+## FILL IN: Section
+FILL IN: what goes here
+```
+-->
+
+<!-- OPTIONAL: Conditional reference — load documentation only when needed.
+
+If FILL IN: condition, read `references/FILL IN: filename.md`.
+-->
+
+## Instructions
+
+FILL IN: Add your skill instructions here. Replace this section with the skill body.
diff --git a/plugins/kyberforge/skills/skill-write/assets/templates/assets/README.md b/plugins/kyberforge/skills/skill-write/assets/templates/assets/README.md
new file mode 100644
index 0000000..4640f98
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/assets/templates/assets/README.md
@@ -0,0 +1,29 @@
+# assets/
+
+Static resources bundled with this skill: templates, schemas, lookup tables,
+sample data, images.
+
+## When to add an asset
+
+Add a file here when the skill needs a static resource that:
+- Would be tedious to reproduce in instructions (a full JSON schema, a CSV
+  lookup table, a binary template)
+- Needs to be referenced by path rather than inlined in SKILL.md
+
+## How to reference from SKILL.md
+
+Use a relative path from the skill root:
+
+```markdown
+Use the schema at `assets/response-schema.json` to validate output.
+```
+
+Or instruct the agent to load it conditionally:
+
+```markdown
+If validating output format, use `assets/response-schema.json`.
+```
+
+## If no assets are needed
+
+Delete this README and the `assets/` directory entirely.
diff --git a/plugins/kyberforge/skills/skill-write/assets/templates/references/README.md b/plugins/kyberforge/skills/skill-write/assets/templates/references/README.md
new file mode 100644
index 0000000..5d65e3e
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/assets/templates/references/README.md
@@ -0,0 +1,31 @@
+# references/
+
+Additional documentation agents load on demand. Files here extend SKILL.md
+without bloating its core context.
+
+## When to add a reference file
+
+Move content here when SKILL.md is approaching 500 lines, or when a topic
+is only relevant in specific circumstances (error handling, edge cases,
+domain-specific sub-procedures).
+
+## How to reference from SKILL.md
+
+Load conditionally — tell the agent exactly when to read each file:
+
+```markdown
+If the API returns a non-200 status, read `references/api-errors.md`.
+```
+
+Avoid generic "see references/ for details" — the agent loads context on
+demand, so give it a precise trigger condition.
+
+## File conventions
+
+- One topic per file — focused files mean less unnecessary context loaded
+- Kebab-case filenames (e.g. `api-errors.md`, `output-formats.md`)
+- Keep files under 200 lines where possible
+
+## If no reference files are needed
+
+Delete this README and the `references/` directory entirely.
diff --git a/plugins/kyberforge/skills/skill-write/assets/templates/scripts/README.md b/plugins/kyberforge/skills/skill-write/assets/templates/scripts/README.md
new file mode 100644
index 0000000..f71640e
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/assets/templates/scripts/README.md
@@ -0,0 +1,47 @@
+# scripts/
+
+Executable code bundled with this skill. Agents run scripts in this directory
+to perform repeatable operations rather than reinventing the logic each run.
+
+## When to add a script
+
+Add a script when agents independently reinvent the same logic across runs —
+building the same parser, chart, or validation routine from scratch each time.
+Bundle it here once, tested and reliable.
+
+## Script requirements (agentskills.io)
+
+Scripts must be designed for non-interactive, agentic execution:
+
+- **No interactive prompts** — agents run in non-interactive shells.
+  Accept all input via flags, env vars, or stdin. A script that blocks on
+  TTY input hangs indefinitely.
+- **Expose `--help`** — this is how agents learn your script's interface.
+  Keep the output concise; it enters the agent's context window.
+- **Structured output** — write data (JSON, CSV, TSV) to stdout.
+  Write progress, warnings, and diagnostics to stderr.
+- **Idempotent** — prefer "create if not exists" over "create and fail on
+  duplicate". Agents may retry on failure.
+- **Meaningful exit codes** — `0` for success, non-zero for failure.
+  Use distinct codes for different failure types; document them in `--help`.
+- **Dry-run support** — add `--dry-run` for destructive operations.
+
+## Self-contained scripts
+
+Bundle dependencies inline so the agent can run the script with a single command.
+
+Python (PEP 723 + uv):
+```python
+# /// script
+# dependencies = ["requests>=2.31,<3"]
+# requires-python = ">=3.11"
+# ///
+import requests
+```
+```bash
+uv run scripts/my-script.py
+```
+
+## If no scripts are needed
+
+Delete this README and the `scripts/` directory entirely.
diff --git a/plugins/kyberforge/skills/skill-write/scripts/new-skill.sh b/plugins/kyberforge/skills/skill-write/scripts/new-skill.sh
new file mode 100755
index 0000000..464e9bc
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/scripts/new-skill.sh
@@ -0,0 +1,87 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+SKILL_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+TEMPLATES_DIR="$SKILL_DIR/../assets/templates"
+
+usage() {
+  cat <<EOF
+Usage: new-skill.sh <skill-name> <destination-dir>
+
+Create a new skill scaffold by copying annotated templates to the destination.
+
+Arguments:
+  skill-name       Kebab-case skill identifier (e.g. my-tool, data-analyzer).
+                   Must match the directory name exactly.
+  destination-dir  Parent directory to create the skill in.
+                   Examples: ~/.agents/skills/  plugins/myplugin/skills/
+
+Output:
+  Creates <destination-dir>/<skill-name>/ with annotated templates ready to fill in.
+
+Exit codes:
+  0  Scaffold created successfully
+  1  Invalid arguments or destination already exists
+EOF
+}
+
+if [[ "${1:-}" == "--help" || "${1:-}" == "-h" ]]; then
+  usage
+  exit 0
+fi
+
+if [[ $# -lt 2 ]]; then
+  echo "Error: skill-name and destination-dir are required." >&2
+  echo "" >&2
+  usage >&2
+  exit 1
+fi
+
+SKILL_NAME="$1"
+DEST_DIR="$2"
+
+# Validate skill name format
+if ! echo "$SKILL_NAME" | grep -qE '^[a-z0-9]+(-[a-z0-9]+)*$'; then
+  echo "Error: skill-name must use lowercase letters, numbers, and hyphens only." >&2
+  echo "       No leading, trailing, or consecutive hyphens." >&2
+  echo "       Received: '$SKILL_NAME'" >&2
+  exit 1
+fi
+
+# Validate templates directory exists
+if [[ ! -d "$TEMPLATES_DIR" ]]; then
+  echo "Error: templates directory not found at '$TEMPLATES_DIR'." >&2
+  echo "       Run this script from its original location inside the skill-write skill." >&2
+  exit 1
+fi
+
+# Validate destination exists
+if [[ ! -d "$DEST_DIR" ]]; then
+  echo "Error: destination directory '$DEST_DIR' does not exist." >&2
+  exit 1
+fi
+
+TARGET="$DEST_DIR/$SKILL_NAME"
+
+# Refuse to overwrite existing directory
+if [[ -d "$TARGET" ]]; then
+  echo "Error: '$TARGET' already exists." >&2
+  echo "       Remove it first or choose a different name." >&2
+  exit 1
+fi
+
+# Copy templates to destination
+cp -r "$TEMPLATES_DIR" "$TARGET"
+
+# Set skill name in templates
+sed -i "s/SKILL_NAME/$SKILL_NAME/g" "$TARGET/SKILL.md"
+sed -i "s/SKILL_NAME/$SKILL_NAME/g" "$TARGET/README.md"
+
+echo "Scaffold created: $TARGET"
+echo ""
+echo "Next steps:"
+echo "  1. Fill in $TARGET/SKILL.md — replace all FILL IN: placeholders"
+echo "  2. Add scripts to scripts/ if needed (or delete the directory)"
+echo "  3. Add docs to references/ if needed (or delete the directory)"
+echo "  4. Add resources to assets/ if needed (or delete the directory)"
+echo "  5. Validate: bash $(dirname "${BASH_SOURCE[0]}")/validate.sh $TARGET"
diff --git a/plugins/kyberforge/skills/skill-write/scripts/validate.sh b/plugins/kyberforge/skills/skill-write/scripts/validate.sh
new file mode 100755
index 0000000..a719fb7
--- /dev/null
+++ b/plugins/kyberforge/skills/skill-write/scripts/validate.sh
@@ -0,0 +1,179 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  cat <<EOF
+Usage: validate.sh <skill-dir>
+
+Validate a skill directory against the agentskills.io specification.
+
+Arguments:
+  skill-dir  Path to the skill directory containing SKILL.md.
+
+Exit codes:
+  0  All checks passed
+  1  One or more checks failed
+EOF
+}
+
+if [[ "${1:-}" == "--help" || "${1:-}" == "-h" ]]; then
+  usage
+  exit 0
+fi
+
+if [[ $# -lt 1 ]]; then
+  echo "Error: skill-dir is required." >&2
+  echo "" >&2
+  usage >&2
+  exit 1
+fi
+
+python3 -u - "$1" <<'PYTHON'
+import sys
+import os
+import re
+
+skill_dir = os.path.abspath(sys.argv[1])
+skill_md = os.path.join(skill_dir, "SKILL.md")
+
+if not os.path.isfile(skill_md):
+    print(f"Error: '{skill_md}' not found.", file=sys.stderr)
+    sys.exit(1)
+
+with open(skill_md) as f:
+    content = f.read()
+
+failed = False
+
+def ok(msg):
+    print(f"PASS  {msg}")
+
+def fail(msg):
+    global failed
+    print(f"FAIL  {msg}", file=sys.stderr)
+    failed = True
+
+# --- Parse frontmatter ---
+fm_match = re.match(r'^---\n(.*?)\n---', content, re.DOTALL)
+if not fm_match:
+    fail("No valid YAML frontmatter block found (expected ---...---)")
+    sys.exit(1)
+
+fm = fm_match.group(1)
+body_start = fm_match.end()
+
+# Extract name
+name_m = re.search(r'^name:\s*(\S+)', fm, re.MULTILINE)
+name = name_m.group(1).strip('"\'') if name_m else ""
+
+# Extract description — inline or block scalar (> or |)
+desc = ""
+desc_m = re.search(r'^description:\s*([>|])\n((?:[ \t]+.+\n?)+)', fm, re.MULTILINE)
+if desc_m:
+    raw = desc_m.group(2)
+    desc = re.sub(r'\s+', ' ', raw).strip()
+else:
+    desc_inline = re.search(r'^description:\s*(.+)', fm, re.MULTILINE)
+    if desc_inline:
+        desc = desc_inline.group(1).strip()
+
+dir_name = os.path.basename(skill_dir)
+
+# --- Checks ---
+
+# name present
+if name:
+    ok(f"name present: '{name}'")
+else:
+    fail("name field is missing or empty")
+
+# name matches directory
+if name and dir_name:
+    if name == dir_name:
+        ok(f"name '{name}' matches directory '{dir_name}'")
+    else:
+        fail(f"name '{name}' does not match directory '{dir_name}'")
+
+# name length
+if name:
+    if len(name) <= 64:
+        ok(f"name length {len(name)} chars (limit: 64)")
+    else:
+        fail(f"name '{name}' is {len(name)} chars — exceeds 64-character limit")
+
+# name format
+if name:
+    if re.match(r'^[a-z0-9]+(-[a-z0-9]+)*$', name):
+        ok(f"name format valid (kebab-case)")
+    else:
+        fail(f"name '{name}' is invalid — use lowercase letters, numbers, and hyphens only; no leading, trailing, or consecutive hyphens")
+
+# description present
+if desc:
+    ok(f"description present")
+else:
+    fail("description field is missing or empty")
+
+# description length
+if desc:
+    dlen = len(desc)
+    if dlen <= 1024:
+        ok(f"description length {dlen} chars (limit: 1024)")
+    else:
+        fail(f"description length {dlen} chars — exceeds 1024-character limit")
+
+# Unfilled placeholder detection — matches FILL IN: followed by actual content,
+# but not backtick-quoted references like `FILL IN:` used in instructions.
+PLACEHOLDER_RE = re.compile(r'(?<!`)FILL IN:[^`\n]')
+
+# description contains unfilled placeholder
+if desc and PLACEHOLDER_RE.search(desc):
+    fail("description still contains 'FILL IN:' placeholder — replace before shipping")
+else:
+    if desc:
+        ok("description has no unfilled placeholders")
+
+# SKILL.md line count
+line_count = len(content.splitlines())
+if line_count <= 500:
+    ok(f"SKILL.md line count {line_count} (limit: 500)")
+else:
+    fail(f"SKILL.md line count {line_count} — exceeds 500-line limit")
+
+# Body unfilled placeholders
+body = content[body_start:]
+fill_matches = PLACEHOLDER_RE.findall(body)
+if fill_matches:
+    fail(f"SKILL.md body contains {len(fill_matches)} unfilled 'FILL IN:' placeholder(s)")
+else:
+    ok("SKILL.md body has no unfilled placeholders")
+
+# Scripts checks
+scripts_dir = os.path.join(skill_dir, "scripts")
+if os.path.isdir(scripts_dir):
+    scripts = [f for f in os.listdir(scripts_dir)
+               if os.path.isfile(os.path.join(scripts_dir, f)) and not f.endswith('.md')]
+    for fname in scripts:
+        fpath = os.path.join(scripts_dir, fname)
+        with open(fpath) as f:
+            sc = f.read()
+        # Interactive prompt heuristic
+        if re.search(r'^\s*(read\s|input\()', sc, re.MULTILINE):
+            fail(f"scripts/{fname}: may use interactive input (read/input detected)")
+        else:
+            ok(f"scripts/{fname}: no interactive prompts detected")
+        # Executable bit
+        if os.access(fpath, os.X_OK):
+            ok(f"scripts/{fname}: is executable")
+        else:
+            fail(f"scripts/{fname}: not executable — run: chmod +x {fpath}")
+
+# Summary
+print()
+if not failed:
+    print("All checks passed.")
+    sys.exit(0)
+else:
+    print("One or more checks failed.", file=sys.stderr)
+    sys.exit(1)
+PYTHON
diff --git a/plugins/kyberforge/skills/write-skill/CATEGORIES.md b/plugins/kyberforge/skills/write-skill/CATEGORIES.md
deleted file mode 100644
index 5aaf491..0000000
--- a/plugins/kyberforge/skills/write-skill/CATEGORIES.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Skill Categories
-
-| Category | Scope |
-|---|---|
-| `design` | grill-me, grill-with-docs, to-prd, prototype, architecture-review |
-| `plan` | to-issues, triage |
-| `implement` | tdd, diagnose, implement-feature, refactor, write-docs |
-| `test` | write-tests, generate-test-data, review-test-coverage |
-| `review` | improve-codebase-architecture, code-review, security-review, pr-description, changelog-entry |
-| `deploy` | write-ci-pipeline, write-deployment-config, write-ai-review-workflow, deployment-checklist |
-| `operate` | write-runbook, incident-diagnosis, post-mortem, inspect-deployment |
-| `iac` | write-ansible-role, write-terraform-module, write-k8s-manifest, write-docker-compose, proxmox-vm-spec, iac-security-review, write-molecule-test |
-| `cross-cutting` | zoom-out, caveman, session-handoff, governance-check, git-guardrails, git-commit-message |
-| `factory` | write-skill, write-agent, write-adr, write-workflow, write-eval, validate-skill, upgrade-skill, write-issue-spec |
-| `marketplace` | marketplace-architect — plugin and skill distribution tooling for Claude Code / GitHub Copilot CLI |
-| `roles` | architect, developer, reviewer, security, qa, ops — Chunk 5 |
diff --git a/plugins/kyberforge/skills/write-skill/META-TEMPLATE.md b/plugins/kyberforge/skills/write-skill/META-TEMPLATE.md
deleted file mode 100644
index ebfdbd6..0000000
--- a/plugins/kyberforge/skills/write-skill/META-TEMPLATE.md
+++ /dev/null
@@ -1,27 +0,0 @@
-```yaml
-version: "1.0"          # increment on meaningful changes to the skill
-updated: YYYY-MM-DD     # ISO date of last update
-
-# when: describes when this skill is loaded — the full trigger context.
-# More detail than the description field; not used for routing.
-when: <describe the invocation conditions here>
-
-# source: tracks content you ADOPTED from an upstream repo.
-# Adopt = you read someone else's code or docs and incorporated text or logic directly.
-# Omit this field entirely if the skill is self-authored — absence means original work.
-# Present only when content was actually taken, tracked at commit-level for upgrade reviews.
-source:
-  - repo: org/repo-name          # GitHub slug — no URL, slug is stable and searchable
-    commit: <full SHA>           # exact commit reviewed at time of adoption
-    files:
-      - path/to/file.md          # inline comment: what was taken from this file
-      - path/to/other.md         # inline comment: what was taken from this file
-    updated: YYYY-MM-DD          # date this source entry was last reviewed
-
-# references: tracks content you CITED but did not adopt verbatim.
-# Cite = you read it and it informed the skill, but nothing was copied or adapted.
-# Examples: a spec you followed, a paper that shaped the approach, external documentation.
-# Distinct from source: source = took content; references = informed by content.
-references:
-  - https://example.com/relevant-doc
-```
diff --git a/plugins/kyberforge/skills/write-skill/META.md b/plugins/kyberforge/skills/write-skill/META.md
deleted file mode 100644
index ffd2f54..0000000
--- a/plugins/kyberforge/skills/write-skill/META.md
+++ /dev/null
@@ -1,16 +0,0 @@
-```yaml
-version: "1.5"
-updated: 2026-05-26
-
-# when: describes when this skill is loaded — the full trigger context.
-# More detail than the description field; not used for routing.
-when: invoked by explicit trigger ("write a new skill for X", "create a SKILL.md that does Y") or implicit request to author a skill file or convert an existing placeholder to the canonical authoring standard
-
-# source: omitted — self-authored original; no upstream content adopted
-# Absence of source means self-authored. If content is adopted from upstream,
-# add a source entry per the META-TEMPLATE.md schema.
-
-references:
-  - https://agentskills.io/specification.md
-  - https://agentskills.io/skill-creation/optimizing-descriptions
-```
diff --git a/plugins/kyberforge/skills/write-skill/SKILL-TEMPLATE.md b/plugins/kyberforge/skills/write-skill/SKILL-TEMPLATE.md
deleted file mode 100644
index 853412a..0000000
--- a/plugins/kyberforge/skills/write-skill/SKILL-TEMPLATE.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-name: <skill-name>
-# description: routing-only field — loaded at startup for every skill scan to decide whether
-# to activate this skill. Write in imperative phrasing ("Use when X", not "This skill does X").
-# Must cover: (1) what the skill does, (2) when to invoke it, (3) negative triggers — what
-# adjacent tasks must NOT activate it. No behavioral or role framing; that belongs in the body.
-# Max 1024 characters. The `when:` detail that lived here previously now lives in META.md.
-# Example: "Use when the user wants to create a new SKILL.md file or convert a placeholder to
-# canonical format. Do NOT use when updating an existing well-formed skill — use upgrade-skill."
-description: <trigger description>
-metadata:
-  category: <category — see CATEGORIES.md>
-# allowed-tools: <add only when the skill has a narrow, well-defined tool surface; omit otherwise>
-# model: sonnet | opus | haiku — Claude Code extension; overrides session model for this skill's turn.
-# Omit to inherit the active session model. Factory §9 routing: haiku=formatting/classification,
-# sonnet=most coding/review, opus=adversarial/complex reasoning.
----
-
-<requirements>
-
-## Required inputs
-
-<!-- List each required input as a bullet: name, what it is, how the agent obtains it.
-     Negative trigger cases are NOT listed here — the agent proposes them during trigger testing.
-     Example:
-     - **Skill name** — kebab-case slug; inferred from user description if not stated explicitly, ask if ambiguous
-     - **Existing SKILL.md path** — for placeholder conversions only; read before writing -->
-
-- **<Input name>** — <description; how obtained>
-
-## Constraints
-
-<!-- One rule per bullet. State the boundary condition inline. Plain English, no jargon.
-     Do not include a constraint about body section structure — the template enforces that.
-     Example:
-     - Frontmatter has three fields only: `name`, `description`, and `metadata.category` — add `allowed-tools` only when the skill has a narrow, well-defined tool surface
-     - Body ≤500 lines — content that explains rather than directs belongs in sub-files, not the body
-     - Sub-files use three spec-defined optional directories: `scripts/` (executable code), `references/` (on-demand docs), `assets/` (templates, data files, lookup tables). File references must be one level deep. Wire each sub-file with an explicit step instruction (e.g. "See references/lookup.md for error codes") — without wiring, the file is never loaded -->
-
-- <constraint>
-
-</requirements>
-
-<steps>
-
-## Process
-
-<!-- Numbered steps with a bold action label. Short, direct sentences — state what to do and
-     what happens as a result. Call out hard gates explicitly (steps that block all progress
-     until satisfied). No preamble, no meta-commentary about the steps themselves.
-     Example:
-     1. **Scan for overlap.** Check `.agents/skills/` for skills with similar purpose or trigger phrases. If overlap is found, surface it and wait for explicit direction — do not continue.
-     2. **Grill.** Run a focused grill to reach shared understanding of: skill name, category, purpose, and use cases. One question at a time, with a recommendation for each. -->
-
-1. **<Step name>.** <what to do and what happens as a result>
-
-## Output format
-
-<!-- Describe the files or artifacts produced. Include paths and how they are created
-     (copy-fill from template, generated, etc.). State the template used for structured file output.
-     Example:
-     Two files produced for every skill, plus optional sub-files if the skill requires them:
-     - `SKILL.md` — copy-filled from `SKILL-TEMPLATE.md` at `.agents/skills/<name>/SKILL.md`
-     - `META.md` — copy-filled from `META-TEMPLATE.md` at `.agents/skills/<name>/META.md`
-     - `scripts/`, `references/`, or `assets/` — created only when needed; each file wired with an explicit step instruction -->
-
-<description of output>
-
-</steps>
-
-<checks>
-
-## Failure handling
-
-<!-- One bullet per failure mode. Lean — no overlap with constraints or process.
-     Format: condition — action.
-     Example:
-     - Template file missing — stop, report the path searched, do not write from memory
-     - `write-eval` fails or is unavailable — flag, do not mark the skill complete -->
-
-- <failure condition> — <what to do>
-
-## Self-check
-
-<!-- Verifiable checklist the agent runs before declaring the skill complete.
-     Each item must be checkable, not aspirational.
-     Example:
-     - [ ] Overlap check completed before any content was written
-     - [ ] Trigger description tested against all three cases — all passed before body content was written -->
-
-- [ ] <check>
-
-</checks>
diff --git a/plugins/kyberforge/skills/write-skill/SKILL.md b/plugins/kyberforge/skills/write-skill/SKILL.md
deleted file mode 100644
index 1f6321e..0000000
--- a/plugins/kyberforge/skills/write-skill/SKILL.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-name: write-skill
-description: >-
-  Use when the user wants to author a new skill file or convert an existing
-  placeholder to the canonical authoring standard. Triggers: "write a new skill
-  for X", "create a SKILL.md that does Y", "build a skill to handle Z". Do NOT
-  use when fixing or updating an existing well-formed skill (use upgrade-skill),
-  running existing evals (use write-eval), refactoring application code, or
-  writing documentation for non-skill artifacts.
-metadata:
-  category: factory
-model: sonnet
----
-
-<requirements>
-
-## Required inputs
-
-- **Skill name** — kebab-case slug; inferred from user description if not stated explicitly, ask if ambiguous
-- **Category** — from the category table in `CATEGORIES.md`; ask if unclear
-- **Purpose + use cases** — what the skill does and what tasks it handles; source for the trigger description
-- **For placeholder conversions:** existing SKILL.md path — read before writing
-
-Negative trigger cases are NOT a required input. The agent proposes them based on the skill's purpose and adjacent skills found during the overlap scan. The user confirms or refines before trigger testing begins.
-
-## Constraints
-
-- Write two files for every skill: `SKILL.md` at `.agents/skills/<name>/SKILL.md` and `META.md` alongside it
-- Frontmatter required fields: `name`, `description`, `metadata.category` — add `allowed-tools` only when the skill has a narrow, well-defined tool surface; add `model:` only when the skill's task complexity warrants a specific model tier (see SKILL-TEMPLATE.md for routing guidance)
-- Keep the body under 500 lines — content that explains rather than directs belongs in sub-files, not the body
-- Sub-files use three spec-defined optional directories: `scripts/` (executable code), `references/` (on-demand docs), `assets/` (templates, data files, lookup tables); additional files (e.g. `META.md`) are valid at the skill root. File references must be one level deep — no nested chains. Wire each sub-file with an explicit instruction in the step that needs it (e.g. `"See references/lookup.md for error codes"`) — without a wiring instruction the file is never loaded
-- Use XML tags only when the body has three or more logical sections and exceeds 500 tokens — default to plain prose
-- Test the trigger description against all three cases — explicit, implicit, negative — before writing any body content. Hard gate: a failed case means revise and retest, not proceed
-- Check for overlapping skills in `.agents/skills/` before writing anything — if overlap is found, surface it and wait for direction
-- For placeholder conversions: read the existing SKILL.md first and remove all stale or outdated content
-
-</requirements>
-
-<steps>
-
-## Process
-
-1. **Scan for overlap.** Check for skills with similar purpose or trigger phrases. If overlap is found, surface it and wait for explicit direction — do not continue.
-
-2. **Grill.** Run a focused grill with the /grill-me skill to reach shared understanding of: skill name, category, purpose, and use cases. One question at a time, with a recommendation for each.
-
-3. **Conflict check.** Spawn a sub-agent: read `docs/ai-constitution.md`, `docs/research/ai-coding-factory/ai-coding-factory-principles.md`, and `docs/notes/factory-integration-decisions.md`, then check the agreed skill purpose and design against all three. Where a factory principle is superseded by an integration decision, the decision takes precedence — do not flag it as a conflict. Return a numbered list of genuine unresolved tensions, or confirm none found. An empty list is a valid result. Hard gate: resolve any findings before proceeding.
-
-4. **Write and test the trigger description.** Using the agreed name, category, purpose, and use cases from the grill, draft `description:`. Propose negative trigger cases based on the skill's purpose and adjacent skills — get explicit user confirmation before running tests. Test all three cases and show per-case PASS/FAIL. A failed case means revise and retest — do not proceed.
-
-5. **Walk through each section.** For each section in `SKILL-TEMPLATE.md`: propose content, state where it comes from, present alternatives if they exist. Wait for explicit human confirmation before moving to the next section.
-
-6. **Copy both templates.** Copy `SKILL-TEMPLATE.md` to `.agents/skills/<name>/SKILL.md`. Copy `META-TEMPLATE.md` to `.agents/skills/<name>/META.md`. Do not modify content yet — copy first, fill second.
-
-7. **Fill both files.** Fill in the copied `SKILL.md` with confirmed section content. Fill in the copied `META.md` with version, updated date, when, source (if applicable), and references (if applicable).
-
-8. **Invoke `write-eval`.** Do not mark the skill complete without an eval file.
-
-9. **Run self-check.** Work through every item in the Self-check section below. Do not proceed until all items pass.
-
-10. **Prompt for HITL.** Ask the user to open a fresh session, trigger the skill, and confirm output before committing.
-
-## Output format
-
-Two files produced for every skill, plus optional sub-files if the skill requires them:
-
-- `SKILL.md` — copy-filled from `SKILL-TEMPLATE.md` at `.agents/skills/<name>/SKILL.md`
-- `META.md` — copy-filled from `META-TEMPLATE.md` at `.agents/skills/<name>/META.md`
-- `scripts/`, `references/`, or `assets/` — created only when needed; each file wired with an explicit step instruction
-
-For placeholder conversions, `SKILL.md` replaces the existing file entirely — no partial edits.
-
-</steps>
-
-<checks>
-
-## Failure handling
-
-- Template file missing — stop, report the path searched, do not write from memory
-- Existing SKILL.md not found for a placeholder conversion — stop, report the path searched
-- `write-eval` fails or is unavailable — flag, do not mark the skill complete
-
-## Self-check
-
-- [ ] Overlap check completed before any content was written
-- [ ] Conflict check sub-agent ran against constitution and factory principles — findings resolved before any writing began
-- [ ] Trigger description tested against all three cases — all passed before body content was written
-- [ ] Negative trigger cases confirmed by user before testing
-- [ ] Each section confirmed explicitly by user before SKILL.md was written
-- [ ] SKILL.md copy-filled from `SKILL-TEMPLATE.md` at correct path
-- [ ] `META.md` copy-filled from `META-TEMPLATE.md` at correct path
-- [ ] Frontmatter contains `name`, `description`, and `metadata.category`; optional `allowed-tools` and `model:` only where justified
-- [ ] Body is under 500 lines
-- [ ] If sub-files exist: placed in correct directory type (`scripts/`, `references/`, or `assets/`) and wired with an explicit instruction in the relevant step
-- [ ] For placeholder conversions: existing files read, all stale content removed, old directory deleted if renamed
-- [ ] `write-eval` invoked — eval file exists at correct path, covers trigger cases (explicit, implicit, negative) and at least one output case
-
-</checks>
diff --git a/plugins/kyberforge/skills/write-skill/evals/eval.yaml b/plugins/kyberforge/skills/write-skill/evals/eval.yaml
deleted file mode 100644
index 1fee481..0000000
--- a/plugins/kyberforge/skills/write-skill/evals/eval.yaml
+++ /dev/null
@@ -1,69 +0,0 @@
-skill_name: write-skill
-
-trigger_tests:
-  - id: explicit-trigger-new-skill
-    name: Explicit — new skill phrase
-    query: "Write a new skill for handling database migrations"
-    should_trigger: true
-
-  - id: implicit-trigger-no-phrase
-    name: Implicit — no trigger phrase
-    query: "I want to add a skill that automates our deploy process"
-    should_trigger: true
-
-  - id: implicit-trigger-conversion
-    name: Implicit — placeholder conversion
-    query: "The grill-me skill is a Pocock placeholder, can you convert it to our standard?"
-    should_trigger: true
-
-  - id: negative-trigger-upgrade
-    name: Negative — existing skill fix
-    query: "The tdd skill is producing wrong output, fix it"
-    should_trigger: false
-
-  - id: negative-trigger-code-refactor
-    name: Negative — code refactor
-    query: "Refactor this module to use the new API client"
-    should_trigger: false
-
-  - id: negative-trigger-write-eval
-    name: Negative — eval request
-    query: "Write evals for the diagnose skill"
-    should_trigger: false
-
-output_tests:
-  - id: output-has-all-sections
-    name: All 8 body sections present in order
-    type: deterministic
-    prompt: "Write a new skill for linting markdown files, category: implement"
-    expected_output: A complete SKILL.md containing all 8 required body sections in the prescribed order.
-    assertions:
-      - "Output contains '## Role'"
-      - "Output contains '## When to use / When not to use'"
-      - "Output contains '## Required inputs'"
-      - "Output contains '## Constraints'"
-      - "Output contains '## Process'"
-      - "Output contains '## Output format'"
-      - "Output contains '## Failure handling'"
-      - "Output contains '## Self-check'"
-      - "Sections appear in this order: ## Role, ## When to use / When not to use, ## Required inputs, ## Constraints, ## Process, ## Output format, ## Failure handling, ## Self-check"
-
-  - id: output-path-correct
-    name: Output path and frontmatter fields correct
-    type: deterministic
-    prompt: "Write a new skill for sending Slack notifications on deploy events, category: deploy"
-    expected_output: A SKILL.md with correct output path stated and all required frontmatter fields present.
-    assertions:
-      - "Output contains '.agents/skills/' in the stated output path"
-      - "Output contains 'metadata:' and 'category:' in frontmatter"
-      - "Output contains 'version:'"
-      - "Output contains 'when:'"
-
-  - id: output-trigger-tested-before-body
-    name: Trigger description tested before body content written
-    type: llm-rubric
-    prompt: "Write a new skill for summarising pull request diffs"
-    expected_output: The skill presents a trigger description and tests it against at least 3 cases (explicit, implicit, negative) before proposing or writing any body section content.
-    assertions:
-      - "The skill proposes a trigger description and explicitly tests it against an explicit query, an implicit query, and a negative query before writing any body section"
-      - "The skill walks through each body section individually and seeks confirmation before writing the file"