git:20260923.03229b0 to git:20261020.b7790f6

@AGENTS.md

## Workflows (Claude Code)

Do NOT interpret workflow requests as a request to build a Claude Code agent

task list, spin up worktrees, or schedule a cron/remote agent. Only reach for

the harness orchestration tools (TaskCreate/TaskList, EnterWorktree, CronCreate,

RemoteTrigger) when the user explicitly names that mechanism (e.g. "task list",

"subagent", "worktree", "cron", "remote agent") or explicitly asks you to do the

work yourself step by step rather than author a swamp workflow.

## Skills

Skills live in `.claude/skills/<skill-name>/`.

IMPORTANT: Before creating or modifying ANY skill file, you MUST load the

`skill-creator` skill first. Do not skip this step — it contains the

authoritative guidelines for structure, frontmatter, and progressive disclosure.

This is a hard prerequisite, not a suggestion.

Repo-specific rules on top of skill-creator's guidance:

- `SKILL.md` must be uppercase — not `skill.md`.

- After editing any `.md` file in `.claude/skills/`, run `deno fmt` — skill

markdown follows the same formatting rules as all other files in this

repository.

After creating or modifying a skill, verify it before submitting:

- `npx tessl review run .claude/skills/<skill-name> --workspace swamp-club` —

quality review of the description and content; aim for an average score ≥ 90%.

It needs `TESSL_TOKEN` in the environment (export

`~/.config/swamp/verify.env`, see

`agent-constraints/verification-conventions.md`). CI enforces that threshold

for the bundled skills (`swamp`, `swamp-getting-started`) via

`deno run review-skills`; for other skills it is good hygiene, not a gate.

- `deno run eval-skill-triggers` — promptfoo trigger-routing evals for the

See `contributing/skills-pipeline.md` for the full skill testing pipeline.