Files

Defame1297 00daf285ec fix(kyberforge): tell an unparsable Contributing-files block from an explicit (none)

parse_contributing_files documented that callers depend on None vs [], because a
parse failure returning [] would silently disable the check. Only check 8
honoured it; checks 4/5 (skill-audit) and 3/4 (agent-audit) used a truthiness
test, so an unreadable block disabled them without a word.

Two live corpus entries were skipping this way. A sweep of all 32 sources.md
found 134 entries, exactly 2 parsing to None, both in gitea-files: one heading
carried an inline parenthetical that defeated both regexes, and one (none) was
written without its leading bullet. Also pins EMPTY_SOURCE_KEYS_RE to the two
indents parse_source_keys actually reads.

agent-audit had no INFO tier at all, so it gains one rather than reporting a
check that could not run as a FAIL.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti

2026-08-31 19:46:05 +00:00

README.md

fix(kyberforge): bridge apm content to Claude Code's flat plugin discovery

2026-08-13 16:59:03 +00:00

vale-wrap.sh

fix(kyberforge): bridge apm content to Claude Code's flat plugin discovery

2026-08-13 16:59:03 +00:00

validate-provenance.sh

fix(kyberforge): tell an unparsable Contributing-files block from an explicit (none)

2026-08-31 19:46:05 +00:00

validate.sh

fix(gates): block a dangling /name route with no preceding verb

2026-08-31 19:45:45 +00:00

README.md

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):

# /// script
# dependencies = ["requests>=2.31,<3"]
# requires-python = ">=3.11"
# ///
import requests

uv run scripts/my-script.py

If no scripts are needed

Delete this README and the scripts/ directory entirely.