Deterministic delegation: run repeatable jobs as checked workflow files
Turn a repeatable job into a checked Nika workflow that Hermes can run with an upfront cost audit and a verifiable hash-chained receipt.
Requirements
- The
nikaskill is required; its commands are CI-tested against each released binary before the skill can merge. - Ollama is optional for a real local model; the mock route works without it.
How to use
This is a first-party integration with a runnable offline demonstration that needs no keys.
Paid runs can be capped with --max-cost-usd, while the offline mock and Ollama routes need no keys.
Workflows are intentionally non-interactive; use OpenCode for autonomous coding and this route for repeatable digest, triage, ETL, or report pipelines.
The offline demonstration needs no API key or model server.
The engine is AGPL-3.0, while the specification and TypeScript SDK are Apache-2.0; the source was contributed by the Nika author.
- Install the single-binary runner and the skill.
brew install supernovae-st/tap/nika
hermes skills tap add supernovae-st/nika-agents
- No additional component is required for the offline demonstration.
Use a prompt to define the workflow.
Ask Hermes to capture a repeated job as a workflow and run it with receipts.
Use the nika skill. Create a workflow file daily-brief.nika.yaml that
fetches https://news.ycombinator.com/rss (feed mode), keeps the top 5
titles, and writes them to brief.md. Check it with nika check first,
run it on the mock model, then verify the trace and tell me the chain
head from the terminal output, not from memory.
Alternatively, give Hermes an existing workflow file.
Run nika check on report.nika.yaml, explain any findings with
nika explain, fix the file, and only run it once check passes.
Cap the run at $0.10 with --max-cost-usd.
Run the supplied demonstration offline with zero keys.
nika examples run 01-hello --model mock/echo # deterministic offline run
nika examples run 01-hello --model ollama/qwen3.5:4b # same run, real local model
nika trace verify # latest run · exit 0 = chain intact
Source: aliaihub/awesome-hermes-usecases and its contributors. License: CC-BY-4.0. Source license notice.
Translation and editorial adaptation by ClawCases.
>Resources
>Related Use Cases
Agent Merge-Conflict Arbiter
Resolve a git merge conflict between two agents' branches as an impartial third party: a neutral arbiter that takes both diffs and their stated intents and produces a merged result without overwriting either side.
AI-Powered Earnings Tracker
Stay on top of earnings season across dozens of tech companies without manually checking multiple sources and remembering report dates for every AI/tech earnings report.
Social Media Content Calendar
Plan a multi-platform social media campaign calendar from briefs through approvals to publishing or verified handoff, adapting post copy per channel and marking platform slots without a connector as handed-off rather than published.