Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Manage complete plugin lifecycle - install, uninstall, reset, destroy.
Install Plugin Lifecycle
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-lifecycle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plugin-lifecycle .claude/skills/plugin-lifecycle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plugin-lifecycle" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycle into .claude/skills/plugin-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-lifecycle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/plugin-lifecycle .agents/skills/plugin-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plugin-lifecycle" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycle into .agents/skills/plugin-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-lifecycle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/plugin-lifecycle .cursor/skills/plugin-lifecycle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plugin-lifecycle" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycle into .cursor/skills/plugin-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-lifecycle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/glittercowboy/plugin-freedom-system.git --path .claude/skills/plugin-lifecycle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/plugin-lifecycle .gemini/skills/plugin-lifecycle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plugin-lifecycle" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycle into .gemini/skills/plugin-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-lifecycle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install glittercowboy/plugin-freedom-system plugin-lifecycleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/plugin-lifecycle .github/skills/plugin-lifecycle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plugin-lifecycle" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycle into .github/skills/plugin-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-lifecycle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/plugin-lifecycle .opencode/skills/plugin-lifecycle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plugin-lifecycle" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-lifecycle into .opencode/skills/plugin-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-lifecycle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plugin-lifecycle- GitHub stars
- 216
- Token cost
- ~2.2k tokens
- SKILL.md length
- 850 words
- Files
- 13 (incl. references, assets)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Manage complete plugin lifecycle - install, uninstall, reset, destroy.
- Works in 8 steps: Build Verification (BLOCKING) - Check… → Product Name Extraction - Extract… → Old Version Removal - Remove existing… → …
- User runs /install-plugin
- SKILL.md covers Overview, Mode Dispatcher, Installation Workflow (Mode 1… and Cache Management, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plugin Lifecycle is an agent skill from glittercowboy/plugin-freedom-system. Manage complete plugin lifecycle - install, uninstall, reset, destroy. Use when user runs /install-plugin, /uninstall, /reset-to-ideation, /destroy, /clean commands, or says 'install [Name]', 'remove [Name]', 'uninstall [Name]', 'delete [Name]'.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including reference files and assets (for example `assets/notes-template.md`, `references/README.md` and `references/cache-management.md`).
It sits in Agent Workflows, covering Brainstorming. The repository describes itself as: AI-assisted JUCE plugin development system for MacOS by TÂCHES.
When your agent uses it
- User runs /install-plugin
- /reset-to-ideation
- /clean commands
- Says install [Name]
Example prompts
- “install [Name]”
- “remove [Name]”
- “uninstall [Name]”
- “/plugin-lifecycle”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Edit, Write
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Build Verification (BLOCKING) - Check Release binaries exist, offer to build if missing
- Product Name Extraction - Extract PRODUCT_NAME from CMakeLists.txt
- Old Version Removal - Remove existing installations to prevent conflicts
- Copy to System Folders (BLOCKING) - Install VST3 and AU to macOS plugin directories
- Permissions Verification (BLOCKING) - Set 755 permissions for DAW access
- Cache Clearing - Clear Ableton Live and Logic Pro caches
- Verification (BLOCKING) - Confirm installation with file checks and size validation
- PLUGINS.md Update (BLOCKING) - Record installation status and locations
What it can do on your machine
Read from SKILL.md and the folder at commit e965cdd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadEditWrite
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plugin Lifecycle loads about 2.2k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 850 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Edit, Write
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 850 words (~2,235 tokens).
“Purpose: Manage the complete lifecycle of plugins from installation to removal with proper state tracking and safety features.”
- name
- plugin-lifecycle
- allowed-tools
- Bash, Read, Edit, Write
- preconditions
- Varies by mode (see mode-specific preconditions)
Files
SKILL.md and 12 other files (references, assets) in .claude/skills/plugin-lifecycle of glittercowboy/plugin-freedom-system.
- SKILL.md
- assets/notes-template.md
- assets/reset-confirmation-example.txt
- assets/reset-success-example.txt
- references/README.md
- references/cache-management.md
- references/decision-menu-protocol.md
- references/error-handling.md
- references/installation-process.md
- references/invocation-protocol.md
- references/mode-3-reset.md
- references/mode-4-destroy.md
- references/uninstallation-process.md
Open the folder on GitHubat commit e965cdd
Compare with similar skills
Plugin Lifecycle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plugin Lifecycle this skillglittercowboy/plugin-freedom-system | 216 | — | ~2.2k | Automated safety check: Notes | None | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| LLM Councilgcpdev/llm-council-skill | 461 | 1 repos | ~1k | Automated safety check: Notes | MIT | |
| Typesafe AIOpenAgentsInc/openagents | 455 | 9 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Yao Meta Skillyaojingang/yao-meta-skill | 2.7k | — | ~768 | Automated safety check: Pass | MIT | |
| Trellis StartROYIANS/foliq-print-template-designer | 135 | 6 repos | ~646 | Automated safety check: Pass | MIT |
Similar skills
LLM Council
gcpdev/llm-council-skill
Multi-LLM collaborative brainstorming and planning. An agent skill from gcpdev/llm-council-skill.
Typesafe AI
OpenAgentsInc/openagents
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.
Yao Meta Skill
yaojingang/yao-meta-skill
Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.
Trellis Start
ROYIANS/foliq-print-template-designer
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/.
Brainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
More from glittercowboy/plugin-freedom-system
All 15 skills in this repoAesthetic Dreaming
glittercowboy/plugin-freedom-system
Create aesthetic templates without first creating a plugin - capture visual design concepts through adaptive questioning.
Deep Research
glittercowboy/plugin-freedom-system
Multi-agent parallel investigation for complex JUCE problems.
Plugin Ideation
glittercowboy/plugin-freedom-system
Adaptive brainstorming for plugin concepts and improvements when exploring ideas, not implementing.
Plugin Improve
glittercowboy/plugin-freedom-system
Fix bugs, add features to completed plugins. An agent skill from glittercowboy/plugin-freedom-system.
Plugin Packaging
glittercowboy/plugin-freedom-system
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system.
Plugin Planning
glittercowboy/plugin-freedom-system
Orchestrates Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through subagent delegation.
Related
Categories
Questions about Plugin Lifecycle
What does Plugin Lifecycle do?
Manage complete plugin lifecycle - install, uninstall, reset, destroy. Plugin Lifecycle is an agent skill from glittercowboy/plugin-freedom-system. Manage complete plugin lifecycle - install, uninstall, reset, destroy.
When should I use Plugin Lifecycle?
Plugin Lifecycle fits situations like: user runs /install-plugin; /reset-to-ideation; /clean commands; says install [Name].
How do I install Plugin Lifecycle in Claude Code?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a claude-code`. Or copy the skill folder (.claude/skills/plugin-lifecycle in glittercowboy/plugin-freedom-system) into .claude/skills/plugin-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Lifecycle in Codex?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a codex`. Or copy the skill folder (.claude/skills/plugin-lifecycle in glittercowboy/plugin-freedom-system) into .agents/skills/plugin-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Plugin Lifecycle in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-lifecycle, .gemini/skills/plugin-lifecycle, .github/skills/plugin-lifecycle and .opencode/skills/plugin-lifecycle in your project.
What does Plugin Lifecycle need to run?
SKILL.md names no scripts, command-line tools or credentials: Plugin Lifecycle is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Edit, Write.
Does Plugin Lifecycle access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Plugin Lifecycle safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Plugin Lifecycle use?
No licence was found for Plugin Lifecycle or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Plugin Lifecycle use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Plugin Lifecycle?
Skills that share tags, products or a category with Plugin Lifecycle: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), LLM Council (gcpdev/llm-council-skill, 461 stars), Typesafe AI (OpenAgentsInc/openagents, 455 stars) and Yao Meta Skill (yaojingang/yao-meta-skill, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plugin Lifecycle?
glittercowboy (a GitHub user) maintains it in glittercowboy/plugin-freedom-system, which has 216 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on November 19, 2025.
Source: glittercowboy/plugin-freedom-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.