opencode-knowledge-work 0.0.0-stage → 0.1.0

package/content/pdf-viewer/skills/pdf-viewer-view-pdf/SKILL.md

@@ -0,0 +1,147 @@
+---
+name: view-pdf
+description: Interactive PDF viewer. Use when the user wants to open, show, or view a PDF and collaborate on it visually — annotate, highlight, stamp, fill form fields, place signature/initials, or review markup together. Not for summarization or text extraction (use native Read instead).
+---
+
+# PDF Viewer — Interactive Document Workflows
+
+You have access to a local PDF server that renders documents in a live
+viewer and lets you annotate, fill forms, and place signatures with
+real-time visual feedback.
+
+## When to use this skill
+
+**Use the PDF viewer when the user wants interactivity:**
+- "Show me this contract" / "Open this paper"
+- "Highlight the key terms and let me review"
+- "Help me fill out this form"
+- "Sign this on page 3" / "Add my initials to each page"
+- "Stamp this CONFIDENTIAL" / "Mark this as approved"
+- "Walk me through this document and annotate the important parts"
+
+**Do NOT use the viewer for pure ingestion:**
+- "Summarize this PDF" → use the native Read tool directly
+- "What does page 5 say?" → use Read
+- "Extract the table from section 3" → use Read
+
+The viewer's value is showing the user the document and collaborating
+on markup — not streaming text back to you.
+
+## Tools
+
+### `list_pdfs`
+List available local PDFs and allowed local directories. No arguments.
+
+### `display_pdf`
+Open a PDF in the interactive viewer. **Call once per document.**
+- `url` — local file path or HTTPS URL
+- `page` — initial page (optional, default 1)
+- `elicit_form_inputs` — if `true`, prompts the user to fill form
+  fields before displaying (use for interactive form-filling)
+
+Returns a `viewUUID` — pass this to every `interact` call. Calling
+`display_pdf` again creates a **separate** viewer; interact calls with
+the new UUID won't reach the one the user is looking at.
+
+Also returns `formFields` (name, type, page, bounding box) if the PDF
+has fillable fields — use these coordinates for signature placement.
+
+### `interact`
+All follow-up actions after `display_pdf`. Pass `viewUUID` plus one or
+more commands. **Batch multiple commands in one call** via the
+`commands` array — they run sequentially. End batches with
+`get_screenshot` to verify changes visually.
+
+**Annotation actions:**
+- `add_annotations` — add markup (see types below)
+- `update_annotations` — modify existing (id + type required)
+- `remove_annotations` — delete by id array
+- `highlight_text` — auto-find text by query and highlight it
+  (preferred over manual rects for text markup)
+
+**Navigation actions:**
+- `navigate` (page), `search` (query), `find` (query, silent),
+  `search_navigate` (matchIndex), `zoom` (scale 0.5–3.0)
+
+**Extraction actions:**
+- `get_text` — extract text from page ranges (max 20 pages). Use for
+  reading content to decide what to annotate, NOT for summarization.
+- `get_screenshot` — capture a page as an image (verify your annotations)
+
+**Form action:**
+- `fill_form` — fill named fields: `fields: [{name, value}, ...]`
+
+## Annotation Types
+
+All annotations need `id` (unique string), `type`, `page` (1-indexed).
+Coordinates are PDF points (1/72 inch), origin **top-left**, Y increases
+downward. US Letter is 612×792pt.
+
+| Type | Key properties | Use for |
+|------|----------------|---------|
+| `highlight` | `rects`, `color?`, `content?` | Mark important text |
+| `underline` | `rects`, `color?` | Emphasize terms |
+| `strikethrough` | `rects`, `color?` | Mark deletions |
+| `note` | `x`, `y`, `content`, `color?` | Sticky-note comments |
+| `freetext` | `x`, `y`, `content`, `fontSize?` | Visible text on page |
+| `rectangle` | `x`, `y`, `width`, `height`, `color?`, `fillColor?` | Box regions |
+| `circle` | `x`, `y`, `width`, `height`, `color?`, `fillColor?` | Circle regions |
+| `line` | `x1`, `y1`, `x2`, `y2`, `color?` | Draw lines/arrows |
+| `stamp` | `x`, `y`, `label`, `color?`, `rotation?` | APPROVED, DRAFT, CONFIDENTIAL, etc. |
+| `image` | `imageUrl`, `x?`, `y?`, `width?`, `height?` | **Signatures, initials**, logos |
+
+**Image annotations** accept a local file path or HTTPS URL (no data:
+URIs). Dimensions auto-detected if omitted. Users can also drag & drop
+images directly onto the viewer.
+
+## Interactive Workflows
+
+### Collaborative annotation (AI-driven)
+1. `display_pdf` to open the document
+2. `interact` → `get_text` on relevant page range to understand content
+3. Propose a batch of annotations to the user (describe what you'll mark)
+4. On approval, `interact` → `add_annotations` + `get_screenshot`
+5. Show the user, ask for edits, iterate
+6. When done, remind them they can download the annotated PDF from the
+   viewer toolbar
+
+### Form filling (visual, not programmatic)
+Unlike headless form tools, this gives the user **live visual
+feedback** and handles forms with cryptic/unnamed fields where the
+label is printed on the page rather than in field metadata.
+
+1. `display_pdf` — inspect returned `formFields` (name, type, page,
+   bounding box)
+2. If field names are cryptic (`Text1`, `Field_7`), `get_screenshot`
+   the pages and match bounding boxes to visual labels
+3. Ask the user for values using the **visual** labels, or infer from
+   context
+4. `interact` → `fill_form`, then `get_screenshot` to show the result
+5. User confirms or edits directly in the viewer
+
+For simple well-labeled forms, `display_pdf` with
+`elicit_form_inputs: true` prompts the user upfront instead.
+
+### Signing (visual, not certified)
+1. Ask for the signature/initials image path
+2. `display_pdf`, check `formFields` for signature-type fields or ask
+   which page/position
+3. `interact` → `add_annotations` with `type: "image"` at the target
+   coordinates
+4. `get_screenshot` to confirm placement
+
+**Disclaimer:** This places a visual signature image. It is **not** a
+certified or cryptographic digital signature.
+
+## Supported Sources
+
+- Local files (paths under client MCP roots)
+- arXiv (`/abs/` URLs auto-convert to PDF)
+- Any direct HTTPS PDF URL (bioRxiv, Zenodo, OSF, etc. — use the
+  direct PDF link, not the landing page)
+
+## Out of Scope
+
+- **Summarization / text extraction** — use native Read instead
+- **Certified digital signatures** — image stamping only
+- **PDF creation** — this works on existing PDFs only

package/content/product-management/.mcp.json

@@ -0,0 +1,72 @@
+{
+  "mcpServers": {
+    "slack": {
+      "type": "http",
+      "url": "https://mcp.slack.com/mcp",
+      "oauth": {
+        "clientId": "1601185624273.8899143856786",
+        "callbackPort": 3118
+      }
+    },
+    "linear": {
+      "type": "http",
+      "url": "https://mcp.linear.app/mcp"
+    },
+    "asana": {
+      "type": "http",
+      "url": "https://mcp.asana.com/v2/mcp"
+    },
+    "monday": {
+      "type": "http",
+      "url": "https://mcp.monday.com/mcp"
+    },
+    "clickup": {
+      "type": "http",
+      "url": "https://mcp.clickup.com/mcp"
+    },
+    "atlassian": {
+      "type": "http",
+      "url": "https://mcp.atlassian.com/v1/mcp"
+    },
+    "notion": {
+      "type": "http",
+      "url": "https://mcp.notion.com/mcp"
+    },
+    "figma": {
+      "type": "http",
+      "url": "https://mcp.figma.com/mcp"
+    },
+    "amplitude": {
+      "type": "http",
+      "url": "https://mcp.amplitude.com/mcp"
+    },
+    "amplitude-eu": {
+      "type": "http",
+      "url": "https://mcp.eu.amplitude.com/mcp"
+    },
+    "pendo": {
+      "type": "http",
+      "url": "https://app.pendo.io/mcp/v0/shttp"
+    },
+    "intercom": {
+      "type": "http",
+      "url": "https://mcp.intercom.com/mcp"
+    },
+    "fireflies": {
+      "type": "http",
+      "url": "https://api.fireflies.ai/mcp"
+    },
+    "google calendar": {
+      "type": "http",
+      "url": ""
+    },
+    "gmail": {
+      "type": "http",
+      "url": ""
+    },
+    "similarweb": {
+      "type": "http",
+      "url": "https://mcp.similarweb.com/mcp"
+    }
+  }
+}

package/content/product-management/CONNECTORS.md

@@ -0,0 +1,22 @@
+# Connectors
+
+## How tool references work
+
+Plugin files use `~~category` as a placeholder for whatever tool the user connects in that category. For example, `~~project tracker` might mean Linear, Asana, Jira, or any other tracker with an MCP server.
+
+Plugins are **tool-agnostic** — they describe workflows in terms of categories (project tracker, design, product analytics, 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 |
+|----------|-------------|-----------------|---------------|
+| Calendar | `~~calendar` | Google Calendar | Microsoft 365 |
+| Chat | `~~chat` | Slack | Microsoft Teams |
+| Competitive intelligence | `~~competitive intelligence` | Similarweb | Crayon, Klue |
+| Design | `~~design` | Figma | Sketch, Adobe XD |
+| Email | `~~email` | Gmail | Microsoft 365 |
+| Knowledge base | `~~knowledge base` | Notion | Confluence, Guru, Coda |
+| Meeting transcription | `~~meeting transcription` | Fireflies | Gong, Dovetail, Otter.ai |
+| Product analytics | `~~product analytics` | Amplitude, Pendo | Mixpanel, Heap, FullStory |
+| Project tracker | `~~project tracker` | Linear, Asana, monday.com, ClickUp, Atlassian (Jira/Confluence) | Shortcut, Basecamp |
+| User feedback | `~~user feedback` | Intercom | Productboard, Canny, UserVoice |

package/content/product-management/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/product-management/README.md

@@ -0,0 +1,118 @@
+# Product Management Plugin
+
+A product management plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application — though it also works in Claude Code. Covers the full PM workflow: writing feature specs, managing roadmaps, communicating with stakeholders, synthesizing user research, analyzing competitors, and tracking product metrics.
+
+## Installation
+
+```
+claude plugin marketplace add anthropics/knowledge-work-plugins
+claude plugin install product-management@knowledge-work-plugins
+```
+
+## What It Does
+
+This plugin gives you an AI-powered product management partner that can help with:
+
+- **Feature Specs & PRDs** — Generate structured product requirements documents from a problem statement or feature idea. Includes user stories, requirements prioritization, success metrics, and scope management.
+- **Roadmap Planning** — Create, update, and reprioritize your product roadmap. Supports Now/Next/Later, quarterly themes, and OKR-aligned formats with dependency mapping.
+- **Stakeholder Updates** — Generate status updates tailored to your audience (executives, engineering, customers). Pulls context from connected tools to save you the weekly update grind.
+- **User Research Synthesis** — Turn interview notes, survey data, and support tickets into structured insights. Identifies themes, builds personas, and surfaces opportunity areas with supporting evidence.
+- **Competitive Analysis** — Research competitors and generate briefs with feature comparisons, positioning analysis, and strategic implications.
+- **Metrics Review** — Analyze product metrics, identify trends, compare against targets, and surface actionable insights.
+- **Product Brainstorming** — Explore problem spaces, generate ideas, and stress-test product thinking with a sharp sparring partner. Supports divergent ideation, assumption testing, and strategy exploration using frameworks like How Might We, Jobs-to-be-Done, First Principles, and Opportunity Solution Trees.
+
+## Commands
+
+| Command | What It Does |
+|---|---|
+| `/write-spec` | Write a feature spec or PRD from a problem statement |
+| `/roadmap-update` | Update, create, or reprioritize your roadmap |
+| `/stakeholder-update` | Generate a stakeholder update (weekly, monthly, launch) |
+| `/synthesize-research` | Synthesize user research from interviews, surveys, and tickets |
+| `/competitive-brief` | Create a competitive analysis brief |
+| `/metrics-review` | Review and analyze product metrics |
+| `/brainstorm` | Brainstorm a product idea, problem space, or strategic question with a thinking partner |
+
+## Skills
+
+| Skill | What It Covers |
+|---|---|
+| `feature-spec` | PRD structure, user stories, requirements categorization, acceptance criteria |
+| `roadmap-management` | Prioritization frameworks (RICE, MoSCoW), roadmap formats, dependency mapping |
+| `stakeholder-comms` | Update templates by audience, risk communication, decision documentation |
+| `user-research-synthesis` | Thematic analysis, affinity mapping, persona development, opportunity sizing |
+| `competitive-analysis` | Feature comparison matrices, positioning analysis, win/loss analysis |
+| `metrics-tracking` | Product metrics hierarchy, goal setting (OKRs), dashboard design, review cadences |
+| `product-brainstorming` | Brainstorming modes (problem exploration, solution ideation, assumption testing, strategy), PM frameworks, session structure, thinking partner behaviors |
+
+## Example Workflows
+
+### Writing a PRD
+
+```
+You: /write-spec
+Claude: What feature or problem are you speccing out?
+You: We need to add SSO support for enterprise customers
+Claude: [Asks about target users, constraints, success metrics]
+Claude: [Generates full PRD with problem statement, user stories, requirements, success metrics, open questions]
+```
+
+### Preparing a Stakeholder Update
+
+```
+You: /stakeholder-update
+Claude: What type of update? (weekly, monthly, launch, ad-hoc)
+You: Weekly update for the exec team
+Claude: [Pulls context from project management tool, chat, and docs]
+Claude: [Generates executive summary with progress, decisions, risks, and next milestones]
+```
+
+### Synthesizing User Research
+
+```
+You: /synthesize-research
+Claude: What research do you want to synthesize? You can paste interview notes, upload files, or I can pull from connected sources.
+You: [Pastes 8 interview transcripts]
+Claude: [Identifies themes, patterns, and insights across interviews]
+Claude: [Generates synthesis with key findings, personas, opportunity areas, and evidence]
+```
+
+### Brainstorming a Product Idea
+
+```
+You: /brainstorm Should we add AI-powered search to our product?
+Claude: Before we jump to AI search — what problem are your users hitting with search today?
+You: They can't find things. Support tickets about "can't find X" are our #2 category.
+Claude: That's a discovery problem, not necessarily a search technology problem. Let me push on this...
+Claude: [Explores whether the issue is search quality, information architecture, or content discoverability]
+Claude: [Generates 5 distinct approaches ranging from better taxonomy to AI search to guided navigation]
+Claude: [Challenges assumptions, suggests cheapest experiment to test the riskiest one]
+```
+
+### Competitive Analysis
+
+```
+You: /competitive-brief
+Claude: Which competitor(s) or feature area do you want to analyze?
+You: Compare our onboarding flow to [competitor A] and [competitor B]
+Claude: [Researches competitor onboarding approaches]
+Claude: [Generates brief with feature comparison, strengths/weaknesses, and strategic implications]
+```
+
+## Data Sources
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).
+
+Connect your project management and communication tools for the best experience. Without them, provide context manually.
+
+**Included MCP connections:**
+- Chat (Slack) for team context and stakeholder threads
+- Project tracker (Linear, Asana, monday.com, ClickUp, Atlassian) for roadmap integration, ticket context, and status tracking
+- Knowledge base (Notion) for existing specs, research, and meeting notes
+- Design (Figma) for design context and handoff
+- Product analytics (Amplitude, Pendo) for usage data, metrics, and behavioral analysis
+- User feedback (Intercom) for support tickets, feature requests, and user conversations
+- Meeting transcription (Fireflies) for meeting notes and discussion context
+
+**Additional options:**
+- See [CONNECTORS.md](CONNECTORS.md) for alternative tools in each category