cowork-plugin-customizer-th-th

Category: Development & Coding | Uploader: WARROOM-CEO | Downloads: 0 | Version: v1.0（Latest）

ปรับแต่งปลั๊กอิน Claude Code สำหรับเครื่องมือและเวิร์กโฟลว์ขององค์กร ใช้เมื่อ: ปรับแต่งปลั๊กอิน, ตั้งค่าปลั๊กอิน, กำหนดค่าปลั๊กอิน, ปรับการตั้งค่าปลั๊กอิน, ปรับแต่ง connector ของปลั๊กอิน, ปรับแต่ง skill ของปลั๊กอิน, แก้ไขการกำหนดค่าปลั๊กอิน, customize plugin, set up plugin, configure plugin, tailor plugin, adjust plugin settings, customize plugin connectors, customize plugin skill, tweak plugin, modify plugin configuration.

Changelog: Source: GitHub https://github.com/WARROOM-CEO/CORE

Directory Structure

Current level: tree/main/plugins/cowork-plugin-management/cowork-plugin-management-th/plugin_01QnM1nVgGYssaPokzEUmJis/skills/cowork-plugin-customizer-th/

📁 examples/
- 📄 customized-mcp.json 853 B
📁 references/
- 📄 mcp-servers-th.md 6.0 KB
- 📄 mcp-servers.md 3.1 KB
- 📄 search-strategies-th.md 3.1 KB
- 📄 search-strategies.md 1.6 KB
📄 SKILL-TH.md 19.8 KB
📄 SKILL.md 10.5 KB

SKILL.md

---
name: cowork-plugin-customizer-th-th
description: >
  ปรับแต่งปลั๊กอิน Claude Code สำหรับเครื่องมือและเวิร์กโฟลว์ขององค์กร
  ใช้เมื่อ: ปรับแต่งปลั๊กอิน, ตั้งค่าปลั๊กอิน, กำหนดค่าปลั๊กอิน, ปรับการตั้งค่าปลั๊กอิน,
  ปรับแต่ง connector ของปลั๊กอิน, ปรับแต่ง skill ของปลั๊กอิน, แก้ไขการกำหนดค่าปลั๊กอิน,
  customize plugin, set up plugin, configure plugin, tailor plugin, adjust plugin settings,
  customize plugin connectors, customize plugin skill, tweak plugin, modify plugin configuration.
compatibility: Requires Cowork desktop app environment with access to mounted plugin directories (mnt/.local-plugins, mnt/.plugins).
---

# Cowork Plugin Customization

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.

> **Language**: All user-facing output — todo list items, AskUserQuestion labels and options, summaries, and any text the user will read — must be written in **Thai (ภาษาไทย)**. Internal logic, file paths, code snippets, and technical values remain in English.

> **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 in Thai: "การปรับแต่งปลั๊กอินใช้ได้เฉพาะในโหมด Cowork ของแอปเดสก์ท็อปเท่านั้น"

## Determining the Customization Mode

After locating the plugin, check for `~~`-prefixed placeholders: `grep -rn '~~\w' /path/to/plugin --include='*.md'-th --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 a `commands/` directory. The Cowork UI now presents these alongside skills as a single "Skills" concept, so treat `commands/*.md` files the same way you would `skills/*/SKILL.md` files when-th 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 Thai. Never mention `~~` prefixes, placeholders, or customization points to the user. Frame everything in terms of the plugin's capabilities and the organization's tools.

## Customization Workflow

### Phase 0: Gather User Intent (scoped and general customization only)

For **scoped customization** and **general customization** (not generic plugin setup), check whether the user provided free-form context alongside their request.

- **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 in Thai before proceeding. E.g., "คุณต้องการเปลี่ยนแปลงอะไรใน skill นี้?" Keep it short and specific to their request.

  Use their response (if any) as additional context throughout the remaining phases.

### Phase 1: Gather Context from Knowledge MCPs

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):

- Tool names and services the organization uses
- Organizational processes and workflows
- Team conventions (naming, statuses, estimation scales)
- Configuration values (workspace IDs, project names, team identifiers)

**Sources to search:**

1. **Chat/Slack MCPs** — tool mentions, integrations, workflow discussions
2. **Document MCPs** — onboarding docs, tool guides, setup instructions
3. **Email MCPs** — license notifications, admin emails, setup invitations

Record all findings for use in Phase 3.

### Phase 2: Create Todo List

Build a todo list of changes to make, scoped appropriately:

- **For scoped customization**: Only include items related to the specific section the user asked about.
- **For generic plugin setup**: Run `grep -rn '~~\w' /path/to/plugin --include='*.md' --include='*.json'` to find all placeholder customization points. Group them by-th theme.
- **For general customization**: Read the plugin files, understand the current config, and based on the user's request, identify what needs to change.

Write todo descriptions in Thai, focused on the plugin's purpose (not file paths):

- **ดี**: "เรียนรู้วิธีเตรียม standup ที่บริษัท"
- **ไม่ดี**: "Replace placeholders in skills/standup-prep/SKILL.md"

### Phase 3: Complete Todo Items

Work through each item using context from Phase 0 and Phase 1.

**If the user's free-form input (Phase 0) or knowledge MCPs (Phase 1) provided a clear answer**: Apply directly without confirmation.

**Otherwise**: Use AskUserQuestion with Thai labels and options. Don't assume "industry standard" defaults are correct — if neither the user's input nor knowledge MCPs provided a specific answer, ask. Note: AskUserQuestion always includes a Skip button and a free-text input box for custom answers, so do not include `None` or `Other` as options.

**Types of changes:**

1. **Placeholder replacements** (generic setup): `~~Jira` → `Asana`, `~~your-org-channel` → `#engineering`
2. **Content updates**: Modifying instructions, skills, workflows, or references to match the organization
3. **URL pattern updates**: `tickets.example.com/your-team/123` → `app.asana.com/0/PROJECT_ID/TASK_ID`
4. **Configuration values**: Workspace IDs, project names, team identifiers

If user doesn't know or skips, leave the value unchanged (or the `~~`-prefixed placeholder, for generic setup).

### Phase 4: Search for Useful MCPs

After customization items have been resolved, connect MCPs for any tools that were identified or changed. See `references/mcp-servers.md` for the full workflow, category-to-keywords mapping, and config file format.

For each tool identified during customization:

1. Search the registry: `search_mcp_registry(keywords=[...])` using category keywords from `references/mcp-servers.md`, or search for the specific tool name if already known
2. If unconnected: `suggest_connectors(directoryUuids=["chosen-uuid"])` — user completes auth
3. Update the plugin's MCP config file (check `plugin.json` for custom location, otherwise `.mcp.json` at root)

Collect all MCP results and present them together in the summary output (see below) — don't present MCPs one at a time during this phase.

## Packaging the Plugin

After all customizations are applied, package the plugin as a `.plugin` file for the user:

1. **Zip the plugin directory** (excluding `setup/` since it's no longer needed):
   ```bash
   cd /path/to/plugin && zip -r /tmp/plugin-name.plugin . -x "setup/*" && cp /tmp/plugin-name.plugin-th /path/to/outputs/plugin-name.plugin
   ```
2. **Present the file to the user** with the `.plugin` extension so they can install it directly.

> **Important**: Always create the zip in `/tmp/` first, then copy to the outputs folder. Writing directly to the outputs folder may fail due to permissions and leave behind temporary-th files.

> **Naming**: Use the original plugin directory name for the `.plugin` file (e.g., if the plugin directory is `coder`, the output file should be `coder.plugin`). Do not rename the plugin or its files during customization — only replace placeholder values and update content.

## Summary Output

After customization, present the user with a Thai-language summary grouped by source. Always include the MCPs sections:

```markdown
## จากการค้นหา Slack

- คุณใช้ Asana สำหรับการจัดการโปรเจกต์
- รอบสปรินต์ 2 สัปดาห์

## จากการค้นหาเอกสาร

- Story points ใช้ขนาดเสื้อยืด

## จากคำตอบของคุณ

- สถานะ ticket: Backlog, In Progress, In Review, Done
```

Then present the MCPs that were connected during setup and any that the user should still connect, with Thai instructions on how to connect them.

If no knowledge MCPs were available in Phase 1, and the user had to answer at least one question manually, include a note at the end:

> อนึ่ง การเชื่อมต่อแหล่งข้อมูลอย่าง Slack หรือ Microsoft Teams จะช่วยให้ค้นหาคำตอบได้โดยอัตโนมัติในครั้งถัดไปที่คุณปรับแต่งปลั๊กอิน

## Additional Resources

- **`references/mcp-servers.md`** — MCP discovery workflow, category-to-keywords mapping, config file locations
- **`references/search-strategies.md`** — Knowledge MCP query patterns for finding tool names and org values
- **`examples/customized-mcp.json`** — Example fully configured `.mcp.json`

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

cowork-plugin-customizer-th-th

Directory Structure

SKILL.md

Report

Notice