Update to Subtext

{
  "name": "subtext-using-subtext",
  "description": "Overview of the Subtext plugin — when to reach for session review vs privacy tools. Read to orient before reviewing a Fullstory session or managing privacy rules.",
  "included_files": [],
  "skill_md_contents": "---\nname: subtext-using-subtext\ndescription: Overview of the Subtext plugin — when to reach for session review vs privacy tools. Read to orient before reviewing a Fullstory session or managing privacy rules.\n---\n\n# Using Subtext\n\nThis plugin gives you read-only access to Fullstory session recordings, plus privacy-rule management.\n\n## When to reach for what\n\n| Signal | Skill |\n|--------|-------|\n| You have a session URL / want to know what happened | `subtext-review` |\n| You need the session-replay tool catalog (`review-*`) | `subtext-session` |\n| Detect PII or manage element-block, URL, or network privacy rules | `subtext-privacy` |\n| Log workflow milestones (e.g. onboarding progress) for analytics | `subtext-telemetry` |\n\n## Notes\n\n- Everything here is read-only analysis **except** `privacy-create` / `privacy-promote` / `privacy-delete` / `privacy-url-create` / `privacy-network-create`, which modify org privacy rules — confirm with the user first. (`telemetry-event` writes analytics events only, never org configuration — no confirmation needed.)\n- This plugin does **not** drive a live browser or capture before/after proof of code changes. That lives in the separate **Subtext Verify** plugin.\n"
}