headwater-ai
Official@headwater-ai
Headwater-ai provides governed documentation engineering and n8n platform development skills covering taxonomy control, STE editing, OAuth2 credentials, RBAC endpoints, and PR lifecycle management.
Agent Skills by headwater-ai
Showing 9 vetted skills indexed across 1 GitHub repositories.
headwater-aiste-editor
Rewrites technical documentation to ASD-STE100 Simplified Technical English Issue 9 rules.
headwater-aiheadwater-engine
Builds the headwater Rust workspace and runs its CLI verbs against a corpus.
headwater-aiheadwater-sweep
Audit a documentation corpus slice for contradictions, supersessions, and undefined concepts.
headwater-airepo-cleanup
Deletes merged git worktrees, local branches, and remote branches after pull request merges.
headwater-aiheadwater-taxonomy
Validates and resolves taxonomy declarations into a committed lock file for the Headwater documentation engine.
headwater-aiheadwater-authoring
Drafts governed documentation documents through the headwater engine's scaffolding verb.
headwater-aiheadwater-orient
Locate relevant documents in a typed documentation corpus using graph-based routing commands.
headwater-aihw-run-policy
Provides standing rulings and environment constraints for Headwater build-order run stages.
headwater-aihw-verification-bar
Defines adversarial verification checks that branches must survive before merging.
Frequently Asked Questions About headwater-ai
FAQPage SchemaWhat tasks can I perform using headwater-ai's skills?▼
You can edit documentation to ASD-STE100 Simplified Technical English, manage a governed document taxonomy, add OAuth2 credentials to n8n nodes, author TypeORM database migrations, protect REST endpoints with RBAC scopes, create Linear tickets and GitHub issues, manage stacked PRs, and review pull requests.
Who are headwater-ai's skills designed for?▼
They target n8n platform engineers, technical writers working under ASD-STE100 controlled vocabulary, and maintainers of governed documentation repositories. Contributors handling community PRs, database migrations, telemetry events, and editor-ui experiments in the n8n monorepo are the primary audience.
What prerequisites do headwater-ai's skills require?▼
Several skills require an authenticated GitHub CLI (gh auth login) and a Linear MCP connection for ticket operations. Optional dependencies include a Notion MCP, the loom-transcript skill, and curl. The Headwater engine skills require building the repository's engine before running cargo or CLI commands.
How do the Headwater documentation governance skills work together?▼
headwater-engine builds the repository engine and runs its verbs; headwater-taxonomy changes declared kinds, facets, and relations; headwater-authoring drafts governed documents; headwater-orient queries the corpus graph; and headwater-sweep audits coherence, reporting contradictions as proposals a person accepts.
Are headwater-ai's skills open source?▼
The manifest pins many skills byte-for-byte from the upstream n8n-io/n8n repository (commit b0550cb3) and the github/gh-stack extension v0.0.9, with Headwater adding provenance metadata. Licensing follows those upstream sources; no separate commercial pricing is indicated in the manifest.