@iowarp/clio-coder 0.4.5 → 0.4.7

package/{skills → library/skills}/meta/clio-coder-dev/SKILL.md

@@ -11,7 +11,7 @@ version: 0.4.0
 license: Apache-2.0
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/meta/clio-coder-dev
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/meta/clio-coder-dev
   audit: pass
   provenance: designed
   eval-status: scenarios-recorded

package/{skills → library/skills}/meta/clio-coder-dev/evals.md

@@ -42,5 +42,5 @@ Expected:
 
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. NOT CLEANLY RUN: scenario id is D1; driver's --scenario S1 exited 2; re-run did not land before the time-box.

package/library/skills/meta/clio-coder-dev/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "clio-coder-dev",
+	"version": "0.4.0",
+	"description": "Governs changes to Clio Coder's own source and harness (TUI, skills, agents, tools, prompts, domains): what may change freely, what needs explicit user intent, and how to change it without breaking the architecture. Not for verifying a change against the harness; use clio-coder-test.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "clio-coder-dev",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/meta/clio-coder-test/SKILL.md

@@ -11,7 +11,7 @@ version: 0.3.0
 license: Apache-2.0
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/meta/clio-coder-test
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/meta/clio-coder-test
   audit: pass
   provenance: designed
   eval-status: scenarios-recorded

package/{skills → library/skills}/meta/clio-coder-test/evals.md

@@ -44,5 +44,5 @@ Expected:
 
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. NOT CLEANLY RUN: scenario id is T1; driver's --scenario S1 exited 2; re-run did not land before the time-box.

package/library/skills/meta/clio-coder-test/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "clio-coder-test",
+	"version": "0.3.0",
+	"description": "Verifies a Clio Coder source change against the current contract, smoke, boundary, and application test lanes, including temporary-state and local-provider harnesses. Not for deciding what may change; use clio-coder-dev.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "clio-coder-test",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/meta/credentials/SKILL.md

@@ -20,7 +20,7 @@ allowed-tools:
   - credential_present
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/meta/credentials
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/meta/credentials
   audit: pass
   provenance: designed
   eval-status: smoke-checked

package/{skills → library/skills}/meta/credentials/evals.md

@@ -100,5 +100,5 @@ protocol works under the current damage-control net.
 
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. PASS (smoke) with mixed rubric: presence flow ran without exposing values (b2/b4/b5 pass), b1/b3 failed; flagged for a full eval pass later.

package/library/skills/meta/credentials/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "credentials",
+	"version": "0.2.0",
+	"description": "Handles API keys, tokens, and facility credentials (kerberos tickets, globus and scheduler tokens, ssh agents, netrc) before a tool needs one, after an auth error, when a new secret is supplied, or when one may have leaked. Not for provider target configuration; use clio-coder auth and target settings.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "credentials",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/library/skills/meta/find-skills/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: find-skills
+description: Finds published skills and prepares their Library installation for the operator when the user asks whether a capability exists as a skill. Not for authoring a new skill; use skill-craft.
+triggers:
+  - find a skill
+  - is there a skill for this
+  - install a skill
+  - add an agent skill
+  - search the skills marketplace
+version: 0.2.1
+license: Apache-2.0
+allowed-tools:
+  - bash
+  - web_fetch
+  - read
+  - ls
+  - ask_user
+clio-coder:
+  registry-id: iowarp/clio-coder
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/meta/find-skills
+  audit: pass
+  provenance: designed
+  eval-status: scenarios-recorded
+  model-size: any
+---
+
+# Find Skills
+
+Find reusable skills through Clio-Coder's Library. Keep the package's origin,
+format, installation scope and actual recipe availability distinct. Library
+management is operator authority in Clio-Coder; the agent discovers, inspects
+and recommends without trying to write protected active roots.
+
+## Procedure
+
+1. **Search the Library first.** Run `clio-coder library search <query>` and
+   inspect `clio-coder library recipes --kind skill --json` for actual recipes.
+   In a Clio session, `context(scope="library", kind="skill", query="...")`
+   provides the same discovery facts. A catalog hint describes a package's
+   contents; it does not prove a skill is installed or usable. Check copy scope,
+   trust, enablement, integrity and resource diagnostics before reporting that
+   the capability is available. An installed but disabled package needs a
+   different action from a missing package.
+
+2. **Research external candidates when needed.** Browse https://skills.sh and
+   GitHub read-only. Record source URL, description and evidence of quality.
+   Distinguish a complete portable `plugin.json` package, a supported Claude
+   Code or Codex plugin, and a bare `SKILL.md` directory. A GitHub listing alone
+   does not prove its payload is directly installable. Do not execute a
+   candidate's setup instructions while researching it.
+
+3. **Prepare the exact operator action.** Use a typed reference such as
+   `clio-coder library install skill:context-handoff --project` for a catalog
+   package. Use `library install <package-path-or-github-tree-url>` for a
+   portable package, and `library import <path-or-github-tree-url> --dry-run`
+   to review a supported foreign plugin's projection and omitted features.
+   A bare skill needs a portable package envelope; use the authoring template
+   under `library/_authoring/templates/skill/` or the package authoring guide.
+   Do not promise that every skill URL works as an install source.
+
+4. **Use the operator's Library controls.** Point to `/library` or Alt+L for
+   review and installation. Show the requested scope explicitly: `--project`
+   uses `<cwd>/.clio-coder/plugins/<package-name>/`; `--user` uses
+   `<configDir>/plugins/<package-name>/` and is the CLI default. Every kind
+   uses that complete-package store. Loose `.clio-coder/skills/` files are a
+   separate operator-managed discovery surface. Honor authorization already
+   provided, while explaining that the Clio operator must apply the mutation
+   through the UI or CLI; do not retry blocked install commands as shell tricks.
+
+5. **Verify after the operator applies it.** Read
+   `clio-coder library recipes --kind skill --json` and
+   `clio-coder library inspect <kind>:<package-name> --json`. Confirm the actual
+   runtime name, whole-package owner, selected scope and recipe availability.
+   Report disabled, foreign, shadowed or invalid states plainly; an installed
+   directory alone is not success. Use `/skill <runtime-name>` for activation;
+   `/skills` opens the category browser. Do not invent an audit status.
+
+## Host boundaries
+
+For a Clio-Coder installation, keep management in its Library. External
+installers such as `npx skills add` target another host's roots and do not
+update Clio's package state. If the user explicitly wants a Claude Code or
+Codex installation instead, follow that host's documented marketplace or
+skill-installation route and name the destination clearly. The Clio-Coder
+library is portable; installing it for one host does not install it for all.

package/library/skills/meta/find-skills/evals.md

@@ -0,0 +1,65 @@
+# Evals — find-skills
+
+Run a subagent WITHOUT the skill to capture the gap, then WITH it to confirm.
+These scenarios describe the current Library contract; historical runs below
+are retained as evidence and do not validate the revised instructions.
+
+## F1 — review an external skill candidate
+
+Setup: an empty project. Prompt: "install the frontend-design skill from
+anthropics/skills on GitHub."
+Expected:
+- Identifies whether the selected source is a bare skill, portable package or
+  supported vendor plugin before choosing install versus import.
+- Gives the operator an exact command with the requested scope, or explains
+  that a bare skill first needs a portable package envelope.
+- Does not run an external installer or attempt to mutate Clio's protected
+  active skill/package roots through model tools.
+- Distinguishes the project package store `.clio-coder/plugins/<name>/` from
+  user `<configDir>/plugins/<name>/`; user scope is the CLI default.
+- After the fixture operator installs, verifies real runtime availability,
+  owner and scope through `library recipes --kind skill --json` and inspection.
+- Does not invent an audit status or claim installation before it happens.
+
+## F2 — capability question resolved locally
+
+Setup: run from a checkout of this repo, so the bundled catalog is discoverable.
+Prompt: "is there a skill that helps me hand off context between sessions?"
+Expected:
+- Searches the Library before browsing the web.
+- Surfaces `context-handoff` and its install target `skill:context-handoff`.
+- Distinguishes a catalog hint from an admitted recipe; does not call a merely
+  installed disabled or untrusted copy active.
+- Points the operator to `/library` or Alt+L for management and `/skill <name>`
+  for activation after installation.
+
+## F3 — ecosystem discovery and host boundaries
+
+Setup: any project. Prompt: "find me a skill for writing changelogs; nothing
+local matches."
+Expected:
+- Researches external candidates read-only and supplies source and format.
+- Prepares a Clio Library install/import review with an explicit scope when
+  the requested consumer is Clio-Coder.
+- Uses that host's documented install route if the user instead explicitly
+  requests Claude Code or Codex, and names that separate destination.
+- Never claims that installation for one host installs it for every host.
+
+## Baseline failure modes to watch for (RED)
+
+- Blindly recommends a bare skill URL as a complete portable package.
+- Installs through model tools, bypasses protected roots, or rewrites another
+  host's files without a request for that host.
+- Treats directory existence or package enablement as recipe availability.
+- Recommends a web result without source evidence or a usable operator action.
+
+## Instruction correction (2026-09-10)
+
+Version 0.2.1 corrects scope defaults, managed package locations, operator
+installation authority and vendor-format review. Scenarios recorded; no new
+model eval is claimed for this edit.
+
+## Smoke record (2026-08-13)
+
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
+(30B local, llamacpp on mini), full-auto sandbox. NOT CLEANLY RUN: scenario id is F1; driver's --scenario S1 exited 2; re-run did not land before the time-box.

package/library/skills/meta/find-skills/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "find-skills",
+	"version": "0.2.1",
+	"description": "Finds published skills and prepares their Library installation for the operator when the user asks whether a capability exists as a skill. Not for authoring a new skill; use skill-craft.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "find-skills",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/meta/herdr/SKILL.md

@@ -15,7 +15,7 @@ allowed-tools:
   - ask_user
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/meta/herdr
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/meta/herdr
   audit: pass
   provenance: adapted
   origin: https://github.com/herdrdev/herdr/tree/master/skills/herdr

package/{skills → library/skills}/meta/herdr/evals.md

@@ -34,5 +34,5 @@ Expected:
 
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. NOT SMOKED: requires HERDR_ENV and live panes; never run before the campaign time-box.

package/library/skills/meta/herdr/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "herdr",
+	"version": "0.2.0",
+	"description": "Launches, drives, or inspects another agent or command in a Herdr pane, tab, or workspace, including a second Clio Coder instance; requires HERDR_ENV=1. Not for background work a plain shell or dispatch already covers.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "herdr",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/meta/skill-craft/SKILL.md

@@ -7,14 +7,17 @@ triggers:
   - improve this skill
   - why isn't this skill firing
   - prune a skill body
-version: 0.3.0
+version: 0.3.1
 license: Apache-2.0
 allowed-tools:
   - read
   - grep
+  - write
+  - edit
+  - bash
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/meta/skill-craft
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/meta/skill-craft
   audit: pass
   provenance: designed
   eval-status: scenarios-recorded
@@ -26,15 +29,26 @@ clio-coder:
 A skill exists to wrangle predictability out of a stochastic system: the same
 process every run, not the same output. Every rule below is a lever on that
 one virtue. A disputed line is settled by running the skill, not by debate;
-in Clio that means `clio-coder skills eval`, and a shipped skill's `evals.md`
+in Clio that means `clio-coder eval skill`, and a shipped skill's `evals.md`
 Expected bullets are its completion criteria.
 
 ## Format and Location
 
-A skill is a folder holding a `SKILL.md`, written with the ordinary write
-tool. Project skills live in `.clio-coder/skills/<name>/`; user skills in the Clio
-config dir under `skills/<name>/`. The loader validates on load; check work
-with `clio-coder skills validate`. Frontmatter contract (Agent Skills compatible):
+A skill is a folder holding a `SKILL.md`. Author with ordinary write/edit tools
+in a draft directory such as `draft-skills/<name>/`, outside active skill and
+installed package roots. In this repository, curated sources live under
+`library/skills/<category>/<name>/`. Validate a draft with
+`clio-coder library validate draft-skills/<name>/SKILL.md`.
+
+For distribution, use the portable envelope in
+`library/_authoring/templates/skill/` and validate the complete package root.
+The operator installs it through the Library into the user or project package
+store (`<configDir>/plugins/` or `.clio-coder/plugins/`). Loose skills under
+`.clio-coder/skills/` and `<configDir>/skills/` are also operator-managed; Clio's
+model tools cannot author directly in those protected roots. Other hosts may
+consume the same `SKILL.md` through their own installation routes.
+
+Frontmatter contract (Agent Skills compatible):
 
 - `name`: lowercase-hyphen, ≤64 chars. Catalog convention requires it to match
   the folder; the runtime loader warns on a mismatch and uses the frontmatter
@@ -50,13 +64,13 @@ with `clio-coder skills validate`. Frontmatter contract (Agent Skills compatible
   grant. While every loaded skill declares `allowed-tools`, the turn's tool
   surface shrinks to their union; `disallowed-tools` always denies. Neither
   ever admits a tool the safety level would refuse. Canonical lowercase Clio
-  names only (see skills/README.md, "Claude Code interop").
+  names only (see library/skills/README.md, "Claude Code interop").
 - `requires`: `skill:<name>` dependencies; the loader warns when one is
   missing. Reference an installed skill by name instead of restating its job.
 - `clio-coder:`: the reserved publication block (`registry-id`, `source-url`,
   `audit`, `provenance` designed|adapted|imported with `origin` when not
   designed, `eval-status`, optional `model-size` and `agents`). Required for
-  catalog skills; approval is judged against it (skills/README.md).
+  catalog skills; approval is judged against it (library/skills/README.md).
 
 Sibling files (`references/*.md`, `evals.md`, scripts) ride along in the
 folder and load only when the body points at them.

package/{skills → library/skills}/meta/skill-craft/evals.md

@@ -7,10 +7,12 @@ WITH the skill to confirm it closes). Rubric is pass/fail per bullet.
 Setup: any repo. Prompt: "write a project skill called log-triage that greps
 service logs for errors, groups them by cause, and files a summary."
 Expected:
-- Writes `.clio-coder/skills/log-triage/SKILL.md` directly with the write tool.
+- Writes `draft-skills/log-triage/SKILL.md` outside protected active roots.
+- Supplies a portable package envelope and operator installation guidance when
+  distribution is requested; authoring does not silently activate the skill.
 - Description is triggers-only, front-loaded, no synonym-duplicated branches.
 - Every step ends on a checkable completion criterion, not "until done".
-- Frontmatter passes `clio-coder skills validate`.
+- Frontmatter passes `clio-coder library validate draft-skills/log-triage/SKILL.md`.
 
 ## S2 — prune an overgrown skill
 Setup: repo containing a 200-line skill whose body restates one rule three
@@ -35,7 +37,13 @@ Expected:
 - "Done when it works" completion criteria.
 - Rewording weak lines instead of deleting them.
 
+## Instruction correction (2026-09-10)
+
+Version 0.3.1 corrects draft authoring and operator installation paths and admits
+the ordinary write/edit/bash tools the existing author/validate procedure needs.
+Scenarios recorded; no new model eval is claimed.
+
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. NOT COMPARABLE: baseline arm hit the loop guard, so no baseline exists; treatment was visibly scaffolding a skill when the run was scored INFRA.

package/library/skills/meta/skill-craft/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "skill-craft",
+	"version": "0.3.1",
+	"description": "Writes, reviews, or prunes a SKILL.md, judging whether its description, body, and length earn their cost. Not for packaging a workflow that just happened; use workflow-distiller.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "skill-craft",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/planning/archify/SKILL.md

@@ -24,7 +24,7 @@ allowed-tools:
   - context
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/planning/archify
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/planning/archify
   audit: pass
   provenance: adapted
   origin: https://github.com/tt-a1i/archify/tree/v2.16.0/archify
@@ -40,19 +40,19 @@ clio-coder:
 # Archify
 
 Create a self-contained interactive HTML diagram from a small typed JSON
-specification. The renderer is the upstream archify package installed
-beside this file; the skill base directory is the directory that holds
-`bin/`. Every command below runs as
-`node .clio-coder/skills/archify/bin/archify.mjs ...` for a project-scope
-install, or `node <clio config dir>/skills/archify/bin/archify.mjs ...` for a
-user-scope install. No install step, no network, and no dependencies beyond
-Node 18 or later.
+specification. This library package contains Clio instructions; the renderer is
+an independently installed upstream Archify v2.16.0 package. Before authoring,
+locate its directory containing `bin/archify.mjs`, `schemas/` and `examples/`.
+If unavailable, ask the operator to prepare that upstream renderer; do not claim
+that installing this instruction package installed it. Below, `<renderer>` is
+that verified directory, and renderer-relative schema/example paths refer to it.
+The renderer needs Node 18 or later; ordinary rendering then needs no network.
 
 ## Fast authoring path
 
 1. Choose `architecture`, `workflow`, `sequence`, `dataflow`, or `lifecycle`
    from the question. When ambiguous, run
-   `node <skill>/bin/archify.mjs guide "<scenario>" --json`.
+   `node <renderer>/bin/archify.mjs guide "<scenario>" --json`.
 2. Read one matching schema in `schemas/`, `schemas/common.schema.json`, and
    one matching example in `examples/`. Read only those files. The example
    supplies field shape, never facts: author new stable ids, domain wording,
@@ -66,7 +66,7 @@ Node 18 or later.
 4. Validate after every edit and immediately before delivery:
 
    ```bash
-   node <skill>/bin/archify.mjs validate <type> <candidate.json> --quality showcase --json
+   node <renderer>/bin/archify.mjs validate <type> <candidate.json> --quality showcase --json
    ```
 
    A showcase pass reports all artifact checks with 0 composition errors
@@ -77,7 +77,7 @@ Node 18 or later.
 5. Deliver once, as the final acceptance command:
 
    ```bash
-   node <skill>/bin/archify.mjs deliver <type> <candidate.json> <output.html> --quality showcase --json
+   node <renderer>/bin/archify.mjs deliver <type> <candidate.json> <output.html> --quality showcase --json
    ```
 
    A non-zero exit is never success. A failed delivery preserves any previous
@@ -120,7 +120,7 @@ component map), `sequenceDiagram` becomes `sequence`, `stateDiagram` becomes
   say that the viewer chrome falls back to English.
 - Brand identity is explicit. Put a canonical built-in id in `brand` only
   when the node names that real product; query
-  `node <skill>/bin/archify.mjs brands "<name>" --json`. Never infer a brand
+  `node <renderer>/bin/archify.mjs brands "<name>" --json`. Never infer a brand
   from a role such as "database".
 - Never accept an edge crossing an unrelated opaque node, an ambiguous shared
   corridor, or a label masking another route.
@@ -180,7 +180,7 @@ verify(check="frontend", path="<output.html>")
 
 That validates structure, local references, and syntax, and loads the page
 in a headless browser when one is on PATH. Archify's own
-`node <skill>/bin/archify.mjs visual-check <output.html> --json` is optional:
+`node <renderer>/bin/archify.mjs visual-check <output.html> --json` is optional:
 it needs a system Chrome and fails with `viewer/chrome-unavailable` on
 headless nodes. Report that outcome as what it is, never as a pass.
 

package/library/skills/planning/archify/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "archify",
+	"version": "0.1.0",
+	"description": "Validated interactive system maps and diagrams as standalone HTML from a typed JSON spec, for one of five diagram types (architecture, workflow, sequence, dataflow, lifecycle). Use when the user asks to visualize architecture, a workflow, a call sequence, a data pipeline, or a state machine, or to map this repository. Not for ad hoc drawings or slide art, and not for Mermaid output; use the artifact tool for plain Markdown.",
+	"license": "MIT",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "archify",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/planning/architecture/SKILL.md

@@ -22,7 +22,7 @@ allowed-tools:
   - ask_user
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/planning/architecture
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/planning/architecture
   audit: pass
   provenance: adapted
   origin: https://github.com/coleam00/skills/tree/main/.claude/skills/architecture

package/{skills → library/skills}/planning/architecture/evals.md

@@ -32,7 +32,7 @@ Expected:
 
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. SMOKE ACTED but substance bullets failed (wrote final_report.md, skipped the loop). Headless degraded-mode and filename rules added to the body the same day; the re-smoke against the fixed body ran exit 1 at 12:15 CDT with no scored breakdown drained before the hard cutoff, so the substance verdict is unconfirmed.
 
 ## Battletest record (2026-09-03)

package/library/skills/planning/architecture/plugin.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "architecture",
+	"version": "0.4.1",
+	"description": "Decides the engineering approach for an intent in an interactive session: investigates, proposes two or three genuinely different approaches with trade-offs, recommends, lets the user decide, and writes the decision doc. Not a task-by-task plan; use cut-it. Not a multi-perspective debate; use design-council. Not product intent; use product-intent. Not a typed implementation handoff; use tech-spec.",
+	"license": "Apache-2.0",
+	"extensions": {
+		"ai.iowarp.clio": {
+			"manifestVersion": 1,
+			"kind": "skill",
+			"resources": {
+				"skills": "."
+			},
+			"components": [
+				{
+					"kind": "skill",
+					"id": "architecture",
+					"path": "SKILL.md"
+				}
+			]
+		}
+	}
+}

package/{skills → library/skills}/planning/backlog/SKILL.md

@@ -19,7 +19,7 @@ allowed-tools:
   - ask_user
 clio-coder:
   registry-id: iowarp/clio-coder
-  source-url: https://github.com/iowarp/clio-coder/tree/main/skills/planning/backlog
+  source-url: https://github.com/iowarp/clio-coder/tree/main/library/skills/planning/backlog
   audit: pass
   provenance: adapted
   origin: https://github.com/coleam00/skills/tree/main/.claude/skills/backlog

package/{skills → library/skills}/planning/backlog/evals.md

@@ -39,7 +39,7 @@ Expected:
 
 ## Smoke record (2026-08-13)
 
-One representative scenario via `clio-coder skills eval` against Nemo-3.5-Lightning
+One representative scenario via `clio-coder eval skill` against Nemo-3.5-Lightning
 (30B local, llamacpp on mini), full-auto sandbox. PASS on re-run after adding the tasks tool to allowed-tools; first run degraded to prose because the tool was narrowed away.
 
 ## Battletest record (2026-09-03)