agentleFS
buttjerbuttjer/n8n-decanter/.claude/skills/verify/SKILL.md

verify

Skill2 starsChanged 26 days agoMITView on GitHub

Drive the real CLI (node n8n-decanter.mts <verb>) as a subprocess against a throwaway mock n8n API — do not import lib/ modules directly. - Mock API: ~40-line node:http server on 127.0.0.1:<port> serving GET/PUT /api/v1/workflows/:id from a mutable in-memory workflow; log requests; add a control route (e.g. PUT /__remote) to simulate n8n-UI edits mid-session. See the reference driver below for a working fixture (connections must reference real node names or the compliance guard blocks pushes). - Sync dir: temp dir with…

  • Reads credentials

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 10 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Bootstrap: run node n8n-decanter.mts pull (cwd = sync dir) to create the layout.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 167 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verify n8n-decanter changes at the CLI surface

Drive the real CLI (node n8n-decanter.mts <verb>) as a subprocess against a throwaway mock n8n API — do not import lib/ modules directly.

Recipe

  • Mock API: ~40-line node:http server on 127.0.0.1:<port> serving GET/PUT /api/v1/workflows/:id from a mutable in-memory workflow; log requests; add a control route (e.g. PUT /__remote) to simulate n8n-UI edits mid-session. See the reference driver below for a working fixture (connections must reference real node names or the compliance guard blocks pushes).
  • Sync dir: temp dir with .env (N8N_HOST=http://127.0.0.1:<port>, N8N_API_KEY=test) + decanter.config.json ({"root":"./workflows","workflows":["wf1"]}), then git init + local user.name/email — pull/push/watch auto-commit and watch refuses its startup pull without git.
  • Bootstrap: run node n8n-decanter.mts pull (cwd = sync dir) to create the layout; then drive the verb under test.
  • watch: spawn it, poll its captured stdout for marker lines ("watching workflow", "pushed", conflict text); 200 ms debounce — allow ~500 ms after a file write before asserting. Piped stdin = non-TTY paths. For TTY-only paths (conflict prompt) wrap in expect — macOS script -q /dev/null does NOT work with piped stdin ("tcgetattr … not supported on socket"). Coordinate expect sends with driver-side file edits via marker files.

Gotchas

  • fs.watch dies under the Bash sandbox (EMFILE, watch from FSEvents) and takes the watch process down — run watch-related drives with the sandbox disabled; it is an environment artifact, not a code failure.
  • The e2e suite's mock (test/e2e.mts) is in-process and not importable; building a fresh mock is faster than extracting it.
  • Piped CLI output is ANSI-free since Plan 11 (styling is TTY-gated) — in fact assert the absence of \x1b in captured output. Error lines start with ✗ , success lines with ✓ .

A known-good full driver (watch structural sync, conflict prompt via expect) from 2026-07-18 exists in the session scratchpad as drive.mjs; recreate from this recipe if gone.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.