ericrisco/rsc-harness / skills/automation-flows
automation-flows
VerifiedUse when building or fixing a no-code automation on n8n, Make, or Zapier — trigger to multi-app steps with data mapping, dedup, retries and an error path — or picking the platform by billing unit (task vs credit vs execution). NOT a typed API client in code (that is api-connector-builder), NOT a webhook receiver in your own app (that is webhooks).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| evals/README.md | markdown | 1.2 KB |
| evals/cases.yaml | config | 3.3 KB |
| references/error-handling.md | markdown | 4.4 KB |
| references/n8n-workflow-json.md | markdown | 3.1 KB |
| scripts/verify.shexecutable | script | 2.2 KB |
evals/README.md
View on GitHub# Evals — automation-flows
`cases.yaml` holds three groups. `should_trigger` lists prompts where this skill must activate (canonical multi-app flows, error-handling fixes, platform-selection-by-billing, the double-fire/dedup symptom, and an importable-JSON request, with Spanish and Catalan phrasings). `should_not_trigger` lists adjacent prompts that belong to a named sibling (code clients → api-connector-builder, webhook receivers → webhooks, sheet scripting → spreadsheet-ops, single-vendor SDK calls → whatsapp-telegram, scraping → data-scraper). `capability` is one end-to-end scenario with a `must_include` rubric the produced flow has to satisfy.
There is no automated runner here. 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 n8n flow, then check every `must_include` item by hand and run `scripts/verify.sh <dir-with-the-json>` to confirm the emitted workflow JSON parses, has non-empty `nodes`, a `connections` object, and a trigger node. `verify.sh` is read-only and exits 0 on an empty target.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |