.cursor/skills/paperclip/SKILL.md
Paperclip (paperclipai) setup and usage from the npm registry. Use when the user mentions Paperclip, paperclipai CLI, local Paperclip server, onboarding, or integrating with Paperclip APIs. Do not clone the Paperclip GitHub repo to obtain or run the product.
npx skillsauth add avirajkhare00/agent-commerce paperclipInstall 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.
Do not git clone the Paperclip repository (for example github.com/paperclipai/paperclip) as the default way to install, run, or update Paperclip for local development or integration work.
Treat the npm registry as the source of truth for the CLI and published packages users actually run.
Prefer one of these patterns (match the user’s package manager):
pnpm dlx paperclipai, npx paperclipai@latest, or npm exec paperclipainpm install paperclipai, pnpm add paperclipai, etc.npm install -g paperclipaiUse paperclipai as the package name on npm (see https://www.npmjs.com/package/paperclipai). Pin a version when reproducibility matters (npx paperclipai@<version>).
Only if the user explicitly asks to work on upstream Paperclip source, fork the repo, or patch core Paperclip code. Even then, prefer npm-linked or workspace workflows only if they request that level of contribution—not as a substitute for “run Paperclip locally.”
tools
GitHub workflows using the GitHub CLI (gh). Use when the user asks for PRs, issues, releases, Actions, repo settings, forks, gists, or any GitHub.com task that can be done from the terminal; prefer gh over ad-hoc curl or guessing REST paths when a local shell is available.
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? | | ------------------------------------------------------ | --------------------------
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? | | ------------------------------------------------------ | --------------------------