Skip to content

Surface the developer skill on docs.autonomi.com and as a Claude Code plugin#14

Merged
JimCollinson merged 5 commits into
mainfrom
claude/review-developer-skill-pr-4A71L
Apr 30, 2026
Merged

Surface the developer skill on docs.autonomi.com and as a Claude Code plugin#14
JimCollinson merged 5 commits into
mainfrom
claude/review-developer-skill-pr-4A71L

Conversation

@JimCollinson

Copy link
Copy Markdown
Collaborator

Summary

Make the autonomi-developer skill installable through the canonical Claude Code plugin-marketplace flow, and surface it from the developer-docs landing page so developers using AI coding tools have a clear path to give their tool Autonomi-specific expertise.

What this adds

  • .claude-plugin/plugin.json — declares this repo as the autonomi-developer plugin (manifest follows the schema at https://code.claude.com/docs/en/plugins).
  • .claude-plugin/marketplace.json — declares this repo as the autonomi marketplace, with autonomi-developer as its first plugin (source: "./").
  • docs/developer-skill.md — new top-level docs page that explains what the skill gives your AI, how to install it (Claude Code marketplace, other AI tools, manual install), and how it stays current.
  • docs/SUMMARY.md — wires the new page in as a companion to the landing page (sibling to What is Autonomi?).
  • docs/index.md — adds a short "Build with an AI coding tool" callout pointing at the new page.

After this lands, the install flow is:

/plugin marketplace add WithAutonomi/autonomi-developer-docs
/plugin install autonomi-developer@autonomi

Dependency

This PR depends on #13 (the skill PR). The plugin manifests reference skills/autonomi-developer/SKILL.md, which lands on main only when #13 merges. Recommended order: merge #13 first, then this.

Validation

  • Both manifest JSON files parse
  • Marketplace + plugin name resolve to /plugin install autonomi-developer@autonomi
  • No prohibited words/phrases per CLAUDE.md style guide
  • Plugin-source path uses ./ (works with the GitHub marketplace install flow per Anthropic's plugin docs)
  • Page placement, terminology, and verification metadata match CLAUDE.md conventions
  • Manual click-through of /developers/developer-skill URL after merge (depends on GitBook sync)
  • End-to-end test of /plugin marketplace add + /plugin install after both PRs merge

Test plan

  • After Add Autonomi developer skill #13 and this PR are merged, run /plugin marketplace add WithAutonomi/autonomi-developer-docs then /plugin install autonomi-developer@autonomi in a fresh Claude Code session and confirm the skill loads.
  • Confirm https://docs.autonomi.com/developers/developer-skill resolves on GitBook.
  • Confirm the landing-page callout renders and links correctly.

https://claude.ai/code/session_011ejE8AuiwqiyytfBWds9ZU


Generated by Claude Code

claude added 5 commits April 30, 2026 13:36
Make the autonomi-developer skill installable through the canonical
plugin-marketplace flow and findable from the docs landing page, so
developers using AI coding tools have a clear path to give their
tool Autonomi-specific expertise.

- Add `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`
  so this repo doubles as the `autonomi` marketplace and as the
  `autonomi-developer` plugin.
- Add `docs/developer-skill.md` describing the skill, what it gives the
  AI, and how to install it.
- Wire the new page into `docs/SUMMARY.md` as a top-level companion to
  the landing page, and add a short callout from `docs/index.md`.

https://claude.ai/code/session_011ejE8AuiwqiyytfBWds9ZU
- Drop the explicit `version` from `plugin.json` so commit SHAs drive
  update detection while the underlying skill is still in `0.1.1-draft`,
  per Anthropic's plugin-marketplace version-resolution rules.
- Add `/reload-plugins` to the install snippet so the skill activates
  in the same session it was installed in, matching the canonical
  `/plugin install` flow documented at code.claude.com.
- Stop labelling the slash-command block as `bash` (it runs inside
  Claude Code, not a shell) and tag the canonical-URL block with
  `text` so every code fence still carries a language tag.

https://claude.ai/code/session_011ejE8AuiwqiyytfBWds9ZU
The previous layout produced an awkward `/autonomi-developer:autonomi-developer`
slash form (plugin name == skill folder name). Reshape the identifiers so the
brand sits in the marketplace name and the plugin/skill names stay short:

- Marketplace: `withautonomi` (mirrors the GitHub org)
- Plugin: `developer`
- Skill folder: `skills/start/`

Resulting flow:

  /plugin marketplace add WithAutonomi/autonomi-developer-docs
  /plugin install developer@withautonomi
  /reload-plugins

  Direct invocation: /developer:start

Files changed:

- `.claude-plugin/plugin.json` — `name: developer`
- `.claude-plugin/marketplace.json` — `name: withautonomi`, plugin name `developer`
- `skills/start/` — git-mv from `skills/autonomi-developer/`; updated `name`,
  `skill`, `version_manifest_url`, `canonical_skill_url`, and the operating-rule
  curl to the new path
- `skills/start/CHANGELOG.md` — Unreleased entry noting the rename
- `skills/start/MAINTAINING.md` — header and path reference updated
- `component-registry.yml` — all 25 `feeds_skills` paths point at the new folder
- `docs/developer-skill.md` — install commands use the new identifiers, manual
  install URL points at the new path, added a single line on direct invocation

The page title and prose keep "Autonomi Developer Skill" as the branded display
name. Only the kebab-case identifiers shorten.

https://claude.ai/code/session_011ejE8AuiwqiyytfBWds9ZU
The plugin manifest has no pinned version (commit-SHA-driven), but the
underlying skill is still `0.1.1-draft`. Flag the docs page as a preview
release so the asymmetry is honest to readers and identifiers can still
shift before the first non-draft cut without surprising anyone.

https://claude.ai/code/session_011ejE8AuiwqiyytfBWds9ZU
@JimCollinson
JimCollinson merged commit 873189d into main Apr 30, 2026
2 checks passed
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.

2 participants