Skip to content

fix(pstack): map cursor-team-kit skills in the Claude Code adapter - #1153

Open
frankcalise wants to merge 1 commit into
cursor:mainfrom
frankcalise:fix/pstack-claude-code-team-kit-skills
Open

frankcalise wants to merge 1 commit into
cursor:mainfrom
frankcalise:fix/pstack-claude-code-team-kit-skills

Conversation

@frankcalise

Copy link
Copy Markdown

Why

pstack calls /deslop, control-ui, and control-cli from cursor-team-kit, and Cursor's built-in create-skill. The Claude Code adapter maps none of them, and the Claude Code marketplace does not list cursor-team-kit, so Claude Code agents skip those steps. Two playbooks also name /no-comments in the same clause as /deslop from cursor-team-kit. Agents then skipped /no-comments as "not installed", although it ships with pstack.

What changed

  • The Claude Code adapter gains a "Skills from other plugins" table for the four skills, and says /no-comments ships with pstack.
  • opening-a-pr.md and multi-phase-plan.md split the instruction into two sentences that say where each skill comes from.
  • The generated harness tree carries the same three edits.

Scope

  • Docs only. Cursor sees two reworded sentences and no behavior change.
  • It does not list cursor-team-kit in .claude-plugin/marketplace.json.

Tradeoffs

Listing cursor-team-kit in the Claude Code marketplace would let /deslop resolve with no copy step. Nobody has checked its 18 skills, 2 agents, and .mdc rules under Claude Code, so that call belongs to the plugin's owners.

Blast Radius

Claude Code users of pstack read one new adapter section. The table only adds mappings, so a session that already skipped these steps now runs them or skips them with the adapter's existing line.

Verification

  • cmp shows each edited harness file is identical to its source. The generator copies these files unchanged, because they are not SKILL.md files and the new text has no links, so generate-pstack-harness-trees.mjs --check in CI should pass. I did not run the generator locally.
  • With deslop copied into ~/.claude/skills/deslop/, a fresh headless Claude Code session lists deslop, and /no-comments resolves through pstack:comment-sicko.

pstack calls /deslop, control-ui, and control-cli from cursor-team-kit,
and Cursor's built-in create-skill. The Claude Code adapter mapped none
of them, so Claude Code agents skipped those steps. Two playbooks also
named /no-comments in the same clause as /deslop, and agents skipped it
as not installed, although it ships with pstack.

The adapter gains a table for the four skills and says /no-comments
ships with pstack. opening-a-pr.md and multi-phase-plan.md split the
instruction so each skill names where it comes from.
@frankcalise
frankcalise marked this pull request as ready for review November 2, 2026 01:30
flexdinesh added a commit to flexdinesh/diffx that referenced this pull request Nov 2, 2026
cursor/plugins#1153 failed in staging: the cursor org's IP allow list refuses
the app's installation tokens on REST pull request reads (HTTP 403), and
previews tried only the repository's and the public installation.

- github: Credential (installation, user access, anonymous); ErrRestricted
  for non-rate-limit 403s; ErrCredentialUnavailable for unmintable tokens.
- githubsync: ordered public read sources (repository, public, viewer,
  anonymous) composed as app policy. Refused credentials fall back; 404 ends
  the chain (except a stale repository installation) and never reaches the
  viewer. Lease fetch credential follows the serving source; the fetcher
  never holds a user token.
- Exhaustion answers failure `restricted` with remedy sign_in or
  connect_github; rate limits stay 429.
- remoteserver: only browser sessions lend their GitHub connection.
- API: `restricted` code and `remedy` field.
- web: "GitHub restricts this repository" state with Sign in / Open Settings
  recovery.
- docs: system, architecture, DESIGN, user docs.
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.

1 participant