Update to SalesEQ

{
  "name": "saleseq-docs",
  "description": "Answer questions about how the SalesEQ product works — recording and the desktop app, sharing and permissions, groups, auto-share rules, public links, insights and reporting, calendar/email/HubSpot integrations, members and roles, billing, two-factor, and connecting SalesEQ to an AI assistant. Fetches the official docs rather than answering from memory. Use when someone asks how to do something in SalesEQ, why SalesEQ behaved a certain way, what a SalesEQ term means, or how a SalesEQ feature is configured. Do NOT use this to look up meeting content — the SalesEQ MCP tools handle searching meetings, reading transcripts, and pulling summaries.",
  "included_files": [],
  "skill_md_contents": "---\nname: saleseq-docs\ndescription: Answer questions about how the SalesEQ product works — recording and the desktop app, sharing and permissions, groups, auto-share rules, public links, insights and reporting, calendar/email/HubSpot integrations, members and roles, billing, two-factor, and connecting SalesEQ to an AI assistant. Fetches the official docs rather than answering from memory. Use when someone asks how to do something in SalesEQ, why SalesEQ behaved a certain way, what a SalesEQ term means, or how a SalesEQ feature is configured. Do NOT use this to look up meeting content — the SalesEQ MCP tools handle searching meetings, reading transcripts, and pulling summaries.\n---\n\n# SalesEQ product documentation\n\nAnswers questions about **how SalesEQ works as a product**. This is not for querying meeting\ndata — the MCP tools (`search_meetings`, `get_transcript`, `get_meeting_summary`,\n`list_meetings`, `get_meeting_frame`, `get_org_context`) own that, and they describe their own\nusage. Use this skill for product behavior, configuration, terminology, and troubleshooting.\n\n## Fetch the docs; do not answer from memory\n\nSalesEQ ships fast and the product changes. Model recall of SalesEQ specifics is unreliable and\nwill invent settings that do not exist. Always fetch before answering anything beyond the\nvocabulary below.\n\nThe docs site publishes agent-readable endpoints:\n\n| URL | What it is |\n| --- | --- |\n| `https://saleseq.ai/docs/llms.txt` | Index of every page with a one-line description (~5 KB). **Start here.** |\n| `https://saleseq.ai/docs/<path>.md` | Any page as clean Markdown — append `.md` to the page URL |\n| `https://saleseq.ai/docs/llms-full.txt` | Every page concatenated (~110 KB). Only when a question genuinely spans the whole product. |\n\n### Workflow\n\n1. Fetch `https://saleseq.ai/docs/llms.txt` and pick the page(s) whose description matches the\n   question.\n2. Fetch those pages as `.md`. Fetch two or three in parallel when a question straddles sections\n   — sharing questions often need both `sharing/share-a-meeting.md` and `sharing/groups.md`.\n3. Answer from what you fetched, and link the human-readable page (the URL without `.md`).\n4. If the docs do not cover it, say so and point to `https://www.saleseq.ai/docs`. Do not guess\n   at menu paths, setting names, or plan limits.\n\n## Vocabulary\n\nEnough to route a question correctly without a fetch. Anything beyond this, fetch.\n\n- **Meeting** — the central object: recording, transcript, participants, and everything generated\n  on top. Arrives three ways: recorded by the desktop app, uploaded by hand, or pulled in by an\n  integration. Some meetings are audio-only or transcript-only.\n- **Organization** — the company account. Owns members, groups, settings, and meetings. Every\n  meeting belongs to exactly one.\n- **Member / Admin** — the two roles. Lowercase \"member\" means anyone in the org; capitalized\n  **Member** is the non-Admin role. Admins manage members, invites, groups, and org-wide sharing.\n- **Group** — a named set of people (Sales, Leadership). Share with a group and later joiners get\n  access too.\n- **Owner** — the person who recorded or uploaded a meeting. Ownership does not transfer.\n- **Viewer / Editor** — the two grant roles. Viewer watches and reads; Editor also edits and\n  shares onward. Sharing is additive: the highest applicable role wins.\n- **Auto-share rule** — shares a meeting the moment it finishes, without manual action.\n- **Public link** — shares a meeting with someone outside the organization.\n\nRecording happens on the user's own machine via the desktop app. **No bot joins the call** and no\nextra participant appears — this is a frequent point of confusion when comparing SalesEQ to\nbot-based notetakers.\n\n## Section map\n\nRoute to the right part of `llms.txt` fast:\n\n- **getting-started** — create/join an org, first recording, download, concepts\n- **capturing-meetings** — desktop app, automatic recording, upload, Live AI, recording notice,\n  what gets captured\n- **your-meetings** — viewing, Ask AI, search, delete and discard\n- **sharing** — share a meeting, groups, auto-share rules, public links\n- **insights** — meeting insights, reporting\n- **integrations** — calendar, email and follow-up drafts, HubSpot\n- **ai-assistants** — overview, connect Claude, connect ChatGPT, connect a custom MCP client,\n  the tool list, troubleshooting\n- **account** — members and roles, billing, two-factor, onboarding flow\n\n## Connection and auth questions\n\nQuestions about connecting SalesEQ to Claude, ChatGPT, or another MCP client, or about why the\ntools return nothing, live under `ai-assistants`. `ai-assistants/troubleshooting.md` is the right\nfirst fetch for \"the connector isn't returning my meetings.\"\n\nEmpty tool results are usually **access**, not failure: the tools return only meetings the account\nowns, meetings shared with it directly, and meetings shared with a group it belongs to. Check that\nbefore treating an empty result as a bug.\n"
}