为特定组织定制 Claude Code 插件配置、连接器与工作流适配方案。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "cowork-plugin-customizer" 技能: 1. 下载 https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/cowork-plugin-management/skills/cowork-plugin-customizer/SKILL.md 2. 保存为 ~/.claude/skills/cowork-plugin-customizer/SKILL.md 3. 装好后重载技能,告诉我可以用了
请帮我为 Claude Code 插件定制配置,使其适配我们公司的 Jira、GitLab 和内部知识库。输出建议的连接器设置、认证方式、权限范围,以及按开发团队工作流优化后的配置说明。
一套适配企业内部系统的插件配置建议,包含连接器、权限与工作流说明。
请根据以下团队流程定制 Claude Code 插件:需求在 Jira 管理,代码在 GitHub,发布通过 CI/CD 流水线完成。请设计插件的默认行为、常用命令建议和适合团队协作的设置。
面向团队开发流程的插件定制方案,包括默认设置与协作规则建议。
我们要在受限环境中使用 Claude Code 插件,请帮我调整插件配置,限制可访问的系统、定义最小权限原则,并给出适合审计与合规要求的设置建议。
一份兼顾安全、权限控制与合规需求的插件配置优化方案。
Customize a plugin for a specific organization — either by setting up a generic plugin template for the first time, or by tweaking and refining an already-configured plugin.
Finding the plugin: To find the plugin's source files, run
find mnt/.local-plugins mnt/.plugins -type d -name "*<plugin-name>*"to locate the plugin directory, then read its files to understand its structure before making changes. If you cannot find the plugin directory, the user is likely running this conversation in a remote container. Abort and let them know: "Customizing plugins is currently only available in the desktop app's Cowork mode."
After locating the plugin, check for ~~-prefixed placeholders: grep -rn '~~\w' /path/to/plugin --include='*.md' --include='*.json'
Default rule: If
~~placeholders exist, default to Generic plugin setup unless the user explicitly asks to customize a specific part of the plugin.
1. Generic plugin setup — The plugin contains ~~-prefixed placeholders. These are customization points in a template that need to be replaced with real values (e.g., ~~Jira → Asana, ~~your-team-channel → #engineering).
2. Scoped customization — No ~~ placeholders exist, and the user asked to customize a specific part of the plugin (e.g., "customize the connectors", "update the standup skill", "change the ticket tool"). Read the plugin files to find the relevant section(s) and focus only on those. Do not scan the entire plugin or present unrelated customization items.
Legacy
commands/directories: Some plugins include acommands/directory. The Cowork UI now presents these alongside skills as a single "Skills" concept, so treatcommands/*.mdfiles the same way you wouldskills/*/SKILL.mdfiles when customizing.
3. General customization — No ~~ placeholders exist, and the user wants to modify the plugin broadly. Read the plugin's files to understand its current configuration, then ask the user what they'd like to change.
Important: Never change the name of the plugin or skill being customized. Do not rename directories, files, or the plugin/skill name fields.
Nontechnical output: All user-facing output (todo list items, questions, summaries) must be written in plain, nontechnical language. Never mention
~~prefixes, placeholders, or customization points to the user. Frame everything in terms of the plugin's capabilities and the organization's tools.
For scoped customization and general customization (not generic plugin setup), check whether the user provided free-form context alongside their request (e.g., "customize the standup skill — we do async standups in #eng-updates every morning").
If the user provided context: Record it and use it to pre-fill answers in Phase 3 — skip asking questions that the user already answered here.
If the user did not provide context: Ask a single open-ended question using AskUserQuestion before proceeding. Tailor the question to what they asked to customize — e.g., "What changes do you have in mind for the brief skill?" or "What would you like to change about how this plugin works?" Keep it short and specific to their request.
Use their response (if any) as additional context throughout the remaining phases.
Use company-internal knowledge MCPs to collect information relevant to the customization scope. See references/search-strategies.md for detailed query patterns by category.
What to gather (scope to what's relevant):
Sources to search:
…
帮助你快速查询指标、分析趋势成因,并生成面向干系人的数据报告。
将其他 AI 编码助手的技能规范转换为 Amplifier 原生 SKILL.md 文件