--- name: recording description: Demo/recording mode that redacts personally identifiable and sensitive information from Claude Code's outputs. Use when the user invokes /recording or says they are about to record, screen-share, or demo their Claude Code session and want PII scrubbed in real time. --- # Recording Mode Activate this mode when the user runs `/recording` or otherwise signals a demo/screen-share. Stay in this mode for the rest of the session unless the user says "stop recording", "/recording off", or equivalent. ## Core rule While recording mode is active, every user-visible output (chat text, code, file contents shown inline, tool result summaries, commit messages, file names invented for examples) MUST have sensitive content replaced with **obviously fake** placeholder data before it leaves the assistant. This applies to text the model generates. It does NOT retroactively edit files on disk — only what the audience sees on screen. If asked to write redacted content to a file, do so explicitly; otherwise leave files alone. ## What to redact Replace these categories: - **Names** (people, partners, family, colleagues, clients) → `Alex Doe`, `Jamie Roe`, `Sam Park` - **Handles / emails / phones / URLs with identifiers** → `@demo_user`, `user@example.com`, `+49 000 000 0000` - **Org / company / brand names** (when private) → `Acme Co`, `Globex` - **Locations** — anything more specific than continent. City, neighborhood, street, venue, coordinates, IP-derived location → `Some City`, `Main Street`, `Venue A`. Even "Berlin" gets replaced if it could identify the user. - **Dates** — any real calendar date (birthdays, appointments, sessions, deadlines, deploy dates, transaction dates, file timestamps shown inline) → shift to placeholder dates like `2025-01-01`, `2025-01-02`. Keep relative ordering and weekday if it matters to the demo. Today's actual date should be replaced too if it appears in output. - **Financial values** (revenue, prices, salaries, invoice amounts) → round dummy numbers like `€1,234` or `$X,XXX` - **Medical info** (diagnoses, medications, doses, symptoms, lab values) → `[medication]`, `[condition]`, `[symptom]` - **Emotional / therapy / coaching content** (feelings, session notes, DIMs/SIMs, relationship details) → `[personal reflection]` - **Business info** (deal terms, client lists, internal strategy, unreleased projects) → `[business detail]` - **Credentials** (tokens, keys, passwords, session IDs, file paths containing usernames) → `sk-XXXX`, `/Users/demo/...` - **Genetic / health data** specific to the user → `[genetic marker]` When in doubt, redact. The cost of over-redaction in a demo is near zero; the cost of leaking is high. ## Style of replacement - Use **obviously dummy** values, not plausible fakes that could be mistaken for real ones. `Alex Doe` not `Andrey Volkov`. `Acme Co` not `Northwind Studio`. - Keep replacements **consistent within a session**: the same real name maps to the same fake name every time, so the demo stays coherent. Maintain this mapping mentally for the duration of recording mode. - Preserve **structure and length roughly** so the demo still reads naturally (e.g. a real email becomes a fake email, not `[REDACTED]`). - Preserve **technical accuracy** of non-sensitive parts: code logic, library names, public APIs, framework terminology stay exact. ## What NOT to redact - Public technical content: language keywords, public package names, public docs URLs, generic file names (`README.md`, `package.json`). - The user's own typed input — do not rewrite what they said, only what the assistant outputs. - Vault structure conventions and folder names that are already public knowledge from CLAUDE.md. ## Tool calls Tool calls themselves run normally — redaction is about what the assistant *says*. But: - When **summarizing** tool results back to the user, apply redaction to the summary. - When **quoting** file contents inline (e.g. showing a snippet of a daily note), redact the snippet. - Avoid reading sensitive files into the visible transcript unnecessarily — prefer to act on them silently and report a redacted summary. ## Toggle behavior `/recording` is a **toggle**. Calling it flips the current state: - If recording mode is OFF, `/recording` turns it ON. Reply with one short redacted line confirming it's on. - If recording mode is ON, `/recording` turns it OFF. Reply with one short line confirming it's off, then resume normal output. Track the current state across the session. Natural-language equivalents also toggle: "I'm about to record" / "starting a demo" turn it on; "stop recording" / "demo done" / "you can stop redacting" turn it off. When in doubt about intent, infer from current state — if already recording and the user says "recording", they mean stop. ## Self-check before sending Before emitting any message while recording mode is active, scan the draft for: 1. Any proper noun that isn't a public technical term. 2. Any number that looks like money, age, dose, or measurement tied to the user. 3. Any path containing `glebkalinin`, `Brains/brain`, real folder names from People/, Daily/, etc. 4. Any emotional or medical vocabulary tied to a first-person subject. If any hit, redact and re-check. Only then send. --- Source attribution: glebis Original project: https://github.com/glebis/claude-skills/blob/d824f5a4a919b71a54c09ce23a23d65664d42b6c/recording/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025-2026 Gleb Kalinin Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: glebis Original project: https://github.com/glebis/claude-skills/blob/d824f5a4a919b71a54c09ce23a23d65664d42b6c/recording/SKILL.md Attribution basis: Source repository record Fields of work: Sales, Customer Support Roles: Customer Success Manager, Support Agent, Technical Support Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: c9fce7e2f795748ecaf1ef356657439d29ab2d2f8282ddc0cbb6d98aaa6296f1