[aitrawog]

Summary

AGENTS.md listed the corpus skills to load and never named the two skills this repo ships. Both now appear.

repo's own skills	strata (the headless gateway box) and strata-layer (the engine layer)
before	grep -c 'skills/strata/' -> 0, grep -c 'skills/strata-layer/' -> 0
after	1 and 1

Why it matters, and it is my omission: I moved both bodies into .agents/skills/ in layer-strata#15 and did not check that the
rulebook named them. A repo whose AGENTS.md does not enumerate its own skills is a repo where those skills are discoverable only
by listing a directory - and the org-wide migration's completion criterion requires each author-skill repo's AGENTS.md to agree
with its measured skill set.

Found by re-measuring rather than trusting: the enumeration check was reported as satisfied on data from roughly 115 rounds
earlier. Re-run today it found this repo at 1 of 2, and plugin-strata at 0 of 1 (plugin-strata#4).

How tested

Change class: docs. Seven added lines, no code, no schema, no pin.

$ git diff --numstat origin/main HEAD
7	0	AGENTS.md

This diff contains 7 insertions and 0 deletions across one file.

$ git ls-tree -r --name-only origin/main | grep -oE '\.agents/skills/[^/]+/SKILL\.md'
.agents/skills/strata-layer/SKILL.md
.agents/skills/strata/SKILL.md
$ grep -c 'skills/strata/'        AGENTS.md
1
$ grep -c 'skills/strata-layer/'  AGENTS.md
1

The repo ships exactly two skills and now names exactly two.

Negative control: the same two greps against origin/main's AGENTS.md return 0 and 0, so each check discriminates:

$ git show origin/main:AGENTS.md | grep -c 'skills/strata/'
0
$ git show origin/main:AGENTS.md | grep -c 'skills/strata-layer/'
0

Rulebook compliance

• R0: /charly-internals:skills governs where guidance belongs; this is the enumeration the repo was missing.
• R1: the finding is mine - #15 moved the bodies without updating the rulebook - and it is fixed here rather than filed.
• R2: no duplication - one entry per skill, in the one rulebook.
• R3: no workaround.
• R4: docs describe the product; nothing is being routed around.
• R5: no legacy path.
• R6: git status read first; fresh branch off origin/main; one commit, one push, no force.
• R7: both checks fail without the change - the negative control above.
• R8: no live service boundary.
• R9: no runtime claim; this is prose.
• R10: docs class - every non-runtime standard passes, and the greps are the evidence.

Change classification

Docs - seven lines adding this repo's two own skills to AGENTS.md with their scope and when to read them.

Filed issues

No new issue. Companion to plugin-strata#4, which fixes the same omission in the sibling repo; both were found by re-measuring a check that had been reported satisfied on stale data.

Agent: charly

Assisted-by: DeepSeek Harness ollama-cloud deepseek-v4.1-flash (documentation reviewed)

[github-actions]

Review — PASS

Head SHA: ca046d0a405e2fdf885977500b62d1f5c3bea978 (branch: fix/agents-skill-entries)

Change class: docs-only (AGENTS.md, +7/−0).

Security screen: PASS — no code, secrets, network, or guardrail weakening (the change adds a skills-enumeration section; it does not touch the rulebook's landing/attribution/no-force-push/no-direct-push rules, so T4 sign-off is not implicated).
Checklist: All applicable rules PASS or NA. Body's greps/negative control are internally consistent with the diff (grep -c 'skills/strata/'→1, skills/strata-layer/→1; main→0/0), attribution tier documentation reviewed is legal for a pure-docs diff, ## Filed issues correctly states none, and the body ends with the required Assisted-by: line. Placement: NA (no code layer touched).

Verdict: PASS

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run