Create, validate, and debug AI workflows as checkable YAML files with cost caps, permit boundaries, and trace forensics. Automates auditing, migration from scripts, and session guardrails.
Audit a .nika.yaml workflow before it runs — findings with their NIKA-XXXX codes, cost envelope, permits
Narrate a workflow (waves · cost · touches · how to run) or teach a NIKA-XXXX error code
Scaffold a workflow from an embedded template, then audit it clean
Infer and paste the tightest permits boundary — the workflow's declared blast radius, default-deny from then on
Read a run's flight recorder — verdict, failing task, tamper check, and the exact resume line if paused
Writes and repairs .nika.yaml workflows with the deterministic authoring protocol. Use when the user wants repeatable AI work turned into a workflow file, asks for a .nika.yaml, or a nika check must pass. Routes intent to a template, fills the SLOT markers, then loops nika check until rc=0. Read-only oracle; it never runs the workflow.
Root-causes failed or paused Nika runs from their hash-chained traces. Use when nika run exited red, a run paused on a prompt and needs the exact resume line, a NIKA-XXXX runtime finding needs a cause, or a trace must be verified and explained. Evidence-first — reads .nika/traces via nika trace; proposes fixes and run lines, never executes them.
Ports an existing script, Makefile target, CI job or prompt chain to a checkable .nika.yaml workflow. Use when converting ad-hoc automation to nika, when a shell script wraps LLM/HTTP/file plumbing, or when a prompt chain in a doc should become a runnable, auditable file. Inventories side effects first, maps steps to the four verbs native-first, proves with check and a golden pin.
Author, check and repair Nika workflows (.nika.yaml files — the workflow language for AI). Use when writing or editing a *.nika.yaml file, converting a repeated AI task or prompt chain into a workflow, or when nika check reports NIKA-XXXX findings to fix.
Diagnose and repair failed, paused or suspicious Nika runs from their traces (.nika/traces). Use when nika run exited red, a run paused on a prompt, a NIKA-XXXX runtime finding needs a root cause, a trace must be read or tamper-verified, or a fixed workflow needs a surgical partial rerun.
Convert existing automation — shell scripts, Python glue, Makefile targets, CI jobs, prompt chains in docs — into checkable .nika.yaml workflows. Use when a script wraps LLM calls or HTTP/file plumbing, a prompt chain lives in a README or notebook, or ad-hoc automation needs audit, cost bounds and replayable traces.
Operate Nika workflows day-2 — spend caps, permits boundaries, secrets, model swaps (cloud/local), CI wiring, trace export. Use when hardening a working workflow for production, wiring it into CI or a scheduler, capping cost, tightening the permits boundary, swapping models, or exporting traces to OpenTelemetry.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Intent as Code. The workflow language for AI: one file, 4 verbs, one binary.
Useful AI work shouldn't disappear into chats. Nika turns repeatable AI work into files you can run, review, diff and share. If you do the same AI task twice, make it a workflow.
The pipeline is a file. A graph of model calls, tools and processes: a shape you declare, not glue you program. Nika audits that file before a token is spent (cost ceiling, permissions, secret flows, types), runs it on whichever LLM you choose, local first, no cloud required, and leaves every run a verifiable receipt. The language is an open Apache-2.0 spec; this repo is the reference engine, a single Rust binary (AGPL-3.0). The way SQL pairs with PostgreSQL, or the Dockerfile with Docker.
Yes.
brew install supernovae-st/tap/nika # or: curl -LsSf https://nika.sh/install.sh | sh
nika examples run 01-hello --model mock/echo # zero setup: no key, no model server
nika examples run 01-hello --model ollama/llama3.2:3b # got Ollama? the same run, real + local
# (first run loads the model into memory; later runs are much faster)

Nika audits a workflow before a single token is spent (plan, cost ceiling, secret flows, types, tool args), then runs it:
$ nika check brief.nika.yaml
✔ PLAN 2 wave(s) · 2 task(s) · max parallelism 1
wave 1 fetch_notes (exec · sh -c)
wave 2 brief (infer · ollama/llama3.2:3b)
✔ SECRETS no information-flow escapes
✔ TYPES every deep output reference fits its declared shape
✔ TOOLS every nika: tool names a canonical builtin
✔ ARGS every invoke arg key is declared + every required arg is present
✔ SCHEMA every authored schema: is satisfiable
✔ audited · 2 task(s) · 2 wave(s) · permits none · est ≥$0.0000
$ nika run brief.nika.yaml
🦋 nika · daily-brief · 2 tasks
✔ fetch_notes exec · cat
✔ brief infer · ollama/llama3.2:3b
── 2/2 done · $0.000 · elapsed 16.2s ───────────────────────────
An agent (or you, at 2am) writes a workflow. nika check audits the file
statically and names every fix; the run streams live; the trace is a
hash-chained receipt nika trace verify re-proves. The whole loop, captured
against the real binary:
What the audit catches before a single token is spent. Each finding
carries its NIKA-XXXX code, the exact source span, and the fix:
npx claudepluginhub supernovae-st/nika --plugin nikaAuthor, debug, operate and migrate AI workflows as checkable .nika.yaml files — 4 skills, 3 subagents, 2 rules, 5 slash commands (/nika:check · /nika:explain · /nika:new · /nika:trace · /nika:permits), 3 hooks on every surface — Cursor, Claude Code and Codex (one dialect, sniffed) (session context · check-on-edit · a guard that audits before any nika run) and the read-only Nika MCP oracle (8 tools · nika_check through nika_tools). Requires the nika binary: brew install supernovae-st/tap/nika
Production-grade n8n workflow building skills. Pairs with the official n8n instance-level MCP server to teach Claude how to architect, validate, and ship workflows that work in production.
Multi-agent workflow orchestration via YAML. Ships the conductor skill so the assistant can validate, run, debug, and author workflow files for the conductor CLI.
Pi Flow — author, enhance, and run structured filesystem-coordinated workflows (a DAG of producer/verify nodes) as a fleet of efficient pi agents driven by non-Claude coding-plan models, with Claude Code as the single console. Three skills: piflow-init (create a workflow), piflow-enhance (improve it), piflow-start (run + monitor it).
Claude Code plugin for n8n-as-code. Adds the n8n-manager and n8n-architect skills and uses the n8nac CLI as its local knowledge/runtime bridge.
Design complex n8n workflows with AI assistance - loops, branching, error handling
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques and MCP tools integration.\n\nExamples:\n- <example>\n Context: User wants to create a Slack notification workflow when a new GitHub issue is created.\n user: "I need to create an n8n workflow that sends a Slack message whenever a new GitHub issue is opened"\n assistant: "I'll use the n8n-workflow-builder agent to design and build this GitHub-to-Slack automation workflow with proper validation."\n <commentary>\n The user needs n8n workflow creation, so use the n8n-workflow-builder agent to handle the complete workflow design, validation, and deployment process.\n </commentary>\n</example>\n- <example>\n Context: User has an existing n8n workflow that needs debugging and optimization.\n user: "My n8n workflow keeps failing at the HTTP Request node, can you help me fix it?"\n assistant: "I'll use the n8n-workflow-builder agent to analyze and debug your workflow, focusing on the HTTP Request node configuration."\n <commentary>\n Since this involves n8n workflow troubleshooting and validation, use the n8n-workflow-builder agent to diagnose and fix the issue.\n </commentary>\n</example>\n- <example>\n Context: User wants to understand n8n best practices and available nodes for a specific use case.\n user: "What are the best n8n nodes for processing CSV data and sending email reports?"\n assistant: "I'll use the n8n-workflow-builder agent to explore the available nodes and recommend the best approach for CSV processing and email automation."\n <commentary>\n This requires n8n expertise and node discovery, so use the n8n-workflow-builder agent to provide comprehensive guidance.\n </commentary>\n</example>