Token导航 LogoToken导航

Agent Skill · AI 工具

plugin-lifecycle(插件生命周期)

plugin-lifecycle 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

plugin-lifecycle 是AI 工具类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证为 MIT,第三方扫描有提醒项,按安装量在AI 工具类的 2,536 个 Skill 里排第 2,064。

总安装 339周安装 14GitHub Stars 182下载 111核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:plugin-lifecycle(插件生命周期)
来源仓库:https://github.com/glittercowboy/plugin-freedom-system
仓库路径:skills/plugin-lifecycle
安装命令:
npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill plugin-lifecycle
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill plugin-lifecycle

这个 Skill 是做什么的

AI 工具类 Skill 用来扩展助手本身的能力,例如接模型、接检索、接外部服务。

plugin-lifecycle 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合围绕仓库状态和协作事项进行整理。它适用于代码审查、变更追踪和团队协作场景,可帮助 Agent 梳理项目结构和提交历史。

通过仓库路径、Issue 编号或 PR ID 触发,返回相关元数据和变更内容供进一步分析。

安装命令为 npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill plugin-lifecycle,需确认 GitHub API 访问权限。

使用前应检查仓库可见性和维护状态,避免依赖私有或归档项目,防止触发不必要的网络请求。

来源仓库内路径:skills/plugin-lifecycle

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill pl…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

plugin-lifecycle 怎么安装?

在终端执行 npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill plugin-lifec…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

plugin-lifecycle 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

plugin-lifecycle 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill plugin-lifecycle;npx skills add glittercowboy/plugin-freedom-system --skill "plugin-lifecycle" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

plugin-lifecycle 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

plugin-lifecycle 用的人多吗?

公开数据是累计安装 339 次,近一周安装 14 次,下载 111 次,GitHub 182 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

plugin-lifecycle 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理AI 工具类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

AI 工具类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
executing-plans

执行计划 · Codex、Claude

1,515,336173,110只读MIT通过
verification-before-completion

完成前的验证 · Codex、Claude

1,319,472173,121权限未标注MIT通过
subagent-driven-development

子 Agent 驱动开发 · Codex、Claude

1,312,416173,138只读MIT通过
copy-editing

复制编辑 · Codex、Claude

1,209,57625,632只读MIT通过
paywall-upgrade-cro

付费专区升级 cro · Codex、Claude

1,030,17625,617只读MIT通过
plugin-lifecycle

插件生命周期 · 本页

339182执行命令MIT有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

plugin-lifecycle Skill

Purpose: Manage the complete lifecycle of plugins from installation to removal with proper state tracking and safety features.

Overview

This skill handles all plugin lifecycle operations on macOS:

  • Installation (Mode 1): Copy Release binaries to system folders (~/Library/Audio/Plug-Ins/)
  • Uninstallation (Mode 2): Clean removal from system folders (preserves source code)
  • Reset to Ideation (Mode 3): Remove implementation, keep idea/mockups (surgical rollback)
  • Destroy (Mode 4): Complete removal with backup (nuclear option)

All operations include proper permissions, cache clearing, state tracking, and safety features (confirmations, backups).


Mode Dispatcher

This skill operates in different modes based on the invoking command:

ModeOperationCommandPurpose
1Installation/install-pluginDeploy to system folders
2Uninstallation/uninstallRemove binaries, keep source
3Reset to Ideation/reset-to-ideationRemove implementation, keep idea/mockups
4Destroy/destroyComplete removal with backup
MenuInteractive/cleanPresent menu, user chooses mode

Invocation Pattern: When user runs /install-plugin [Name], the command expands to a prompt that invokes THIS skill. Determine mode by examining command (see references/invocation-protocol.md), then load ONLY the relevant reference file:

  • Mode 1 → Load and execute references/installation-process.md ONLY
  • Mode 2 → Load and execute references/uninstallation-process.md ONLY
  • Mode 3 → Load and execute references/mode-3-reset.md ONLY
  • Mode 4 → Load and execute references/mode-4-destroy.md ONLY
  • Menu → Present menu, wait for selection, then load chosen mode reference file

IMPORTANT: Do NOT load other mode reference files. Load only the reference file for the active mode to optimize context window usage.

Installation targets (macOS):

  • VST3, AU: ~/Library/Audio/Plug-Ins/VST3/, ~/Library/Audio/Plug-Ins/Components/
  • AAX: ~/Library/Application Support/Avid/Audio/Plug-Ins/ (future)

Installation Workflow (Mode 1 - Critical - Do Not Skip Steps)

Copy this checklist to track installation progress:

Installation Progress:
- [ ] Step 1: Build verification (BLOCKING)
- [ ] Step 2: Product name extraction
- [ ] Step 3: Old version removal
- [ ] Step 4: Copy to system folders (BLOCKING)
- [ ] Step 5: Permissions verification (BLOCKING)
- [ ] Step 6: Cache clearing
- [ ] Step 7: Verification (BLOCKING)
- [ ] Step 8: PLUGINS.md update (BLOCKING)

Execute these steps in order:

  1. Build Verification (BLOCKING) - Check Release binaries exist, offer to build if missing

- See: references/installation-process.md Step 1 - Cannot proceed without binaries

  1. Product Name Extraction - Extract PRODUCT_NAME from CMakeLists.txt

- See: references/installation-process.md Step 2 - Required for all subsequent steps

  1. Old Version Removal - Remove existing installations to prevent conflicts

- See: references/installation-process.md Step 3 - Can proceed if no old version exists

  1. Copy to System Folders (BLOCKING) - Install VST3 and AU to macOS plugin directories

- See: references/installation-process.md Step 4 - Core installation step

  1. Permissions Verification (BLOCKING) - Set 755 permissions for DAW access

- See: references/installation-process.md Step 5 - DAWs cannot load plugins without correct permissions

  1. Cache Clearing - Clear Ableton Live and Logic Pro caches

- See: references/cache-management.md - Display warning if fails, then proceed

  1. Verification (BLOCKING) - Confirm installation with file checks and size validation

- See: references/installation-process.md Step 7 - Must confirm success before declaring completion

  1. PLUGINS.md Update (BLOCKING) - Record installation status and locations

- See: references/installation-process.md Step 8 - State tracking is part of success criteria

Note: Steps marked BLOCKING must succeed before proceeding.

Feedback Loop: If Step 7 (Verification) fails:

  1. Review error details
  2. Check reference file: references/error-handling.md
  3. Apply fix
  4. Retry from Step 4 (Copy to System Folders)

If verification succeeds, proceed to decision menu.

See references/installation-process.md for complete implementation.


Cache Management

See references/cache-management.md for cache clearing procedures (invoked during installation and uninstallation).


Uninstallation Workflow (Mode 2)

See references/uninstallation-process.md for complete uninstallation process (locate, confirm, remove, clear caches, update PLUGINS.md).


Reset to Ideation Workflow (Mode 3)

Surgical rollback - removes implementation, preserves idea/mockups. Use case: Implementation failed but concept is solid. See references/mode-3-reset.md for complete process.


Destroy Workflow (Mode 4)

Complete removal with backup. Use case: Abandoned experiment, never using again. Requires exact plugin name confirmation (safety gate). See references/mode-4-destroy.md for complete process.


Interactive Menu (Mode: Menu)

When invoked via /clean [PluginName], present interactive menu:

Plugin cleanup options for [PluginName]:

1. Uninstall - Remove binaries from system folders (keep source code)
2. Reset to ideation - Remove implementation, keep idea/mockups
3. Destroy - Complete removal with backup (IRREVERSIBLE except via backup)
4. Cancel

Choose (1-4): _

Menu logic:

  1. Read current status from PLUGINS.md
  2. Filter options based on status:

- IF status = "💡 Ideated" → Show options 2, 3, 4 (cannot uninstall what isn't built) - IF status = "✅ Working" → Show options 1, 2, 3, 4 (not installed yet) - IF status = "📦 Installed" → Show ALL options (full lifecycle available) - IF status = "🚧 In Progress" → Show only option 4 (Cancel) - ELSE (unknown status) → Show ALL options with warning: "Unknown status '[status]' - showing all options"

  1. Present filtered menu, wait for user choice
  2. Route to selected mode (1-4) or exit on Cancel

Checkpoint Protocol

After successful operations, check workflow mode before presenting decision menu:

  1. Check workflow mode:

- Read .claude/preferences.json for workflow.mode setting - Modes: "manual" (present menu) or "express" (skip menu)

  1. Manual mode (default):

- Present decision menu to user - See references/decision-menu-protocol.md for menu format

  1. Express mode:

- Skip decision menu - Return control to caller immediately

Note: plugin-lifecycle operations are terminal (don't chain to next stage), so express mode behavior is: complete operation → skip menu → end workflow.


Integration Points

Invoked by:

  • /install-plugin [PluginName] → Mode 1 (Installation)
  • /uninstall [PluginName] → Mode 2 (Uninstallation)
  • /reset-to-ideation [PluginName] → Mode 3 (Reset)
  • /destroy [PluginName] → Mode 4 (Destroy)
  • /clean [PluginName] → Interactive menu
  • plugin-workflow skill → After Stage 3 (auto-installs)
  • plugin-improve skill → After successful changes (offers reinstallation)
  • Natural language: "Install [PluginName]", "Remove [PluginName]", "Clean up [PluginName]"

Invokes:

  • None (terminal skill, doesn't invoke others)

Invocation patterns: See references/invocation-protocol.md for mode detection and routing.

Updates:

  • PLUGINS.md → Table row: status, version, last updated
  • plugins/[Name]/NOTES.md → Status metadata, timeline entries, installation details

Creates:

  • System folder installations (non-git-tracked):

- ~/Library/Audio/Plug-Ins/VST3/[Product].vst3 - ~/Library/Audio/Plug-Ins/Components/[Product].component

Blocks:

  • None (installation is optional, plugins can be tested without installing)

Success Criteria

Installation is successful when: VST3/AU installed with 755 permissions, caches cleared, PLUGINS.md updated, user informed of next steps.


平台分布

Claude Code

31.11%
按下载量换算35

windsurf

20.64%
按下载量换算23

OpenCode

18.2%
按下载量换算20

Codex

11.69%
按下载量换算13

Antigravity

7.07%
按下载量换算8

Gemini CLI

3.72%
按下载量换算4

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/glittercowboy/plugin-freedom-system --skill plugin-lifecycle;npx skills add glittercowboy/plugin-freedom-system --skill "plugin-lifecycle" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills