Skip to content

Plugins & Skill Packs

Two ways to extend gald3r beyond what ships by default: plugins (community, git-cloned) and skill packs (curated bundles of skills, first-party and community). Both are covered here.

Skill packs — curated bundles of ready-made skills

gald3r skill-pack list

3d-graphics
ai-media
ai-ml-dev
ai-video-tools
blockchain
cloud-providers
community
content-creation
context7
continual-learning
create-plugin
cursor-team-kit
firecrawl
huggingface
infrastructure
phantom-connect
startup-tools
superpowers
user-skills
vercel

(Real output from this repo — every one of these is a discoverable pack today, install/update status shown per-skill when a pack is already partially installed.)

gald3r skill-pack add <pack>                    # install every skill in the pack
gald3r skill-pack add <pack> --skill <name>      # install just one skill from it
gald3r skill-pack del <pack>                     # remove all (or --skill one) from active IDE folders
gald3r skill-pack save <name>                    # save a customization as an _evolved variant that survives future pack updates

skill-pack add's real argument shape (--help):

Usage:
  gald3r skill-pack add PACK [flags]

Flags:
      --data-dir string     Writable user data dir for local pack installs (default: $GALD3R_HOME or ~/.gald3r)
      --json                 Emit machine-readable JSON instead of a human summary
      --skill string         Install only this one skill from the pack (default: every skill in it)

--data-dir defaults to $GALD3R_HOME or ~/.gald3r — packs install into a writable per-user data directory, then get symlinked/copied into your active IDE folders, so an update to the pack doesn't clobber a skill you've customized (that's what skill-pack save's _evolved variant mechanism protects).

Plugins — community, git-cloned, SKILL.md-based

gald3r plugin list

No plugins installed.

(Real output — this checkout has none installed; a project with plugins lists each by name, source, and enabled/disabled-per-project state.)

gald3r plugin install <name-or-git-url>
gald3r plugin update <name>       # git pull --ff-only
gald3r plugin uninstall <name>
gald3r plugin enable <name>       # turn ON for the current project (globally installed, per-project association)
gald3r plugin disable <name>      # turn OFF for the current project

Plugins are git clones — install clones the repo, update fast-forward-pulls it, uninstall removes the clone. Install is global (once per machine); enable/disable is per-project, so you can have a plugin installed but only active in the projects that need it.

Skill packs vs. plugins — which one am I looking at?

Skill packs Plugins
Source Curated first-party + community registry Any git URL, or a registry name
Granularity Whole pack, or one named skill from it Whole plugin
Customization survives updates? Yes (_evolved save mechanism) Not a built-in mechanism — it's a plain git clone
Typical content Domain-specific skill collections (ai-ml-dev, blockchain, cloud-providers, ...) Anything a SKILL.md-based plugin author ships

Reference/prompt library, and MCP exposure

Two related surfaces worth knowing about:

gald3r prompt --help    # judgment/prompt-asset library: role briefs, rubrics, playbooks, voice
gald3r mcp --help       # expose gald3r's prompt/judgment library to any MCP client (Claude Desktop, Cursor, ...) over stdio

gald3r mcp is how an external MCP-compatible client reaches into gald3r's own prompt library — the reverse direction from plugins/skill packs extending gald3r. Direct prompt get / gald3r_prompt_get still refuse shipped-core IP except the narrow agent-retrievable allowlist (pipeline playbooks named by shipped g-go* shims); a plugin's own prompts/ directory stays fully gettable so you can debug it.

Where next

  • marketplace.md — curated one-click installers with provenance, an in-Throne skill builder, and the malware-review pipeline + per-skill change log that gates every marketplace add/edit/update (builds on plugin install/update above)
  • crash.md — how a skill actually gets loaded and activated once installed
  • verbs.md — the full verb catalog