Skip to content
Back to search

ade-skills

MarketplaceWorks with Claude CodeGitHub

Predefined skills and MCP servers for ADE developers. Add more by pull request.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/better-ade--ade-skills/badge.svg)](/listings/better-ade--ade-skills)

HTML

<a href="/listings/better-ade--ade-skills"><img src="/api/listings/better-ade--ade-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

/plugin marketplace add better-ade/ade-skills
/plugin install git@ade-skills
/plugin install browser@ade-skills
/plugin install ade@ade-skills
/plugin install notes@ade-skills
/plugin install fde@ade-skills
/plugin install clickup@ade-skills
/plugin install jira@ade-skills
/plugin install linear@ade-skills

The connector plugins (`clickup`, `jira`, `linear`) hold no credential: each owner signs in themselves through `/mcp`. [docs/connectors.md](docs/connectors.md) gives each server's address, sign-in, sign-out, revocation and reach.

A project can offer them to teammates in its committed `.claude/settings.json` (`extraKnownMarketplaces`, `enabledPlugins`); each teammate still installs them on their own machine.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines
  1. {
  2. "name": "ade-skills",
  3. "owner": { "name": "better-ade" },
  4. "description": "Predefined skills and MCP servers for ADE developers. Add more by pull request.",
  5. "plugins": [
  6. { "name": "git", "source": "./plugins/git", "description": "Branch, commit and pull-request conventions: commit as the user, no AI attribution." },
  7. { "name": "browser", "source": "./plugins/browser", "description": "Browser automation (Claude in Chrome, Playwright MCP) with read-only defaults and ask-first rules." },
  8. { "name": "ade", "source": "./plugins/ade", "description": "Drive ADE from inside Claude Code through the ade CLI; starting agents and messaging stay behind the owner's prompt." },
  9. { "name": "notes", "source": "./plugins/notes", "description": "Meeting notes, summaries, action items, digests and captures, written into the named hub folder." },
  10. { "name": "fde", "source": "./plugins/fde", "description": "Forward deployed engineering documents drafted from the customer's constraints; prices, dates and terms left blank." },
  11. { "name": "clickup", "source": "./plugins/clickup", "description": "ClickUp through ClickUp's own hosted MCP server; reads need no extra question; every change through this server asks, or is refused when prompts are switched off." },
  12. { "name": "jira", "source": "./plugins/jira", "description": "Jira through Atlassian's own hosted MCP server (Rovo MCP, v2); reads need no extra question; every change through this server asks, or is refused when prompts are switched off." },
  13. { "name": "linear", "source": "./plugins/linear", "description": "Linear through Linear's own hosted MCP server; reads need no extra question; every change through this server asks, or is refused when prompts are switched off." }
  14. ]
  15. }
README.md · README · 54 lines
  1. # ade-skills
  2. Predefined skills and MCP servers for ADE developers, as a Claude Code plugin marketplace. Developers add more by pull
  3. request. Roles live in [ade-method](https://github.com/better-ade/ade-method) and
  4. [ade-agent-registry](https://github.com/better-ade/ade-agent-registry); this repo is what those roles can *do*.
  5. | Plugin | What it gives an agent |
  6. |---|---|
  7. | `git` | Branch, commit and PR conventions: commit as the user, no AI attribution, verify before pushing, ask before push or merge |
  8. | `browser` | Claude in Chrome for signed-in tools, Playwright MCP (headless, isolated) for public pages and tests; read-only by default |
  9. | `ade` | Slash commands for the `ade` CLI (status, work, dispatch, notify, specialists, plugins); risky ones ask the owner |
  10. | `notes` | Meeting notes, summaries, action items, digests and captures in the named hub folder, each point with its source |
  11. | `fde` | Forward deployed engineering documents (discovery, proposal, SOW, change request, design doc, workflow, status report, handover) from the customer's constraints; prices, dates and terms left blank |
  12. | `clickup` | ClickUp's own hosted MCP server; the owner signs in through `/mcp`; a hook asks before any tool not on its read list |
  13. | `jira` | Atlassian's own hosted MCP server (Rovo MCP, v2) for Jira; the owner signs in through `/mcp`; a hook asks before any tool not on its read list |
  14. | `linear` | Linear's own hosted MCP server; the owner signs in through `/mcp`; a hook asks before any tool not on its read list |
  15. ## Install
  16. ```
  17. /plugin marketplace add better-ade/ade-skills
  18. /plugin install git@ade-skills
  19. /plugin install browser@ade-skills
  20. /plugin install ade@ade-skills
  21. /plugin install notes@ade-skills
  22. /plugin install fde@ade-skills
  23. /plugin install clickup@ade-skills
  24. /plugin install jira@ade-skills
  25. /plugin install linear@ade-skills
  26. ```
  27. The connector plugins (`clickup`, `jira`, `linear`) hold no credential: each owner signs in themselves through
  28. `/mcp`. [docs/connectors.md](docs/connectors.md) gives each server's address, sign-in, sign-out, revocation and reach.
  29. A project can offer them to teammates in its committed `.claude/settings.json` (`extraKnownMarketplaces`,
  30. `enabledPlugins`); each teammate still installs them on their own machine.
  31. ## Add a plugin
  32. 1. Copy `plugins/_template/` to `plugins/<name>/`, fill in `plugin.json` (name, description, version) and the skill.
  33. 2. Every skill has a `## Ask first` section: each action that sends, publishes, buys, deletes or changes something
  34. outside the repo, and that the agent asks before it.
  35. 3. A plugin that writes documents follows [docs/conventions.md](docs/conventions.md) and has the `document` keyword.
  36. 4. MCP servers: pin the package version. No secrets in this repo: remote servers sign in with OAuth; a server that
  37. needs a key gets it from the hub's Keychain (`bin/secret`), never from a value written here.
  38. 5. Add the plugin to `.claude-plugin/marketplace.json` (no version there), bump `version` in `plugin.json` on every
  39. change, run `bash tests/run.sh`, open a pull request.
  40. ## Verification
  41. `bash tests/run.sh`: manifests and names, a version in one place, `## Ask first` in every skill, pinned MCP packages,
  42. `claude plugin validate` on every plugin the marketplace lists (fails if `claude` is missing), the document-plugin
  43. conventions in [docs/conventions.md](docs/conventions.md), the connector checks (`tests/connectors.sh`: vendor servers
  44. only, no secret, the ask-first hook run on sample tool names), and a gitleaks scan.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.