feat: add 'npx skills' support for other agents - #131
Conversation
The README and the public plugin page both scoped this project to Claude Code, Cursor, and Codex, the three agents with a plugin marketplace. The `skills` CLI already installs the eight skills into any of 77 agents straight from `main`, with no repo changes required, so developers on Gemini CLI, OpenCode, Zed, or Warp had a working path and no way to find it. Adds an "Other agents" section to the README and the matching section to `docs/slack-skills-plugin.md`, covering the command, agent identifiers, `-a '*'`, `--list`, `-g`, where skills land per agent, and how `skills-lock.json` lets `npx skills update` re-sync after a release. Both state that this path carries the skills only: no commands, no MCP server, so `slack-search` cannot query a workspace.
🦋 Changeset detectedLatest commit: 4a5c282 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Replace the placeholder `<agent>` guidance with identifiers a developer can copy: crush, devin, gemini-cli, hermes-agent, openclaw, opencode, and pi. The docs page carries them as a table with the project directory each agent reads, since that path is per-agent and not guessable. Also corrects the README's claim that skills land in `.agents/skills/` for most agents. That holds for Gemini CLI and OpenCode, but Crush uses `.crush/skills/`, Devin `.devin/skills/`, and Hermes `.hermes/skills/`. Paths and identifiers verified against the Supported Agents table in vercel-labs/skills, and by installing into each agent.
Refer to the tool as `npx skills` throughout, and stop naming a specific number of supported agents: that count moves with every release of the tool and would date the page. Both surfaces now lead with runnable examples for Gemini CLI and OpenCode, name a few other popular agents, and link to the upstream supported-agents list for the rest. Drops the per-agent skills directories and the `skills-lock.json` paragraph. Those belong to the tool, not to this plugin, and documenting them here means our page goes stale when the tool changes them. The multi-agent and `--list` flags come out for the same reason; `-g` stays, since installing for your user rather than one project is a choice a developer makes about this plugin.
The examples alone left a developer on an agent we do not name with nothing to pattern-match against. Each code block now leads with the general form, `-a <agent>`, commented to say the value is the agent's own identifier, then the two concrete invocations underneath.
WilliamBergamin
left a comment
There was a problem hiding this comment.
Nice work 💯
Not sure if its worth pointing out here but it seem like npx skills strips the plugin namespace, and our skills refer to one another as slack:. In OpenCode, slack:slack-cli and slack:slack-docs are not registered; only slack-cli and slack-docs are. Maybe this will fix itself once we add opencode specific support 🤔
|
|
||
| Other popular agents include `crush`, `devin`, `hermes-agent`, `openclaw`, and `pi`. See [supported agents][npx-skills] for the full list of agents and their identifiers. Add `-g` to install for your user instead of the current project. | ||
|
|
||
| This path carries the skills only: no commands, and no MCP server. |
There was a problem hiding this comment.
Nice 🙏 praise for pointing this out
Co-authored-by: William Bergamin <wbergamin@salesforce.com>
|
Thanks for the review @WilliamBergamin! 🙇🏻 🤔 Good find that |
Summary
This pull request documents how to install the Slack skills into coding agents that have no plugin marketplace, so a developer on Gemini CLI, OpenCode, or anything else
npx skillssupports is no longer told this plugin is for Claude Code, Cursor, and Codex only.Docs only. This path already worked and was simply undocumented. The README gains an Other agents section and
docs/slack-skills-plugin.mdgains the matching one, both linking to supported agents rather than mirroring a list that changes every release. Both say what the path costs you: skills only, no commands, and no MCP server, soslack-searchcannot query a workspace.Notes
Requirements
make testand the tests pass.