skills/super-curl/SKILL.md
Send configured HTTP requests (named endpoints, JWT, templates, SSE). Use for API testing, webhooks, or scripted calls without the Pi extension. Prefer this skill when the user wants curl-like requests with shared config.
npx skillsauth add graffioh/dotfiles super-curlInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
HTTP client with the same behavior as pi-super-curl’s send-request script, but loads config.json from this directory first (then falls back to .pi-super-curl/config.json in the tree or home).
config.example.json to config.json in this folder (or pass --config /path/to/config.json).baseUrl, auth, endpoints / templates, and optional envFile as needed.node (no extra npm deps).Resolve the script path (this repo, symlinked Cursor skill, or absolute path):
SCRIPT="/absolute/path/to/dotfiles/skills/super-curl/send-request.cjs"
node "$SCRIPT" GET @get
Common flags: --body '{...}', --header 'Name: value', --stream, --save, --repeat N, --config /path/to/config.json.
Symlink or copy this folder to a location Cursor loads user skills from (for example ~/.cursor/skills-cursor/super-curl on your machine, or a project’s .cursor/skills/super-curl).
{{uuid}}, {{uuidv7}}, {{timestamp}}, {{env.VAR}}, etc.ttft-ui helper on disk; otherwise streaming still works without TTFT.config.json local or use env vars / envFile.development
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
tools
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------