Create, test, and develop swamp extensions — models, vaults, drivers, datastores, and reports. Covers Zod schemas, smoke testing, manifest.yaml, and the quality scorecard. Do NOT use for running existing models (swamp-model), using vaults (swamp-vault), workflows (swamp-workflow), debugging (swamp-troubleshooting), or publishing (swamp-extension-publish). Triggers on "create model", "custom model", "extension model", "zod schema", "build integration", "extensions/models", "implement model", "smoke test extension", "test extension", "manifest.yaml", "custom vault", "VaultProvider", "extensions/vaults", "custom driver", "ExecutionDriver", "extensions/drivers", "custom datastore", "DatastoreProvider", "extensions/datastores", "create report extension", "extensions/reports", "quality score", "scorecard", "improve my extension", "extension quality", "rubric", "fast-check", "extension grade", "symbols-docs".
Publish swamp extensions to the registry and manage post-publication lifecycle (deprecation). Enforces a state-machine checklist that verifies repo initialization, authentication, manifest validation, collective ownership, version bumping, formatting, and dry-run before allowing a push. Also covers deprecating and undeprecating published extensions. Do NOT use for creating extensions (that is swamp-extension), improving quality scores (that is swamp-extension), or smoke testing extensions before push (that is swamp-extension). Use when publishing, pushing, releasing, deprecating, or undeprecating extensions. Triggers on "publish extension", "push extension", "extension push", "publish to registry", "swamp extension push", "release extension", "prepare for publishing", "extension-publish", "deprecate extension", "undeprecate extension", "mark extension deprecated", "remove deprecation", "extension deprecated", "superseded by".
Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues. Use when the user wants to triage a swamp-club issue, generate an implementation plan, or iterate on a plan with feedback. Triggers on "triage issue", "triage #", "issue plan", "review plan", "iterate plan", "approve plan", "issue lifecycle".
Manage swamp vaults for secure secret storage — create vault instances, store and retrieve secrets, list keys, and use vault expressions in workflows. Use when working with existing vault types through the CLI. Do NOT use for creating custom vault TypeScript implementations (that is swamp-extension). Triggers on "vault", "secret", "secrets", "swamp vault", "store secret", "get secret", "vault expression", "aws secrets manager", "credential storage", "vault create", "vault put", "vault read-secret", "vault list-keys", "vault migrate", "vault annotate", "vault inspect", "annotation", "annotate secret", "inspect secret".
Fetch, edit, search, and submit issues to swamp Lab — view details, edit title/body, search/list issues, file bugs/features/security reports, post ripples (comments) with close/reopen, route to extension publishers. Triggers on "bug report", "feature request", "security report", "report bug", "file bug", "submit bug", "swamp bug", "swamp feature", "feedback", "report issue", "file issue", "extension bug", "ripple", "comment on issue", "close issue", "reopen issue", "get issue", "view issue", "fetch issue", "show issue", "edit issue", "update issue", "change issue title", "search issues", "list issues", "find issue", "issue search".
Work with swamp workflows for AI-native automation — define jobs and steps in YAML, wire models together with dependencies, validate DAGs, and inspect run history. Use when searching for workflows, creating new workflows, validating workflow definitions, running workflows, or viewing run history. Triggers on "swamp workflow", "swamp workflow create", "swamp workflow run", "swamp workflow validate", "workflow YAML", "workflow DAG", "wire models together", "model_method step", "workflows/*.yaml", "swamp run history", "swamp workflow logs", "debug swamp workflow". Use ONLY for swamp's declarative YAML workflow artifacts created via swamp workflow create — NOT for the Claude Code Workflow tool, multi-step agent task lists, worktrees, or cron/scheduled agent runs.
Run, configure, and view reports for swamp models and workflows. Use when running reports via CLI, configuring report selection in definition YAML, viewing report output, or filtering reports by label. Do NOT use for creating report extensions (that is swamp-extension) or debugging report failures (that is swamp-troubleshooting). Triggers on "run report", "swamp report", "model report", "report output", "report label", "skip report", "report results", "cost report", "audit report", "workflow report", "report get", "report filtering".
Work with existing swamp models — structured automation units that define typed schemas, methods (validate, transform, enrich), and outputs for data processing. Use when searching for model types, describing schemas, creating inputs, running or executing methods, viewing outputs, or managing lifecycle (edit, delete). Do NOT use when the user wants to build, create, or implement a custom model type, Zod schema, or TypeScript model — that is swamp-extension. Do NOT use for orchestrating or chaining models in workflows — that is swamp-workflow. Triggers on "swamp model", "model type", "model schema", "create input", "type search", "type describe", "run method", "execute method", "validation method", "transform method", "enrichment model", "model validate", "model delete", "model edit", "model output", "output logs", "output format", "CEL expression".