.cursor/skills/github/SKILL.md
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.
npx skillsauth add avirajkhare00/agent-commerce githubInstall 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.
Use the GitHub CLI (gh) for GitHub-related work whenever the environment has shell access. Prefer gh subcommands and gh api over hand-built curl to GitHub’s REST API, unless gh cannot express the call.
Run commands from the relevant git repository root when the task is about the current project so gh resolves the correct remote and default repository.
gh installed: If a command fails with “command not found”, say that gh is required and point to https://cli.github.com/gh auth status. If not logged in, run gh auth login (or instruct the user to do so in their environment).| Goal | Prefer |
|------|--------|
| Current branch’s PR | gh pr view, gh pr status |
| List / search PRs | gh pr list, gh pr list --search '...' |
| Create PR | gh pr create (after push) |
| PR checks / mergeability | gh pr checks, gh pr view --json ... |
| Issues | gh issue list, gh issue view, gh issue create |
| Actions / workflow runs | gh run list, gh run view, gh workflow run |
| Releases / tags | gh release list, gh release create |
| Repo metadata | gh repo view, gh api repos/{owner}/{repo} |
| API not wrapped by a subcommand | gh api <endpoint> [--method ...] [--input -] |
Use gh <command> --help or gh help <topic> when flags are unclear instead of guessing URLs.
gh pr view 123 --json title,state,url,commits,files etc.--limit, query params via gh api).gh + git; do not assume a separate GitHub MCP unless the user has one configured.gh invocation.Summarize what was queried or changed, with links (html_url / url from JSON when helpful) and next steps if something is blocked on auth or missing scope.
tools
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.
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? | | ------------------------------------------------------ | --------------------------