Frame the repo as the Poimandres plugin, not the docs plugin

[abernier]

Base of a two-PR stack. #3 (the docs-lookup subagent) now targets this branch.

Why

The manifests and the README both read as though documentation lookup were what this plugin is:

Answers questions about react-three-fiber, drei and zustand from the official docs.pmnd.rs pages instead of from memory.

That's what it does first. Everything meant to follow — more skills, subagents, hooks — would have arrived as an exception to the plugin's own description, and the first one would have forced this rewrite anyway, mixed into a PR about something else.

So the framing states the shape without promising components that don't exist yet: one install carrying Poimandres tooling, of which docs lookup is today's entire content. Marketplace descriptions gain a "Currently:", pmndrs and poimandres join the keywords, and the README splits what grows (components) from what doesn't (plumbing).

name is deliberately untouched — it's baked into every scoped MCP tool name (mcp__plugin_pmndrs_docs__…), so it's the one field here that isn't free to change.

Also fixes

SKILL.md told Claude to pass docs as the server argument to ReadMcpResourceTool. Bundled in a plugin, the server registers as plugin:pmndrs:docs — the bare key from .mcp.json isn't a name anything answers to, and the failure is a silent empty read rather than an error. Unrelated to the stack's second half, so it belongs here.

Tests

npm test — Node's built-in runner, no install step, wired to CI in .github/workflows/test.yml. Everything here targets wiring that fails silently at runtime rather than loudly at load:

Invariant	Why it matters
the plugin name agrees across both manifests	it's baked into every scoped MCP tool name, so a one-sided rename breaks tools silently
a component reading MCP resources names a server to read from	ReadMcpResourceTool takes a configured name; the bare key isn't one
every bundled MCP server is reached by some component	catches dead .mcp.json config
skill names match their directories	otherwise the skill is invoked under the install directory name, which for a marketplace install is a version string that changes every update
the coverage table carries a real checked-on date	the empty-library list is a claim about the outside world, and it goes stale
the README lists every component shipped	the rule that matters as components accumulate
claude plugin validate . passes	skipped when the CLI isn't installed

That last one is the point of doing this now: a capability nobody can find is a capability nobody uses, so the README table is enforced rather than maintained by good intentions. It caught its own omission twice while this stack was being written.

Each invariant was mutation-checked — breaking it fails the test that claims to guard it, and no other. 13/13 green with no agents/ directory present, which is the case this PR has to work in.

Worth a look during review

• category stays documentation. Retitling it generalist while there is exactly one component seemed worse for discoverability than leaving it accurate; it should move when a second component lands.
• Wording of the "not a promise" paragraph in the README — it's the part making a claim about the future, so it's the part worth disagreeing with.

---

Generated by Claude Code