git:20260825.693f684 to git:20260914.dbab098

1 added, 0 removed. Audit A to A.

# Skills

`skills/` contains the published packages. Before changing one, read

[`../docs/skills/skill-standard.md`](../docs/skills/skill-standard.md) and the

effective repository instructions.

## Design Rules

- Keep one public Skill per stable user intent and authority boundary.

+ - Keep project task state in the target repository. `to-task` owns the reusable transformation and reconciliation workflow, not a catalog-side copy of any project's ledger.

- Use profiles for framework or technology variants that share the same owner,

workflow, mutation boundary, and output.

- Keep `SKILL.md` concise. Link detailed checklists, examples, and variants directly

from it; keep references one level deep.

- Packages must be self-contained. They may use their own `scripts/`, `references/`,

and `assets/`, but must not depend on repository-root maintenance files at runtime.

- Keep provider-specific metadata in its provider surface. This catalog includes

`agents/openai.yaml` for OpenAI without treating it as portable frontmatter.

- Do not invent parallel per-provider files. Add another provider surface only when

that provider documents a real machine-readable contract that this catalog ships.

- Do not put installation, update, changelog, or repository-maintenance guidance in

published packages.

- Preserve unrelated changes and keep Git mutation in `repo-delivery`.

Shared package protocols are authored under `protocols/` and synchronized with

`python3 scripts/sync-shared-protocols.py`; do not hand-edit generated copies.

When adding, renaming, or removing a package, update `README.md`, `INSTALL.md`,

`skills.sh.json`, and `skills-index.json` in the same change. When routing meaning,

nearest neighbors, or capability keywords change, update the semantic index even when

the package set stays the same.

## Validation

Use risk-tiered validation during development. The canonical full gate remains

`bash scripts/check-skills.sh`; on macOS it resolves and verifies Homebrew Python,

refuses `/usr/bin/python3`, and uses `uv` with the pinned

`requirements-dev.txt` when available. Other platforms use their configured

`PYTHON_BIN` or `python3`.

For a bounded prose correction in one package, run exact-path whitespace/link checks

and the smallest directly affected validator or regression. Do not run the full gate

after every prose edit.

```bash

git diff --check -- skills/<name>

```

For a behavior, metadata, routing, schema, shared-protocol, or package-structure

change, run the focused `scripts/test_*.py` cases and validators that cover the

changed contract, plus shared-protocol sync checks when applicable. Expand to every

affected consumer, but do not substitute an unrelated full suite for missing focused

coverage.

For merge, release, catalog delivery, final fixed-basis acceptance, or an explicit

full-regression request, run:

```bash

bash scripts/check-skills.sh

```

For behavior changes, keep the repository routing matrix synchronized with the

affected Skill's normal use, nearest non-trigger or owner boundary, and critical stop.

The full gate runs the deterministic routing matrix, its committed no-new-regression

baseline, and a warning-only context report. Do not rerun it after an unchanged full

pass unless the basis or relevant gate inputs changed. Real host/model behavior still

requires representative live tasks when claimed. For a new or materially changed

behavior, a real-failure repair, or an improvement claim, run the actual Agent on a

fixed targeted prompt set and capture JSONL trace plus task artifacts. Cover explicit

and implicit/contextual use, the nearest non-trigger, an applicable valid no-op, and the

critical stop; score observable selection, process, outputs/effects, honest stop state,

and efficiency separately. Keep public cases synthetic and project-neutral, keep raw

business/project evidence ignored or private, and require human confirmation before

replacing the maintained basis. Static gate counts cannot substitute for this live

capability result. An explicitly requested independent provider/model remains a

required live case dimension: absent or mismatched provider evidence is `Not verified`,

not a waived pass. A formal cross-model benchmark remains optional.