agentleFS
Sign inStart free
0mlkrizzz655335v0mlkrizzz655335v/claude-skills-zh/skills/ecosystem/plugin-management/SKILL.md

plugin-management

Skill2 starsChanged 5 months agoMITView on GitHub

插件发现与管理。推荐相关插件、查看权限依赖、管理插件连接与卸载。

We split this skill into the rules it gives an agent

13 rules. 0 are common, 7 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the Plugin Management app to discover useful integrations and manage existing plugins.

    line 8
  2. Distinctive:

    Use an available built-in tool when it already provides the needed capability.

    line 14
  3. Distinctive:

    Use an already connected plugin when it can complete the task.

    line 18
  4. Distinctive:

    Search for a plugin when an external app, account, service, or data source would materially improve the result and no available tool can …

    line 19
  5. Distinctive:

    Before saying an external service is unavailable, requesting pasted data, or proposing a manual workaround, determine whether a relevant …

    line 27
  6. Very specific:

    Call search_plugins with concise provider names, product names, or capability keywords.

    line 32
  7. Very specific:

    When a relevant unconnected plugin would help, call suggest_plugins with its exact returned plugin ID.

    line 37
  8. Very specific:

    Use get_app_permissions to inspect a plugin's permissions.

    line 48
  9. Very specific:

    Use update_app_permissions only for a permission change the user requested.

    line 49
  10. Distinctive:

    Ask before ambiguous, broad, or risky changes.

    line 50
  11. Very specific:

    Use get_plugin_dependencies to inspect required apps or dependencies.

    line 51
  12. Very specific:

    Use uninstall_app only when the user explicitly requests removal.

    line 52
  13. Distinctive:

    Keep user-facing explanations focused on the task, connection state, and requested change.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plugin Management

Use the Plugin Management app to discover useful integrations and manage existing plugins. Choose the most direct capability for the user's task before searching for anything new.

Choose the right capability

  1. Use an available built-in tool when it already provides the needed capability. General web search, image generation, memory, and sites do not require a plugin unless the user requests a specific external provider or a capability unavailable natively.
  2. Use an already connected plugin when it can complete the task.
  3. Search for a plugin when an external app, account, service, or data source would materially improve the result and no available tool can access it.

Infer plugin intent from the user's actual task. Requests involving email, calendars, messaging, documents, project management, customer systems, finance, or analytics may need an external integration even when the user never says "plugin," "install," or "connect."

Before saying an external service is unavailable, requesting pasted data, or proposing a manual workaround, determine whether a relevant plugin exists.

Find and suggest plugins

Call search_plugins with concise provider names, product names, or capability keywords. For example, use Gmail, calendar, or project management, not the entire user request. The currently available tools and any recommended plugin list are not a complete directory.

When a relevant unconnected plugin would help, call suggest_plugins with its exact returned plugin ID. Suggest the smallest useful set, preferably three or fewer. Do not suggest plugins that are already installed or already pending.

Suggestions do not block the task. Continue any work that does not require the connection and briefly explain what still needs the user's action. Never claim a plugin is installed or connected without verification. Use its tools only after its individual connection is confirmed.

Manage existing plugins

  • Use get_app_permissions to inspect a plugin's permissions.
  • Use update_app_permissions only for a permission change the user requested. Ask before ambiguous, broad, or risky changes.
  • Use get_plugin_dependencies to inspect required apps or dependencies.
  • Use uninstall_app only when the user explicitly requests removal. Correct an obvious spelling mistake when the intended plugin is unambiguous, and pass its actual name without inventing an identifier.

Keep user-facing explanations focused on the task, connection state, and requested change. Do not expose internal tool names or claim actions happened without checking their results.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free