Update to Subtext

{
  "name": "subtext-shared",
  "description": "Foundation skill for the Subtext plugin. MCP tool conventions and security rules. Read this when any skill lists it in PREREQUISITE.",
  "included_files": [],
  "skill_md_contents": "---\nname: subtext-shared\ndescription: Foundation skill for the Subtext plugin. MCP tool conventions and security rules. Read this when any skill lists it in PREREQUISITE.\n---\n\n# Shared\n\nFoundation for all Subtext skills. Read this when a skill lists it in PREREQUISITE.\n\n## MCP Servers\n\nAll tools are served from the **subtext** MCP server. A **subtext-eu1** variant exists for EU1 data center sessions (`app.eu1.fullstory.com`). The agent framework resolves tool prefixes automatically based on the configured MCP servers — you do not need to hardcode prefixes.\n\n## Tool Name Prefixes\n\n| Prefix | Tools |\n|--------|-------|\n| `review-` | Session replay: `review-list-sessions`, `review-open`, `review-summary`, `review-zoom`, `review-snapshot`, `review-close` |\n| `privacy-` | Privacy rules: `privacy-propose`, `privacy-create`, `privacy-list`, `privacy-delete`, `privacy-promote`, `privacy-url-list`, `privacy-url-create`, `privacy-network-list`, `privacy-network-create` |\n| `telemetry-` | Workflow telemetry: `telemetry-event` |\n\n## Discovering MCP Tool Parameters\n\nEach MCP tool is self-describing. If you're unsure about parameters, the tool's schema is available at call time. Don't memorize parameter lists — consult the atomic skill (`subtext-session` or `subtext-privacy`) for which tools exist, then let the schema guide parameter usage.\n\n## Security Rules\n\n- Never expose API tokens, session tokens, or credentials in output.\n- Confirm with the user before any write operation that modifies org configuration (e.g. `privacy-promote`, `privacy-create`, `privacy-url-create`, `privacy-network-create`).\n- Session URLs may contain sensitive user data — don't log or repeat them unnecessarily.\n"
}