opencode-knowledge-work 0.0.0-stage → 0.1.1

package/content/productivity/skills/productivity-update/SKILL.md

@@ -0,0 +1,168 @@
+---
+name: update
+description: Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
+argument-hint: "[--comprehensive]"
+---
+
+# Update Command
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
+
+Keep your task list and memory current. Two modes:
+
+- **Default:** Sync tasks from external tools, triage stale items, check memory for gaps
+- **`--comprehensive`:** Deep scan chat, email, calendar, docs — flag missed todos and suggest new memories
+
+## Usage
+
+```bash
+/productivity:update
+/productivity:update --comprehensive
+```
+
+## Default Mode
+
+### 1. Load Current State
+
+Read `TASKS.md` and `memory/` directory. If they don't exist, suggest `/productivity:start` first.
+
+### 2. Sync Tasks from External Sources
+
+Check for available task sources:
+- **Project tracker** (e.g. Asana, Linear, Jira) (if MCP available)
+- **GitHub Issues** (if in a repo): `gh issue list --assignee=@me`
+
+If no sources are available, skip to Step 3.
+
+**Fetch tasks assigned to the user** (open/in-progress). Compare against TASKS.md:
+
+| External task | TASKS.md match? | Action |
+|---------------|-----------------|--------|
+| Found, not in TASKS.md | No match | Offer to add |
+| Found, already in TASKS.md | Match by title (fuzzy) | Skip |
+| In TASKS.md, not in external | No match | Flag as potentially stale |
+| Completed externally | In Active section | Offer to mark done |
+
+Present diff and let user decide what to add/complete.
+
+### 3. Triage Stale Items
+
+Review Active tasks in TASKS.md and flag:
+- Tasks with due dates in the past
+- Tasks in Active for 30+ days
+- Tasks with no context (no person, no project)
+
+Present each for triage: Mark done? Reschedule? Move to Someday?
+
+### 4. Decode Tasks for Memory Gaps
+
+For each task, attempt to decode all entities (people, projects, acronyms, tools, links):
+
+```
+Task: "Send PSR to Todd re: Phoenix blockers"
+
+Decode:
+- PSR → ✓ Pipeline Status Report (in glossary)
+- Todd → ✓ Todd Martinez (in people/)
+- Phoenix → ? Not in memory
+```
+
+Track what's fully decoded vs. what has gaps.
+
+### 5. Fill Gaps
+
+Present unknown terms grouped:
+```
+I found terms in your tasks I don't have context for:
+
+1. "Phoenix" (from: "Send PSR to Todd re: Phoenix blockers")
+   → What's Phoenix?
+
+2. "Maya" (from: "sync with Maya on API design")
+   → Who is Maya?
+```
+
+Add answers to the appropriate memory files (people/, projects/, glossary.md).
+
+### 6. Capture Enrichment
+
+Tasks often contain richer context than memory. Extract and update:
+- **Links** from tasks → add to project/people files
+- **Status changes** ("launch done") → update project status, demote from CLAUDE.md
+- **Relationships** ("Todd's sign-off on Maya's proposal") → cross-reference people
+- **Deadlines** → add to project files
+
+### 7. Report
+
+```
+Update complete:
+- Tasks: +3 from project tracker (e.g. Asana), 1 completed, 2 triaged
+- Memory: 2 gaps filled, 1 project enriched
+- All tasks decoded ✓
+```
+
+## Comprehensive Mode (`--comprehensive`)
+
+Everything in Default Mode, plus a deep scan of recent activity.
+
+### Extra Step: Scan Activity Sources
+
+Gather data from available MCP sources:
+- **Chat:** Search recent messages, read active channels
+- **Email:** Search sent messages
+- **Documents:** List recently touched docs
+- **Calendar:** List recent + upcoming events
+
+### Extra Step: Flag Missed Todos
+
+Compare activity against TASKS.md. Surface action items that aren't tracked:
+
+```
+## Possible Missing Tasks
+
+From your activity, these look like todos you haven't captured:
+
+1. From chat (Jan 18):
+   "I'll send the updated mockups by Friday"
+   → Add to TASKS.md?
+
+2. From meeting "Phoenix Standup" (Jan 17):
+   You have a recurring meeting but no Phoenix tasks active
+   → Anything needed here?
+
+3. From email (Jan 16):
+   "I'll review the API spec this week"
+   → Add to TASKS.md?
+```
+
+Let user pick which to add.
+
+### Extra Step: Suggest New Memories
+
+Surface new entities not in memory:
+
+```
+## New People (not in memory)
+| Name | Frequency | Context |
+|------|-----------|---------|
+| Maya Rodriguez | 12 mentions | design, UI reviews |
+| Alex K | 8 mentions | DMs about API |
+
+## New Projects/Topics
+| Name | Frequency | Context |
+|------|-----------|---------|
+| Starlight | 15 mentions | planning docs, product |
+
+## Suggested Cleanup
+- **Horizon project** — No mentions in 30 days. Mark completed?
+```
+
+Present grouped by confidence. High-confidence items offered to add directly; low-confidence items asked about.
+
+## Notes
+
+- Never auto-add tasks or memories without user confirmation
+- External source links are preserved when available
+- Fuzzy matching on task titles handles minor wording differences
+- Safe to run frequently — only updates when there's new info
+- `--comprehensive` always runs interactively

package/content/sales/.mcp.json

@@ -0,0 +1,100 @@
+{
+  "mcpServers": {
+    "slack": {
+      "type": "http",
+      "url": "https://mcp.slack.com/mcp",
+      "oauth": {
+        "clientId": "1601185624273.8899143856786",
+        "callbackPort": 3118
+      }
+    },
+    "hubspot": {
+      "type": "http",
+      "url": "https://mcp.hubspot.com/anthropic"
+    },
+    "salesforce": {
+      "type": "http",
+      "url": "https://api.salesforce.com/platform/mcp/v1/platform/headless-360"
+    },
+    "close": {
+      "type": "http",
+      "url": "https://mcp.close.com/mcp"
+    },
+    "monday": {
+      "type": "http",
+      "url": "https://mcp.monday.com/mcp"
+    },
+    "clay": {
+      "type": "http",
+      "url": "https://api.clay.com/v3/mcp"
+    },
+    "zoominfo": {
+      "type": "http",
+      "url": "https://mcp.zoominfo.com/mcp"
+    },
+    "notion": {
+      "type": "http",
+      "url": "https://mcp.notion.com/mcp"
+    },
+    "atlassian": {
+      "type": "http",
+      "url": "https://mcp.atlassian.com/v1/mcp"
+    },
+    "fireflies": {
+      "type": "http",
+      "url": "https://api.fireflies.ai/mcp"
+    },
+    "apollo": {
+      "type": "http",
+      "url": "https://mcp.apollo.io/mcp"
+    },
+    "outreach": {
+      "type": "http",
+      "url": "https://api.outreach.io/mcp/"
+    },
+    "google calendar": {
+      "type": "http",
+      "url": ""
+    },
+    "gmail": {
+      "type": "http",
+      "url": ""
+    },
+    "microsoft-365": {
+      "type": "http",
+      "url": "https://microsoft365.mcp.claude.com/mcp"
+    },
+    "similarweb": {
+      "type": "http",
+      "url": "https://mcp.similarweb.com/mcp"
+    },
+    "google drive": {
+      "type": "http",
+      "url": ""
+    },
+    "gong": {
+      "type": "http",
+      "url": "https://mcp.gong.io/mcp"
+    },
+    "zoom": {
+      "type": "http",
+      "url": "https://mcp.zoom.us/mcp/zoom/streamable"
+    },
+    "otter-ai": {
+      "type": "http",
+      "url": "https://mcp.otter.ai/mcp"
+    },
+    "calendly": {
+      "type": "http",
+      "url": "https://mcp.calendly.com/"
+    },
+    "lusha": {
+      "type": "http",
+      "url": "https://mcp.lusha.com/mcp/claude"
+    },
+    "crunchbase": {
+      "type": "http",
+      "url": "https://mcp.crunchbase.com/"
+    }
+  }
+}

package/content/sales/CONNECTORS.md

@@ -0,0 +1,36 @@
+# Connectors
+
+## How tool references work
+
+Plugins are **tool-agnostic**. They describe workflows in terms of categories (CRM, chat, email, etc.) rather than specific products. The `.mcp.json` pre-configures specific MCP servers, but any MCP server in that category works.
+
+Many plugins use `~~category` placeholders in their files. The skills in this plugin name the category in plain words instead ("the CRM", "email", "the calendar", "call transcripts"). Either way, a skill refers to the category, so any connector in that category works. The placeholder column below maps each category to the shared naming used across plugins.
+
+Every skill also works with nothing connected: upload an export or paste notes, and the skill works from that.
+
+## Connectors for this plugin
+
+| Category | Placeholder | Included servers | Other options |
+|----------|-------------|-----------------|---------------|
+| CRM | `~~CRM` | HubSpot, Salesforce\*, Close, Monday | Pipedrive, Attio, Zoho CRM, Copper |
+| Email | `~~email` | Gmail, Microsoft 365 (Outlook)\* |  |
+| Calendar | `~~calendar` | Google Calendar, Calendly, Microsoft 365 (Outlook)\* |  |
+| Chat | `~~chat` | Slack, Microsoft 365 (Teams)\* |  |
+| Docs and knowledge base | `~~knowledge base` | Google Drive, Notion, Atlassian (Confluence), Microsoft 365 (SharePoint)\* | Box, Dropbox, Guru |
+| Conversation intelligence | `~~conversation intelligence` | Gong, Fireflies, Zoom, Otter.ai | Granola, Fathom, Chorus |
+| Data enrichment | `~~data enrichment` | Clay, ZoomInfo, Apollo, Lusha, Crunchbase | Clearbit |
+| Sales engagement | `~~sales engagement` | Outreach, Apollo | Salesloft |
+| Competitive intelligence | `~~competitive intelligence` | Similarweb | Crayon, Klue |
+| Project tracker | `~~project tracker` | Atlassian (Jira) | Linear, Asana |
+
+## Salesforce and Microsoft 365
+
+**Salesforce and Microsoft 365 (marked \* above) are included, and both need setup at the organization level: an admin enables the connector in Claude before people can sign in. For Salesforce, that includes setting up your org's Salesforce app.**
+
+Once connected, the skills use them the same way as any other tool in their category.
+
+Google Calendar, Gmail and Google Drive are listed in `.mcp.json` without a URL. Connect them in Claude's connector settings.
+
+## Permissions
+
+What a connector is allowed to do is set on the connector itself: allow, ask or block for each tool. The skills never go beyond those settings. See the README for recommended settings for scheduled runs.

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

@@ -0,0 +1,148 @@
+# Sales Plugin
+
+A sales plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application, though it also works in Claude Code. It helps with the whole sales day: prepping calls, summarizing and following up, researching accounts, working deals, reviewing pipeline and writing the forecast. It works with the tools your team already uses (your CRM, email, calendar, chat and call recorder) or with files you upload when nothing is connected.
+
+## Installation
+
+```bash
+claude plugin marketplace add anthropics/knowledge-work-plugins
+claude plugin install sales@knowledge-work-plugins
+```
+
+## What's new in 2.0
+
+- **From 9 to 36 skills.** New skills cover deal reviews, close plans, stakeholder maps, renewals, customer health, lead routing, CRM updates, meeting booking, inbox sweeps and team pipeline views.
+- **Works across CRMs and email providers.** Skills read your CRM's own stages and fields instead of assuming one vendor's setup, and work the same on Gmail or Outlook, Slack or Teams. No settings file is needed; a skill asks once for anything it cannot find.
+- **Uses uploaded files when nothing is connected.** Upload a pipeline export, a transcript or a list of accounts, and the skill works from that.
+- **Acts when you ask.** Skills can update CRM records, create email drafts or send email, post to chat and book meetings, within each connector's permissions. Changes a skill suggests on its own are shown to you first, with the evidence behind them.
+- **Treats outside content as information.** Emails, call transcripts, chat messages and documents are read as information, never as instructions. If an email or transcript asks for an action, the skill shows you the action before anything happens.
+- **Existing skill names still work.** `account-research`, `call-summary`, `forecast`, `call-prep`, `daily-briefing`, `draft-outreach`, `pipeline-review`, `competitive-intelligence` and `create-an-asset` keep their names, rebuilt on the new skills. Two behave differently: `create-an-asset` now builds decks, one-pagers and leave-behinds from your account data rather than landing pages or interactive demos, and `forecast` writes a commit, best-case and pipeline narrative instead of best, likely and worst scenarios.
+
+## Skills
+
+Skills run when your request matches, or directly by name (for example `/sales:call-summary`).
+
+### Your day
+
+| Skill | Description |
+|---|---|
+| `setup` | First-run setup: shows what's connected and what each tool unlocks, learns how you write, and renders a starter dashboard |
+| `daily-briefing` | Morning rundown: today's meetings with account context, deals closing soon, customer emails waiting, top actions |
+| `call-prep` | Pre-call brief: attendees, account history, prior call context, open opportunity status, discovery questions |
+| `call-summary` | Turn a transcript or call notes into a follow-up email draft, a team summary and proposed CRM updates |
+| `inbox-sweep` | Sort unread customer emails by priority and draft replies |
+| `schedule-meeting` | Find a time, draft the invite, book it on your calendar and log it to the CRM |
+| `log-activity` | Log a call, meeting or email to the right account, opportunity and contact in the CRM |
+| `end-of-day` | Close out the day: calls processed, CRM current, commitments captured, tomorrow's top three |
+| `weekly-wrap` | End-of-week summary of what closed, moved and slipped, and what's on deck Monday |
+
+### Accounts and prospecting
+
+| Skill | Description |
+|---|---|
+| `account-research` | Research a company or contact: overview, recent news, likely priorities and fit against your ICP |
+| `account-context` | One brief on an account from CRM data, email, docs, transcripts and team chat |
+| `stakeholder-map` | Map the people in a deal: roles, influence, sentiment, who's missing and your best way in |
+| `draft-outreach` | Draft a personalized email or multi-touch sequence, and add the contact to a sequence when asked |
+| `lead-triage` | Score an inbound lead or rank a lead backlog against your ICP and recommend next actions |
+| `route-lead` | Decide who owns an unrouted lead or opportunity and draft the handoff notes |
+| `account-tiering` | Score and tier a list of accounts or your whole book by fit and engagement |
+| `account-plan` | Build or refresh a strategic account plan and sync key fields to the CRM |
+| `expansion-whitespace` | Find expansion plays in an account or book, with evidence and the opportunities to create |
+
+### Deals
+
+| Skill | Description |
+|---|---|
+| `deal-review` | Deep-dive on one opportunity: health score, risks, qualification gaps and next actions |
+| `deal-advance-gap` | What is missing to move a deal to the next stage and to close, with owners and dates |
+| `deal-signals` | Alerts across your book: deals gone quiet, slipping close dates, champion changes, competitor mentions |
+| `deal-slip-scenario` | Model the effect on your number if a deal slips, shrinks or is lost |
+| `close-plan` | Business case and mutual action plan: why buy, why now, and the dated path to signature |
+| `handle-objection` | Work through an objection or competitive threat with responses and proof points from your own history |
+| `competitive-intelligence` | The play against a named competitor in a deal, plus win/loss patterns and battlecards across the book |
+| `create-an-asset` | Build a customer deck, one-pager or leave-behind from your account data, with no made-up numbers |
+| `update-opportunity` | Update stage, close date, next steps, amount or forecast category, with a before and after |
+
+### Pipeline and forecast
+
+| Skill | Description |
+|---|---|
+| `pipeline-review` | Stage-by-stage pipeline health: coverage, aging, conversion and at-risk deals |
+| `crm-hygiene-check` | Read-only audit of opportunities for missing fields, stale dates and stage mismatches |
+| `forecast` | The commit, best-case and pipeline narrative for a forecast call or a 1:1 with your manager |
+| `team-pipeline` | Leader view of a team's pipeline by rep and stage, with at-risk deals and coaching moments |
+| `rep-context` | Leader prep for a 1:1 with a rep: pipeline, recent activity and where they may need help |
+| `win-loss-review` | Patterns in recently closed deals: where deals are lost, common objections, what wins |
+
+### Customers
+
+| Skill | Description |
+|---|---|
+| `customer-health` | Health check on a customer and QBR prep: relationship, engagement, risks and value delivered |
+| `customer-voice` | Direct, attributed customer quotes on a topic from call transcripts and email |
+| `renewal-radar` | Upcoming renewals with timing, risk and uplift potential |
+
+## Example workflows
+
+### After a call
+
+```
+/sales:call-summary
+```
+
+Paste your notes or transcript, or name the call if your call recorder is connected. You get a summary, a follow-up email draft, a team summary and proposed CRM updates. Nothing is written to the CRM or sent until you say so.
+
+### Forecast call
+
+```
+Write my forecast for this quarter
+```
+
+The `forecast` skill reads your open opportunities (or an uploaded pipeline export) and writes the commit, best-case and pipeline story, what changed and where the risk is.
+
+### Researching a prospect
+
+```
+Research Acme Corp before my call tomorrow
+```
+
+The `account-research` skill gives you a company overview, recent news, likely priorities and fit against your ICP, and checks whether the company is already in your CRM.
+
+## Works with files, better with your tools
+
+Every skill works without any connectors:
+
+| What you can do | With nothing connected | With connected tools |
+|---|---|---|
+| Summarize a call and follow up | Paste notes or a transcript | Call recorder, email, CRM, chat |
+| Review pipeline and forecast | Upload a pipeline export | CRM |
+| Research accounts | Web search and your context | Data enrichment, CRM |
+| Prep for calls | Describe the meeting | Calendar, CRM, email, call recorder |
+| Draft outreach | Web search and your context | Email, CRM, sales engagement |
+| Update the CRM | Get a checklist to apply by hand | CRM |
+| Book meetings | Get a draft invite to send yourself | Calendar, CRM |
+
+With nothing connected, a skill says plainly what it used and what it could not see.
+
+## Connectors
+
+> To check which tools are included and what else works, see [CONNECTORS.md](CONNECTORS.md).
+
+| Category | Examples | What it enables |
+|---|---|---|
+| **CRM** | HubSpot, Close, Salesforce | Opportunities, accounts, contacts, record updates |
+| **Email and calendar** | Gmail, Google Calendar, Calendly, Microsoft 365 | Customer threads, drafts, meetings, booking |
+| **Call recorder** | Gong, Fireflies, Zoom, Otter.ai | Transcripts and call history |
+| **Data enrichment** | Clay, ZoomInfo, Apollo, Lusha, Crunchbase | Company and contact data |
+| **Chat** | Slack, Microsoft Teams | Team context and summaries posted to channels |
+
+**Salesforce and Microsoft 365 (Outlook, Teams, SharePoint) are included. Your organization's admin enables each one in Claude before people can sign in; for Salesforce, that includes setting up your org's Salesforce app.**
+
+See [CONNECTORS.md](CONNECTORS.md) for every included server and other options.
+
+## For admins
+
+Connector permissions are where your team controls what runs. Each connector can allow, ask or block each of its tools, and the skills never go beyond those settings. If a write tool is blocked, the skill keeps working and hands the person a checklist to apply by hand.
+
+For scheduled runs (a morning briefing, a weekly deal signals digest), set send, post and write tools to **ask**, so nothing goes out or changes without a person approving it.