Skip to content

docs: document the npx skills path for agents outside the big three#71

Merged
devantler merged 2 commits into
mainfrom
claude/npx-skills-install-path
Jul 18, 2026
Merged

docs: document the npx skills path for agents outside the big three#71
devantler merged 2 commits into
mainfrom
claude/npx-skills-install-path

Conversation

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Daily AI Engineer

Why

The install instructions covered VS Code, Copilot CLI and Claude Code. Anyone using one of the many other agents had no documented way to use any of this — even though the npx skills path already works against this marketplace today and reaches 70+ agents.

What

Documents that path, with a clear warning that it is a partial one: it delivers the bundled skills but not the MCP server or custom agents, so people who can use a first-class tool still should. Being upfront about the limit keeps expectations right rather than sending someone to a worse experience.

Part of devantler-tech/monorepo#2229

The README only covered VS Code, Copilot CLI and Claude Code, so anyone on one
of the other 70+ agents `npx skills` supports had no documented way in — even
though the path already works today.

Verified live: `npx skills add devantler-tech/agent-plugins` reads this repo's
.claude-plugin/marketplace.json via the CLI's plugin-manifest discovery and
resolves all 27 bundled skills, matching the on-disk count exactly.

Documented as an explicitly PARTIAL path, because it is: an install pulls the
skills but NOT the 1 bundled MCP server config or the 4 custom agents — those
are plugin-level resources only a real plugin install delivers. Confirmed by
installing a skill and checking what landed (skill files only). Overstating
this as a full install path would send people to a worse experience than the
three first-class tools.
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Engineer

@coderabbitai review

@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Engineer

Readiness record — tried and evaluated as a user

Ran the documented commands against the real marketplace:

  • npx skills add devantler-tech/agent-plugins --list"Found 27 skills", resolved through the CLI's .claude-plugin/marketplace.json plugin-manifest discovery. That matches the on-disk count exactly (find plugins -mindepth 4 -maxdepth 4 -name SKILL.md → 27), so nothing is silently missed.
  • npx skills add devantler-tech/agent-plugins --skill gitops-knowledge --agent cursor → installed to ./.agents/skills/gitops-knowledge/, with its references/, assets/ and evals/ intact.

Why the "partial path" warning is in the README rather than a cheerful install line. I checked what an install actually leaves behind: skill files only. The repo bundles 1 MCP server config and 4 custom agents, and neither came through — they are plugin-level resources that only a real plugin install delivers. Documenting this as a general-purpose install path would quietly hand people a degraded gitops-kubernetes (no Flux MCP server, no flux-troubleshooter agent) while implying parity with the three first-class tools, so the note states the limit and points back to them.

Validation:

  • ./scripts/validate-manifests.sh → pass (manifest parity, plugin.json, README table ↔ filesystem, skill provenance).
  • ./scripts/validate-manifests.test.sh → 43 passed, 0 failed.
  • shellcheck scripts/*.sh → clean.
  • All 40 CI checks green; mergeStateStatus: CLEAN.

The change is prose under ## Installation only — the plugin table the validator cross-checks against the filesystem is untouched.

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

@devantler I’ll review the changes, including the documented limitations of the npx skills path.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@devantler, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: edf6b969-046b-4a88-b31d-2164cfe212d4

📥 Commits

Reviewing files that changed from the base of the PR and between add0c6a and e22989a.

📒 Files selected for processing (1)
  • README.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Engineer

@codex review

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e22989a556

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md Outdated
The partial-path note sent people to "VS Code, Copilot CLI, or Claude Code" for
the complete plugins, but this README's own MCP servers and Custom agents
sections state that VS Code does NOT bundle a plugin's .mcp.json or agents/ —
both need adding by hand there.

So for gitops-kubernetes, vibe-coding and automated-ai-engineer, a VS Code user
following that sentence would have got exactly what the note warned them about:
skills without the Flux MCP server or the agents. Names only Claude Code and
Copilot CLI as the automatic paths and states the VS Code caveat explicitly.

Found by Codex review (P2) on #71.
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Engineer

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: a1d1eef9f5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@devantler
devantler marked this pull request as ready for review July 18, 2026 07:43
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Daily AI Engineer

Self-promoted — readiness conditions met at a1d1eef.

  • Programmatically tested: all 40 checks green; validate-manifests.sh pass; self-test 43/43; shellcheck clean.
  • Reviewed: green Codex review at a1d1eef9f5 — the current head, re-secured after the fix push. Its earlier P2 (VS Code wrongly listed as a complete-plugin path) is fixed and the thread resolved. 0 unresolved threads.
  • Tried and evaluated as a user: ran npx skills add devantler-tech/agent-plugins --list (27 skills, matching the on-disk count) and installed one to confirm what actually lands — skills only, no MCP server, no agents. That check is what produced the partial-path warning, and the review is what corrected which tools the warning should point at.

Pre-merge checks are not-posted because the green review came from the Codex lane — CodeRabbit's evaluator only runs when CodeRabbit reviews, and it rate-limited all three of this run's PRs at once. That is the lane-choice consequence, not a hygiene gap.

@devantler
devantler merged commit 6009413 into main Jul 18, 2026
39 of 40 checks passed
@devantler
devantler deleted the claude/npx-skills-install-path branch July 18, 2026 07:43
@github-project-automation github-project-automation Bot moved this from 🫴 Ready to ✅ Done in 🌊 Project Board Jul 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

1 participant