learn-plugin-docs

Learn Plugin Docs

Turn a plugin name or URL into a local, condensed markdown reference, then answer from it.

When to use

Any time you are not confidently current about a specific plugin's config keys, permission nodes, commands, or placeholders. Fetch first, answer second. Never invent config keys.

Procedure

Given an argument like LuckPerms, MythicMobs, https://modrinth.com/plugin/dynmap, or a Hangar slug:

1. Check the bundled library first, then the cache. ~55 popular plugins are pre-fetched into skills/learn-plugin-docs/library/ (committed, zero-network) and resolved by name/alias via library/registry.json. learn-docs.mjs does this automatically — resolution order is library → _cache/ (7-day) → registry canonical URL → Modrinth/Hangar search. Pass --refresh to bypass the library/cache and re-fetch. If skills/_cache/<slug>/REFERENCE.md already exists and is recent, it is reused.

2. Resolve the target. If $ARGUMENTS is a URL, infer the host. If it's a name, the script searches Modrinth, then Hangar.

3. Run the fetcher:

   node "${CLAUDE_PLUGIN_ROOT}/skills/learn-plugin-docs/scripts/learn-docs.mjs" "$ARGUMENTS"
   

   It picks the cheapest adapter for the host (see references/source-routing.md), fetches the authoritative markdown, condenses it, and writes:

   • skills/_cache/<slug>/REFERENCE.md — condensed (Overview, Install, Config keys, Permissions, Commands, Placeholders, Dependencies, Folia, Footguns), with source_url + fetched_at.
   • skills/_cache/<slug>/RAW.md — the full fetched markdown.

4. Read REFERENCE.md and answer the user's actual question from it. Summarise the key config keys, permissions, and commands, and cite the cache path + source URL.

5. If the fetch fails (host unknown, network blocked on enterprise installs), tell the user and offer the manual fallback: ask them to paste the relevant docs, or to upload the plugin .jar so you can read plugin.yml (commands/permissions) and bundled config.yml.