Skip to content

Add verify-cf skill for scripted Cloudflare CLI proofs - #18

Merged
jordanpartridge merged 1 commit into
mainfrom
cursor/verify-cf-skill-c71d
Oct 14, 2026
Merged

jordanpartridge merged 1 commit into
mainfrom
cursor/verify-cf-skill-c71d

Conversation

@jordanpartridge

Copy link
Copy Markdown
Contributor

Summary

Adds a project-local verify-cf skill so agents can drive the real ./cf binary the way a user/agent does: launch deps, doctor health, run commands (prefer --json), capture exit/stdout/stderr evidence, and clean up isolate trees without deleting proof.

What’s included

  • .cursor/skills/verify-cf/SKILL.md — launch / doctor / drive / evidence / cleanup
  • bin/verify-cf helper (executable)
  • Feature map: agent JSON (missing creds), setup (isolate), zones, DNS list, tunnel list
  • Artifacts dir gitignored except .gitignore

Proof run (this agent)

On this cloud VM (PHP 8.3 + Composer installed via apt as stand-in setup):

  1. verify-cf launch → ready
  2. verify-cf doctor → vendor=ok, cf_list=ok, live_creds=absent
  3. Drove agent-json via drive zones --json with creds unset → exit 1, exact failure envelope
  4. cleanup left evidence under .cursor/skills/verify-cf/artifacts/prove-*/

Unverified on a machine that already has PHP/Composer: the apt install steps this stand-in performed.

Live zones / DNS / tunnel journeys need CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID and remain mapped as precondition-gated.

Follow-up

Use /maintain-verification-skill as the app’s commands change.

Open in Web Open in Cursor 

Scripted launch/doctor/drive/cleanup helpers and a feature map so agents
can prove real ./cf --json behavior (starting with missing-creds) without
touching a developer's .env.

Co-authored-by: Jordan Partridge <jordan@partridge.rocks>

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ship it.

  • First verify- skill in the org; no conflicting patterns.
  • Doctor + drive + isolate flow is sound and matches the documented agent JSON contract.
  • Two small robustness gaps called out inline (symlink target, entrypoint name assumption) but neither blocks the stated use cases.
  • Evidence layout and cleanup contract are correct; live-creds preconditioning is explicit.

Ready to merge.

@jordanpartridge
jordanpartridge marked this pull request as ready for review October 14, 2026 05:08
@jordanpartridge
jordanpartridge merged commit 9b5e85e into main Oct 14, 2026
1 check passed

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking correctness issue in PHP version gate.

  • PHP >=8.3 check fails on 8.4+ due to sort order (line 48 in bin/verify-cf).
  • Minor: drive() assumes RUN_DIR exists from prior launch/doctor.
  • Everything else is self-contained, follows the stated contract, and isolates setup mutations correctly.
  • No other patterns in repo to contradict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants