[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNK8GWCP3CTXG4XY9TQVMY":3,"skill-same:01M7DNK8GWCP3CTXG4XY9TQVMY":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M7DNK8GWCP3CTXG4XY9TQVMY","nika",null,"Runs repeatable AI work as checked, budgeted workflow files.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnika\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nika\ndescription: \"Runs repeatable AI work as checked, budgeted workflow files.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fsupernovae-st\u002Fnika-agents\u002Ftree\u002Fmain\u002Fskills\u002Fnika\nsource_repo: supernovae-st\u002Fnika-agents\nsource_type: community\nversion: 1.1.0\nauthor: Thibaut Melen (@ThibautMelen) · SuperNovae Studio (github.com\u002Fsupernovae-st)\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fsupernovae-st\u002Fnika-agents\u002Fblob\u002Fmain\u002FLICENSE\nplatforms: [linux, macos]\nprerequisites:\n  commands: [nika]\nmetadata:\n  hermes:\n    tags: [Workflow, Automation, Deterministic, Cost-Control, Audit, Local-First, MCP]\n    category: autonomous-ai-agents\n    related_skills: [opencode, claude-code, codex]\n    homepage: https:\u002F\u002Fnika.sh\n    requires_toolsets: [terminal]\n---\n\n# Nika Skill\n\nUse [Nika](https:\u002F\u002Fnika.sh) as a deterministic workflow worker orchestrated by\nthe Hermes `terminal` tool. Nika is an open-source (AGPL) Rust engine that captures\na repeatable AI task as a plain-text `*.nika.yaml` file, audits it **before a\nsingle token is spent** (plan, cost floor, secret flows, types), executes it\nagainst local or cloud providers (Ollama\u002Fllama.cpp\u002FvLLM included), and records\na tamper-evident trace.\n\nDivision of labor: **Hermes orchestrates · Nika captures repeatable work as a\ncheckable file and runs it with receipts.** Nika is NOT another coding agent —\nfor autonomous coding, use the `opencode` skill. Delegate to Nika when the\nwork should be *repeatable, budgeted, and auditable*.\n\n## When to Use\n\n- The user asks to run, check, or author a `*.nika.yaml` workflow\n- A task will be repeated (daily digest, triage, ETL, report, multi-step LLM\n  pipeline) — capture it as a workflow instead of re-prompting\n- The user wants a hard cost cap, a cost estimate before running, or\n  receipts\u002Faudit of what ran\n- A pipeline mixes models\u002Fproviders (local + cloud) or mixes LLM steps with\n  shell\u002FHTTP\u002Ffile steps\n- The user wants a run they can replay, verify, or reproduce later\n\n### When NOT to use\n\n- One-off questions or single tool calls — just answer or use a tool\n- Autonomous code implementation\u002Frefactoring\u002FPR review — use the `opencode` skill\n- Interactive back-and-forth tasks — workflows are non-interactive by design\n\n## Prerequisites\n\n- Nika installed: `brew install supernovae-st\u002Ftap\u002Fnika` — other install\n  paths (script, manual download) are documented at https:\u002F\u002Fnika.sh: installing\n  is a human step, not something this skill runs\n- Verify: `terminal(command=\"nika --version\")`\n- Zero keys needed for local\u002Foffline work: `--model mock\u002Fecho` (offline) and\n  `--model ollama\u002F...` (local) run without any API key\n- Cloud providers read standard env vars from the shell;\n  `terminal(command=\"nika doctor\")` diagnoses and prints exact fix commands\n\n## How to Run\n\nProve the toolchain offline first (no key, no network):\n\n```\nterminal(command=\"nika examples run 01-hello --model mock\u002Fecho\")\n```\n\nRun a real workflow — local model first:\n\n```\nterminal(command=\"nika run flow.nika.yaml --model ollama\u002Fqwen3.5:4b\", workdir=\"~\u002Fproject\")\n```\n\nCloud model with a hard budget (always set one for paid models):\n\n```\nterminal(command=\"nika run flow.nika.yaml --model mistral\u002Fmistral-small-latest --max-cost-usd 0.25\", workdir=\"~\u002Fproject\")\n```\n\nPass workflow variables:\n\n```\nterminal(command=\"nika run report.nika.yaml --var city=Paris --var days=7 --max-cost-usd 0.50\", workdir=\"~\u002Fproject\")\n```\n\nLong runs: launch in background and poll — do not block the turn:\n\n```\nterminal(command=\"nika run long.nika.yaml --max-cost-usd 1.00\", workdir=\"~\u002Fproject\", background=true)\nprocess(action=\"poll\", session_id=\"\u003Cid>\")\nprocess(action=\"log\", session_id=\"\u003Cid>\")\n```\n\n### The check-before-run law\n\nNever run a workflow you have not checked. `nika check` is a static pre-flight\n(no tokens spent, no network): plan shape, cost floor, secret-flow analysis,\ntype checks, tool args.\n\n```\nterminal(command=\"nika check flow.nika.yaml --json\", workdir=\"~\u002Fproject\")\n```\n\nFindings carry `NIKA-XXXX` codes that explain themselves via\n`nika explain NIKA-XXXX`. Exit 0 = green, safe to run. Fix findings before\nrunning — never suppress them.\n\n### Authoring a workflow\n\nTurn a repeated task into a file. List templates, then instantiate:\n\n```\nterminal(command=\"nika new --from '?'\")\nterminal(command=\"nika new flow.nika.yaml --from chain\", workdir=\"~\u002Fproject\")\n```\n\n`--from` also accepts plain-words intent. Edit the skeleton (`vars:`,\n`tasks:`, `outputs:`), then **check it**. `nika explain flow.nika.yaml`\nnarrates what it will do, the waves, the cost floor, and what it touches —\nbefore anything runs.\n\nThe artifact you are producing looks like this (checks clean on 0.98):\n\n```yaml\nnika: v1\nworkflow: daily-brief\nmodel: ollama\u002Fqwen3.5:4b\ntasks:\n  - id: fetch\n    invoke:\n      tool: \"nika:fetch\"\n      args: { url: \"https:\u002F\u002Fhn.algolia.com\u002Fapi\u002Fv1\u002Fsearch?tags=front_page\" }\n  - id: brief\n    depends_on: [fetch]\n    infer:\n      max_tokens: 300\n      prompt: |\n        Five bullet points, most signal first: ${{ tasks.fetch.output }}\noutputs:\n  brief: ${{ tasks.brief.output }}\n```\n\nOne file, plain YAML: tasks, an explicit dependency, a bounded model step,\na declared output. That file is what gets checked, run, diffed and reused.\n\n### Cost honesty\n\n- When the workflow prices above the budget, `--max-cost-usd` refuses to\n  start (exit 2, zero tokens) — and since 0.99 the pre-start floor prices\n  the EFFECTIVE model, `--model` override included\n- Mid-run, the ledger stops the workflow the moment real spend crosses the\n  budget: the crossing call completes, nothing new starts, the run fails\n  `NIKA-1704` (exit 1) with spent-vs-budget\n- Estimates use LIST RATES from the vendored public catalog; local · mock ·\n  unpriced work is never blocked\n- A model absent from the catalog meters as $0 — a paid *uncataloged* model\n  runs with no budget protection; prefer cataloged ids (`nika catalog`)\n- Report the cost line from the final run card (the summary block `nika\n  run` prints last — status, cost, trace path) back to the user verbatim\n\n### Receipts and verification\n\nEvery run writes a trace under `.nika\u002Ftraces\u002F` — the run card prints the\ntrace path on its `trace:` line. Both commands take that path (bare\ninvocations are a usage error):\n\n```\nterminal(command=\"nika trace show .nika\u002Ftraces\u002F\u003Crun>.ndjson\", workdir=\"~\u002Fproject\")\nterminal(command=\"nika trace verify .nika\u002Ftraces\u002F\u003Crun>.ndjson\", workdir=\"~\u002Fproject\")\n```\n\n`trace verify` checks the tamper-evidence hash chain: exit 0 intact · 2\nbroken · 3 pre-chain. Also useful: `nika trace outputs` · `nika trace flow` ·\n`nika trace reproduce` · `nika trace export` (OTLP lines).\n\n### Optional: MCP oracle tools\n\nNika also ships a read-only MCP oracle (`nika mcp`) exposing validation and\nlearning tools (`nika_check`, `nika_explain`, `nika_schema`, `nika_examples`,\n`nika_template`, `nika_canon`, `nika_catalog`, `nika_tools`). If the user\nwants those wired into their agent client, point them at the wiring guide —\nhttps:\u002F\u002Fgithub.com\u002Fsupernovae-st\u002Fnika-agents\u002Ftree\u002Fmain\u002Fintegrations\u002Fmcp —\nediting the client's own configuration is the user's step, never this\nskill's. Without the oracle, everything above still works over the terminal;\nrunning workflows stays there regardless, where the budget flags and traces\nlive.\n\n## Quick Reference\n\n| Command | Use |\n|---------|-----|\n| `nika welcome` | What Nika is + what this machine has (offline, exit 0) |\n| `nika new \u003Cfile> --from \u003Ctemplate>` | Scaffold a workflow (`--from '?'` lists) |\n| `nika check \u003Cfile> --json` | Static pre-flight — ALWAYS before run |\n| `nika explain \u003Cfile>` | Narrate: waves, cost floor, touches |\n| `nika run \u003Cfile> --model \u003Cp\u002Fm> --max-cost-usd \u003Cusd>` | Execute with budget |\n| `nika test \u003Cfile>` | Golden test under the mock provider (offline) |\n| `nika trace show\u002Fverify\u002Foutputs\u002Fflow \u003Ctrace>` | Receipts after a run (path from the run card's `trace:` line) |\n| `nika doctor` | Diagnose env\u002Fkeys — prints exact fixes |\n| `nika catalog` | Provider\u002Fmodel ids + required env vars |\n\n## Procedure\n\n1. Verify readiness: `terminal(command=\"nika --version\")`; install per\n   Prerequisites if missing.\n2. If the task is new, scaffold: `nika new \u003Cfile> --from \u003Ctemplate>`.\n3. Check: `nika check \u003Cfile> --json`. Fix every finding\n   (`nika explain \u003Ccode>`). Do not run an unchecked file.\n4. Preview offline when useful: `nika run \u003Cfile> --model mock\u002Fecho`.\n5. Run with an explicit `--model` and, for any paid model, an explicit\n   `--max-cost-usd`.\n6. For long runs use `background=true` and poll with\n   `process(action=\"poll\"|\"log\")`.\n7. After the run: `nika trace show \u003Ctrace>` + `nika trace verify \u003Ctrace>`\n   (path from the run card); report outputs, actual cost, and the verify\n   verdict to the user.\n\n### Rules\n\n1. NEVER run an unchecked workflow — `nika check` first, every time.\n2. ALWAYS pass `--max-cost-usd` when the model is a paid cloud model.\n3. Prefer local models (`ollama\u002F...`) or `mock\u002Fecho` for drafts; escalate to\n   cloud models only when needed.\n4. Report the final run card honestly: status, actual cost, trace path,\n   `trace verify` verdict.\n5. One workflow file per delegated task; keep files in the user's repo so\n   they are diffable and reusable.\n6. If a run fails, read `nika explain \u003CNIKA-code>` before retrying — do not\n   blind-retry.\n\n## Pitfalls\n\n- `nika run` renders live on a TTY; when piped (Hermes terminal), output can\n  stay quiet until completion — for anything long, prefer `background=true` +\n  poll, then read `nika trace show \u003Ctrace>` for the final card.\n- `nika new` with no `--from` opens a guided TTY flow; in a pipe it fails\n  fast naming the flag — always pass `--from \u003Ctemplate>` when delegating.\n- The budget guard stops NEW admissions: one wide parallel wave can overshoot\n  by that wave's spend. Tighten with `max_parallel:` when the budget is strict.\n- Uncataloged model ids meter as $0 — never rely on `--max-cost-usd` for a\n  custom endpoint model.\n- Workflow `outputs:` are not resolved on a budget stop — per-task values\n  live in the trace (`nika trace outputs`).\n\n## Limitations\n\n- Static checks reduce risk but cannot prove that remote content, shell steps,\n  provider behavior, or generated outputs are safe or correct.\n- Cost caps are not reliable for uncataloged paid models and a parallel wave\n  can overshoot before new work is stopped; require explicit user approval for\n  paid runs and report the actual ledger result.\n- Trace verification proves integrity of the recorded chain, not correctness\n  of the workflow or truth of its outputs.\n\n## Verification\n\nSmoke test (offline, zero keys):\n\n```\nterminal(command=\"nika examples run 01-hello --model mock\u002Fecho\")\n```\n\nSuccess criteria: run completes exit 0 with a final run card · `nika check`\nexits 0 before any real run · `nika trace verify` exits 0 after the run.\n","# Nika Skill\n\nUse [Nika](https:\u002F\u002Fnika.sh) as a deterministic workflow worker orchestrated by\nthe Hermes `terminal` tool. Nika is an open-source (AGPL) Rust engine that captures\na repeatable AI task as a plain-text `*.nika.yaml` file, audits it **before a\nsingle token is spent** (plan, cost floor, secret flows, types), executes it\nagainst local or cloud providers (Ollama\u002Fllama.cpp\u002FvLLM included), and records\na tamper-evident trace.\n\nDivision of labor: **Hermes orchestrates · Nika captures repeatable work as a\ncheckable file and runs it with receipts.** Nika is NOT another coding agent —\nfor autonomous coding, use the `opencode` skill. Delegate to Nika when the\nwork should be *repeatable, budgeted, and auditable*.\n\n## When to Use\n\n- The user asks to run, check, or author a `*.nika.yaml` workflow\n- A task will be repeated (daily digest, triage, ETL, report, multi-step LLM\n  pipeline) — capture it as a workflow instead of re-prompting\n- The user wants a hard cost cap, a cost estimate before running, or\n  receipts\u002Faudit of what ran\n- A pipeline mixes models\u002Fproviders (local + cloud) or mixes LLM steps with\n  shell\u002FHTTP\u002Ffile steps\n- The user wants a run they can replay, verify, or reproduce later\n\n### When NOT to use\n\n- One-off questions or single tool calls — just answer or use a tool\n- Autonomous code implementation\u002Frefactoring\u002FPR review — use the `opencode` skill\n- Interactive back-and-forth tasks — workflows are non-interactive by design\n\n## Prerequisites\n\n- Nika installed: `brew install supernovae-st\u002Ftap\u002Fnika` — other install\n  paths (script, manual download) are documented at https:\u002F\u002Fnika.sh: installing\n  is a human step, not something this skill runs\n- Verify: `terminal(command=\"nika --version\")`\n- Zero keys needed for local\u002Foffline work: `--model mock\u002Fecho` (offline) and\n  `--model ollama\u002F...` (local) run without any API key\n- Cloud providers read standard env vars from the shell;\n  `terminal(command=\"nika doctor\")` diagnoses and prints exact fix commands\n\n## How to Run\n\nProve the toolchain offline first (no key, no network):\n\n```\nterminal(command=\"nika examples run 01-hello --model mock\u002Fecho\")\n```\n\nRun a real workflow — local model first:\n\n```\nterminal(command=\"nika run flow.nika.yaml --model ollama\u002Fqwen3.5:4b\", workdir=\"~\u002Fproject\")\n```\n\nCloud model with a hard budget (always set one for paid models):\n\n```\nterminal(command=\"nika run flow.nika.yaml --model mistral\u002Fmistral-small-latest --max-cost-usd 0.25\", workdir=\"~\u002Fproject\")\n```\n\nPass workflow variables:\n\n```\nterminal(command=\"nika run report.nika.yaml --var city=Paris --var days=7 --max-cost-usd 0.50\", workdir=\"~\u002Fproject\")\n```\n\nLong runs: launch in background and poll — do not block the turn:\n\n```\nterminal(command=\"nika run long.nika.yaml --max-cost-usd 1.00\", workdir=\"~\u002Fproject\", background=true)\nprocess(action=\"poll\", session_id=\"\u003Cid>\")\nprocess(action=\"log\", session_id=\"\u003Cid>\")\n```\n\n### The check-before-run law\n\nNever run a workflow you have not checked. `nika check` is a static pre-flight\n(no tokens spent, no network): plan shape, cost floor, secret-flow analysis,\ntype checks, tool args.\n\n```\nterminal(command=\"nika check flow.nika.yaml --json\", workdir=\"~\u002Fproject\")\n```\n\nFindings carry `NIKA-XXXX` codes that explain themselves via\n`nika explain NIKA-XXXX`. Exit 0 = green, safe to run. Fix findings before\nrunning — never suppress them.\n\n### Authoring a workflow\n\nTurn a repeated task into a file. List templates, then instantiate:\n\n```\nterminal(command=\"nika new --from '?'\")\nterminal(command=\"nika new flow.nika.yaml --from chain\", workdir=\"~\u002Fproject\")\n```\n\n`--from` also accepts plain-words intent. Edit the skeleton (`vars:`,\n`tasks:`, `outputs:`), then **check it**. `nika explain flow.nika.yaml`\nnarrates what it will do, the waves, the cost floor, and what it touches —\nbefore anything runs.\n\nThe artifact you are producing looks like this (checks clean on 0.98):\n\n```yaml\nnika: v1\nworkflow: daily-brief\nmodel: ollama\u002Fqwen3.5:4b\ntasks:\n  - id: fetch\n    invoke:\n      tool: \"nika:fetch\"\n      args: { url: \"https:\u002F\u002Fhn.algolia.com\u002Fapi\u002Fv1\u002Fsearch?tags=front_page\" }\n  - id: brief\n    depends_on: [fetch]\n    infer:\n      max_tokens: 300\n      prompt: |\n        Five bullet points, most signal first: ${{ tasks.fetch.output }}\noutputs:\n  brief: ${{ tasks.brief.output }}\n```\n\nOne file, plain YAML: tasks, an explicit dependency, a bounded model step,\na declared output. That file is what gets checked, run, diffed and reused.\n\n### Cost honesty\n\n- When the workflow prices above the budget, `--max-cost-usd` refuses to\n  start (exit 2, zero tokens) — and since 0.99 the pre-start floor prices\n  the EFFECTIVE model, `--model` override included\n- Mid-run, the ledger stops the workflow the moment real spend crosses the\n  budget: the crossing call completes, nothing new starts, the run fails\n  `NIKA-1704` (exit 1) with spent-vs-budget\n- Estimates use LIST RATES from the vendored public catalog; local · mock ·\n  unpriced work is never blocked\n- A model absent from the catalog meters as $0 — a paid *uncataloged* model\n  runs with no budget protection; prefer cataloged ids (`nika catalog`)\n- Report the cost line from the final run card (the summary block `nika\n  run` prints last — status, cost, trace path) back to the user verbatim\n\n### Receipts and verification\n\nEvery run writes a trace under `.nika\u002Ftraces\u002F` — the run card prints the\ntrace path on its `trace:` line. Both commands take that path (bare\ninvocations are a usage error):\n\n```\nterminal(command=\"nika trace show .nika\u002Ftraces\u002F\u003Crun>.ndjson\", workdir=\"~\u002Fproject\")\nterminal(command=\"nika trace verify .nika\u002Ftraces\u002F\u003Crun>.ndjson\", workdir=\"~\u002Fproject\")\n```\n\n`trace verify` checks the tamper-evidence hash chain: exit 0 intact · 2\nbroken · 3 pre-chain. Also useful: `nika trace outputs` · `nika trace flow` ·\n`nika trace reproduce` · `nika trace export` (OTLP lines).\n\n### Optional: MCP oracle tools\n\nNika also ships a read-only MCP oracle (`nika mcp`) exposing validation and\nlearning tools (`nika_check`, `nika_explain`, `nika_schema`, `nika_examples`,\n`nika_template`, `nika_canon`, `nika_catalog`, `nika_tools`). If the user\nwants those wired into their agent client, point them at the wiring guide —\nhttps:\u002F\u002Fgithub.com\u002Fsupernovae-st\u002Fnika-agents\u002Ftree\u002Fmain\u002Fintegrations\u002Fmcp —\nediting the client's own configuration is the user's step, never this\nskill's. Without the oracle, everything above still works over the terminal;\nrunning workflows stays there regardless, where the budget flags and traces\nlive.\n\n## Quick Reference\n\n| Command | Use |\n|---------|-----|\n| `nika welcome` | What Nika is + what this machine has (offline, exit 0) |\n| `nika new \u003Cfile> --from \u003Ctemplate>` | Scaffold a workflow (`--from '?'` lists) |\n| `nika check \u003Cfile> --json` | Static pre-flight — ALWAYS before run |\n| `nika explain \u003Cfile>` | Narrate: waves, cost floor, touches |\n| `nika run \u003Cfile> --model \u003Cp\u002Fm> --max-cost-usd \u003Cusd>` | Execute with budget |\n| `nika test \u003Cfile>` | Golden test under the mock provider (offline) |\n| `nika trace show\u002Fverify\u002Foutputs\u002Fflow \u003Ctrace>` | Receipts after a run (path from the run card's `trace:` line) |\n| `nika doctor` | Diagnose env\u002Fkeys — prints exact fixes |\n| `nika catalog` | Provider\u002Fmodel ids + required env vars |\n\n## Procedure\n\n1. Verify readiness: `terminal(command=\"nika --version\")`; install per\n   Prerequisites if missing.\n2. If the task is new, scaffold: `nika new \u003Cfile> --from \u003Ctemplate>`.\n3. Check: `nika check \u003Cfile> --json`. Fix every finding\n   (`nika explain \u003Ccode>`). Do not run an unchecked file.\n4. Preview offline when useful: `nika run \u003Cfile> --model mock\u002Fecho`.\n5. Run with an explicit `--model` and, for any paid model, an explicit\n   `--max-cost-usd`.\n6. For long runs use `background=true` and poll with\n   `process(action=\"poll\"|\"log\")`.\n7. After the run: `nika trace show \u003Ctrace>` + `nika trace verify \u003Ctrace>`\n   (path from the run card); report outputs, actual cost, and the verify\n   verdict to the user.\n\n### Rules\n\n1. NEVER run an unchecked workflow — `nika check` first, every time.\n2. ALWAYS pass `--max-cost-usd` when the model is a paid cloud model.\n3. Prefer local models (`ollama\u002F...`) or `mock\u002Fecho` for drafts; escalate to\n   cloud models only when needed.\n4. Report the final run card honestly: status, actual cost, trace path,\n   `trace verify` verdict.\n5. One workflow file per delegated task; keep files in the user's repo so\n   they are diffable and reusable.\n6. If a run fails, read `nika explain \u003CNIKA-code>` before retrying — do not\n   blind-retry.\n\n## Pitfalls\n\n- `nika run` renders live on a TTY; when piped (Hermes terminal), output can\n  stay quiet until completion — for anything long, prefer `background=true` +\n  poll, then read `nika trace show \u003Ctrace>` for the final card.\n- `nika new` with no `--from` opens a guided TTY flow; in a pipe it fails\n  fast naming the flag — always pass `--from \u003Ctemplate>` when delegating.\n- The budget guard stops NEW admissions: one wide parallel wave can overshoot\n  by that wave's spend. Tighten with `max_parallel:` when the budget is strict.\n- Uncataloged model ids meter as $0 — never rely on `--max-cost-usd` for a\n  custom endpoint model.\n- Workflow `outputs:` are not resolved on a budget stop — per-task values\n  live in the trace (`nika trace outputs`).\n\n## Limitations\n\n- Static checks reduce risk but cannot prove that remote content, shell steps,\n  provider behavior, or generated outputs are safe or correct.\n- Cost caps are not reliable for uncataloged paid models and a parallel wave\n  can overshoot before new work is stopped; require explicit user approval for\n  paid runs and report the actual ledger result.\n- Trace verification proves integrity of the recorded chain, not correctness\n  of the workflow or truth of its outputs.\n\n## Verification\n\nSmoke test (offline, zero keys):\n\n```\nterminal(command=\"nika examples run 01-hello --model mock\u002Fecho\")\n```\n\nSuccess criteria: run completes exit 0 with a final run card · `nika check`\nexits 0 before any real run · `nika trace verify` exits 0 after the run.\n",{"name":5,"risk":24,"author":25,"source":26,"license":15,"version":27,"metadata":28,"platforms":46,"description":7,"source_repo":49,"source_type":50,"prerequisites":51,"license_source":53},"critical","Thibaut Melen (@ThibautMelen) · SuperNovae Studio (github.com\u002Fsupernovae-st)","https:\u002F\u002Fgithub.com\u002Fsupernovae-st\u002Fnika-agents\u002Ftree\u002Fmain\u002Fskills\u002Fnika","1.1.0",{"hermes":29},{"tags":30,"category":38,"homepage":39,"related_skills":40,"requires_toolsets":44},[31,32,33,34,35,36,37],"Workflow","Automation","Deterministic","Cost-Control","Audit","Local-First","MCP","autonomous-ai-agents","https:\u002F\u002Fnika.sh",[41,42,43],"opencode","claude-code","codex",[45],"terminal",[47,48],"linux","macos","supernovae-st\u002Fnika-agents","community",{"commands":52},[5],"https:\u002F\u002Fgithub.com\u002Fsupernovae-st\u002Fnika-agents\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fnika",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill nika",{"tool":67,"command":68},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill nika",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill nika","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnika\u002FSKILL.md",true,[],[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]