Packaging Static Installer
netdata/netdata
Build, test, review or troubleshoot Netdata static makeself installers and packaging/makeself changes.
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system.
No licenceAuto-check passed
Install Plugin Packaging
$ npx skills add glittercowboy/plugin-freedom-system --skill plugin-packaging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-packaging --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-packaging .claude/skills/plugin-packaging && 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-packaging" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-packaging into .claude/skills/plugin-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-packaging", 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-packagingType 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-packaging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-packaging --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-packaging .agents/skills/plugin-packaging && 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-packaging" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-packaging into .agents/skills/plugin-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-packaging", 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-packaging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-packaging --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-packaging .cursor/skills/plugin-packaging && 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-packaging" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-packaging into .cursor/skills/plugin-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-packaging", 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-packaging--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-packaging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glittercowboy/plugin-freedom-system plugin-packaging --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-packaging .gemini/skills/plugin-packaging && 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-packaging" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-packaging into .gemini/skills/plugin-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-packaging", 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-packagingInstalls 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-packaging -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-packaging .github/skills/plugin-packaging && 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-packaging" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-packaging into .github/skills/plugin-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-packaging", 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-packaging -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-packaging --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-packaging .opencode/skills/plugin-packaging && 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-packaging" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/plugin-packaging into .opencode/skills/plugin-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-packaging", 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-packaging- GitHub stars
- 216
- Token cost
- ~1.9k tokens
- SKILL.md length
- 642 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system.
- Works in 6 steps: Verify Prerequisites → Extract Plugin Metadata → Create Branding Files → …
- User requests to package a plugin
- SKILL.md covers Overview, Workflow, Integration Points and Decision Menu, plus 3 more sections
- Calls git
What it does
Plugin Packaging is an agent skill from glittercowboy/plugin-freedom-system. Create branded PKG installers for plugin distribution. Use when user requests to package a plugin, create installer, share plugin with others, or mentions distributing/sending plugin to someone. Invoked by /package command or natural language like 'create installer for TapeAge' or 'package GainKnob'.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `references/pkg-creation.md`).
The repository describes itself as: AI-assisted JUCE plugin development system for MacOS by TÂCHES.
When your agent uses it
- User requests to package a plugin
- Create installer
- Share plugin with others
- Mentions distributing/sending plugin to someone
Example prompts
- “create installer for TapeAge”
- “package GainKnob”
- “/plugin-packaging”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Verify Prerequisites
- Extract Plugin Metadata
- Create Branding Files
- Build Base Package
- Build Branded Installer
- Output Distribution Package
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 nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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 Packaging loads about 1.9k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 642 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 passed
The automated check found no risky patterns in SKILL.md.
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 642 words (~1,908 tokens).
“Purpose: Create professional PKG installers for sharing plugins with others.”
- name
- plugin-packaging
Files
SKILL.md and 4 other files (references, assets) in .claude/skills/plugin-packaging of glittercowboy/plugin-freedom-system.
- SKILL.md
- assets/conclusion-template.txt
- assets/readme-template.txt
- assets/welcome-template.txt
- references/pkg-creation.md
Open the folder on GitHubat commit e965cdd
Compare with similar skills
Plugin Packaging 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 Packaging this skillglittercowboy/plugin-freedom-system | 216 | — | ~1.9k | Automated safety check: Pass | None | |
| Packaging Static Installernetdata/netdata | 81k | — | ~4.4k | Automated safety check: Notes | GPL-3.0 | |
| Brand Guidelinesalirezarezvani/claude-skills | 28k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Anthropic Brand Stylinganthropics/skills | 180k | 29 repos | ~559 | Automated safety check: Pass | Apache-2.0 | |
| Brand Extractnexu-io/open-design | 100k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Brand Guidelinesnexu-io/open-design | 100k | — | ~346 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Brand Guidelines
alirezarezvani/claude-skills
When the user wants to apply, document, or enforce brand guidelines for any product or company.
- Official
Anthropic Brand Styling
anthropics/skills
Applies Anthropic's brand colors and fonts to artifacts such as PowerPoint slides, using fixed hex values for text and accents, Poppins headings and Lora body text.
Brand Extract
nexu-io/open-design
Extract a complete Brand Kit from a live website by driving the in-app browser.
Brand Guidelines
nexu-io/open-design
Apply Anthropic's official brand colors and typography to artifacts for consistent visual identity and professional design standards.
Brand Discovery
affaan-m/ECC
Run a structured, resumable multi-session brand identity interview across 8 modules (purpose, positioning, audience, personality, voice, narrative, founder tension) using laddering, 5 Whys, and…
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 Lifecycle
glittercowboy/plugin-freedom-system
Manage complete plugin lifecycle - install, uninstall, reset, destroy.
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.
Questions about Plugin Packaging
What does Plugin Packaging do?
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system. Plugin Packaging is an agent skill from glittercowboy/plugin-freedom-system. Create branded PKG installers for plugin distribution.
When should I use Plugin Packaging?
Plugin Packaging fits situations like: user requests to package a plugin; create installer; share plugin with others; mentions distributing/sending plugin to someone.
How do I install Plugin Packaging in Claude Code?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-packaging -a claude-code`. Or copy the skill folder (.claude/skills/plugin-packaging in glittercowboy/plugin-freedom-system) into .claude/skills/plugin-packaging in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Packaging in Codex?
Run `npx skills add glittercowboy/plugin-freedom-system --skill plugin-packaging -a codex`. Or copy the skill folder (.claude/skills/plugin-packaging in glittercowboy/plugin-freedom-system) into .agents/skills/plugin-packaging in your project. Codex loads it when a task matches its description.
Can I use Plugin Packaging 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-packaging -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-packaging, .gemini/skills/plugin-packaging, .github/skills/plugin-packaging and .opencode/skills/plugin-packaging in your project.
What does Plugin Packaging need to run?
Going by SKILL.md and its folder, Plugin Packaging needs the command-line tools its instructions call (git).
Does Plugin Packaging access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Plugin Packaging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plugin Packaging use?
No licence was found for Plugin Packaging or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Plugin Packaging use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 2.8k tokens, read only when the agent opens those files.
What are the alternatives to Plugin Packaging?
Skills that share tags, products or a category with Plugin Packaging: Packaging Static Installer (netdata/netdata, 81k stars), Brand Guidelines (alirezarezvani/claude-skills, 28k stars), Anthropic Brand Styling (anthropics/skills, 180k stars) and Brand Extract (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plugin Packaging?
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.