opencode-knowledge-work 0.0.0-stage → 0.1.1

package/content/bio-research/skills/bio-research-start/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: start
+description: Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
+---
+
+# Bio-Research Start
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
+
+You are helping a biological researcher get oriented with the bio-research plugin. Walk through the following steps in order.
+
+## Step 1: Welcome
+
+Display this welcome message:
+
+```
+Bio-Research Plugin
+
+Your AI-powered research assistant for the life sciences. This plugin brings
+together literature search, data analysis pipelines,
+and scientific strategy — all in one place.
+```
+
+## Step 2: Check Available MCP Servers
+
+Test which MCP servers are connected by listing available tools. Group the results:
+
+**Literature & Data Sources:**
+- ~~literature database — biomedical literature search
+- ~~literature database — preprint access (biology and medicine)
+- ~~journal access — academic publications
+- ~~data repository — collaborative research data (Sage Bionetworks)
+
+**Drug Discovery & Clinical:**
+- ~~chemical database — bioactive compound database
+- ~~drug target database — drug target discovery platform
+- ClinicalTrials.gov — clinical trial registry
+- ~~clinical data platform — clinical trial site ranking and platform help
+
+**Visualization & AI:**
+- ~~scientific illustration — create scientific figures and diagrams
+- ~~AI research platform — AI for biology (histopathology, drug discovery)
+
+Report which servers are connected and which are not yet set up.
+
+## Step 3: Survey Available Skills
+
+List the analysis skills available in this plugin:
+
+| Skill | What It Does |
+|-------|-------------|
+| **Single-Cell RNA QC** | Quality control for scRNA-seq data with MAD-based filtering |
+| **scvi-tools** | Deep learning for single-cell omics (scVI, scANVI, totalVI, PeakVI, etc.) |
+| **Nextflow Pipelines** | Run nf-core pipelines (RNA-seq, WGS/WES, ATAC-seq) |
+| **Instrument Data Converter** | Convert lab instrument output to Allotrope ASM format |
+| **Scientific Problem Selection** | Systematic framework for choosing research problems |
+
+## Step 4: Optional Setup — Binary MCP Servers
+
+Mention that two additional MCP servers are available as separate installations:
+
+- **~~genomics platform** — Access cloud analysis data and workflows
+  Install: Download `txg-node.mcpb` from https://github.com/10XGenomics/txg-mcp/releases
+- **~~tool database** (Harvard MIMS) — AI tools for scientific discovery
+  Install: Download `tooluniverse.mcpb` from https://github.com/mims-harvard/ToolUniverse/releases
+
+These require downloading binary files and are optional.
+
+## Step 5: Ask How to Help
+
+Ask the researcher what they're working on today. Suggest starting points based on common workflows:
+
+1. **Literature review** — "Search ~~literature database for recent papers on [topic]"
+2. **Analyze sequencing data** — "Run QC on my single-cell data" or "Set up an RNA-seq pipeline"
+3. **Drug discovery** — "Search ~~chemical database for compounds targeting [protein]" or "Find drug targets for [disease]"
+4. **Data standardization** — "Convert my instrument data to Allotrope format"
+5. **Research strategy** — "Help me evaluate a new project idea"
+
+Wait for the user's response and guide them to the appropriate tools and skills.

package/content/customer-support/.mcp.json

@@ -0,0 +1,40 @@
+{
+  "mcpServers": {
+    "slack": {
+      "type": "http",
+      "url": "https://mcp.slack.com/mcp",
+      "oauth": {
+        "clientId": "1601185624273.8899143856786",
+        "callbackPort": 3118
+      }
+    },
+    "intercom": {
+      "type": "http",
+      "url": "https://mcp.intercom.com/mcp"
+    },
+    "hubspot": {
+      "type": "http",
+      "url": "https://mcp.hubspot.com/anthropic"
+    },
+    "guru": {
+      "type": "http",
+      "url": "https://mcp.api.getguru.com/mcp"
+    },
+    "atlassian": {
+      "type": "http",
+      "url": "https://mcp.atlassian.com/v1/mcp"
+    },
+    "notion": {
+      "type": "http",
+      "url": "https://mcp.notion.com/mcp"
+    },
+    "google calendar": {
+      "type": "http",
+      "url": ""
+    },
+    "gmail": {
+      "type": "http",
+      "url": ""
+    }
+  }
+}

package/content/customer-support/CONNECTORS.md

@@ -0,0 +1,19 @@
+# Connectors
+
+## How tool references work
+
+Plugin files use `~~category` as a placeholder for whatever tool the user connects in that category. For example, `~~support platform` might mean Intercom, Zendesk, or any other support tool with an MCP server.
+
+Plugins are **tool-agnostic** — they describe workflows in terms of categories (support platform, CRM, chat, etc.) rather than specific products. The `.mcp.json` pre-configures specific MCP servers, but any MCP server in that category works.
+
+## Connectors for this plugin
+
+| Category | Placeholder | Included servers | Other options |
+|----------|-------------|-----------------|---------------|
+| Chat | `~~chat` | Slack | Microsoft Teams |
+| Email | `~~email` | Microsoft 365 | — |
+| Cloud storage | `~~cloud storage` | Microsoft 365 | — |
+| Support platform | `~~support platform` | Intercom | Zendesk, Freshdesk, HubSpot Service Hub |
+| CRM | `~~CRM` | HubSpot | Salesforce, Pipedrive |
+| Knowledge base | `~~knowledge base` | Guru, Notion | Confluence, Help Scout |
+| Project tracker | `~~project tracker` | Atlassian (Jira/Confluence) | Linear, Asana |

package/content/customer-support/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/content/customer-support/README.md

@@ -0,0 +1,140 @@
+# Customer Support Plugin
+
+A customer support plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application — though it also works in Claude Code. Provides ticket triage, escalation management, response drafting, customer research, and knowledge base authoring for support teams.
+
+## Installation
+
+```
+claude plugin marketplace add anthropics/knowledge-work-plugins
+claude plugin install customer-support@knowledge-work-plugins
+```
+
+## What It Does
+
+This plugin turns Claude into a customer support co-pilot. It helps you:
+
+- **Triage incoming tickets** with structured categorization, priority assessment, and routing recommendations
+- **Research customer questions** by synthesizing information from multiple sources with confidence scoring
+- **Draft professional responses** tailored to the situation, urgency, and communication channel
+- **Package escalations** with full context, reproduction steps, and business impact for engineering or product
+- **Write KB articles** from resolved issues to reduce future ticket volume
+
+## Commands
+
+| Command | Description |
+|---|---|
+| `/triage` | Categorize, prioritize, and route a support ticket or customer issue |
+| `/research` | Multi-source research on a customer question or topic |
+| `/draft-response` | Draft a customer-facing response for any situation |
+| `/escalate` | Package an escalation for engineering, product, or leadership |
+| `/kb-article` | Draft a knowledge base article from a resolved issue |
+
+## Skills
+
+| Skill | Description |
+|---|---|
+| `ticket-triage` | Category taxonomy, priority framework (P1-P4), routing rules, duplicate detection |
+| `customer-research` | Multi-source research methodology, source prioritization, answer synthesis |
+| `response-drafting` | Communication best practices, tone guidelines, templates for common scenarios |
+| `escalation` | Escalation tiers, structured escalation format, impact assessment, follow-up cadence |
+| `knowledge-management` | Article structure standards, writing for searchability, review cadence, maintenance |
+
+## Data Sources
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).
+
+Connect your support platform, knowledge base, and communication tools for the best experience. Without them, provide customer context manually.
+
+**Included MCP connections:**
+- Chat (Slack) for internal discussions and customer channel context
+- Support platform (Intercom) for ticket history and customer conversations
+- CRM (HubSpot) for account details and contact information
+- Knowledge base (Guru, Notion) for internal documentation and runbooks
+- Project tracker (Atlassian) for bug reports and feature requests
+- Email and cloud storage (Microsoft 365) for customer correspondence
+
+**Additional options:**
+- See [CONNECTORS.md](CONNECTORS.md) for alternative tools in each category
+
+## Example Workflows
+
+### Triaging an Incoming Ticket
+
+```
+You: /triage Customer says their dashboard has been showing a blank
+     page since this morning — they're on the Enterprise plan
+
+Claude: Analyzing the issue...
+
+## Triage: Dashboard blank page — Enterprise customer
+
+**Category:** Bug
+**Priority:** P2 — High (core feature broken, enterprise customer)
+**Product area:** Dashboard / Frontend
+
+### Routing Recommendation
+Route to: Tier 2 Support (investigate browser/account specifics,
+then escalate to Engineering if reproducible)
+
+### Suggested Initial Response
+[Draft acknowledging the issue, asking clarifying questions
+about browser and any recent changes, offering status page link]
+```
+
+### Researching a Customer Question
+
+```
+You: /research Does our platform support SSO with Okta?
+
+Claude: Let me check across available sources...
+
+[Searches docs, knowledge base, previous conversations,
+ and web sources — synthesizes answer with confidence
+ level and source attribution]
+```
+
+### Packaging an Escalation
+
+```
+You: /escalate API returning 500 errors intermittently — 3
+     Enterprise customers reported this week
+
+Claude: I'll gather context and build the escalation brief...
+
+[Pulls ticket history, identifies affected accounts,
+ structures reproduction steps, assesses business impact,
+ and generates a structured escalation for engineering]
+```
+
+### Drafting a Response
+
+```
+You: /draft-response Customer escalation — their integration
+     has been down for 2 days and they're frustrated
+
+Claude: [Generates empathetic, professional response acknowledging
+ the frustration, taking ownership, providing a clear action
+ plan with timeline, and offering a call]
+```
+
+### Writing a KB Article
+
+```
+You: /kb-article How to configure webhook notifications —
+     just resolved this for the third customer this month
+
+Claude: [Generates a structured how-to article with prerequisites,
+ step-by-step instructions, verification steps, and common
+ issues — optimized for search]
+```
+
+## Configuration
+
+The plugin works out of the box with the included MCP connections. For the richest experience, connect additional data sources through your Claude settings:
+
+1. **Support platform**: Add your ticketing system for ticket history and customer context
+2. **Knowledge base**: Add your wiki for internal documentation and existing KB articles
+3. **Project tracker**: Add your issue tracker for bug reports and feature requests
+4. **CRM**: Add your CRM for account details and contact information
+
+Without these connections, the plugin will ask you to provide context manually and offer frameworks and templates you can fill in with your own data.