ericrisco/rsc-harness / skills/n8n
n8n
VerifiedUse when operating a live n8n instance programmatically — its REST API (`{host}/api/v1`, `X-N8N-API-KEY`) or the n8n-mcp server — to create, validate, test, activate, update, delete workflows and read executions on self-host or n8n.cloud. NOT designing the flow or its importable JSON (that is `automation-flows`), NOT another platform (`make`, `zapier`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/cases.yaml | config | 3.9 KB |
| references/auth-and-selfhost.md | markdown | 2.8 KB |
| references/n8n-mcp-tools.md | markdown | 4.4 KB |
| references/rest-api-cheatsheet.md | markdown | 4.3 KB |
evals/README.md
View on GitHub# Evals — n8n
`cases.yaml` has three groups. `should_trigger` covers the operate tasks this skill owns: deploying a
workflow JSON over the REST API, the read-only-`active` gotcha, wiring n8n-mcp management tools,
running a workflow by id, hard-delete safety, and validate/autofix — with a Spanish phrasing. Each
`should_not_trigger` names a real sibling: flow design + importable JSON → automation-flows,
platform/cost choice → automation-strategy, another platform → make, a typed code client →
api-connector-builder, an in-app inbound receiver → webhooks. `capability` is one end-to-end deploy
scenario whose `must_include` rubric pins the current API/MCP calls, the honesty limits (read-only
`active`, no-input `execute`), and the irreversibility rule (export before hard delete).
No automated runner. Score by judgement: feed each `should_trigger`/`should_not_trigger` prompt to the
routing layer and confirm it activates or routes to the listed sibling; for `capability`, have the
skill produce the deploy plan/commands and check every `must_include` bullet by hand.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |