// Extract session cookies from Chrome on macOS by decrypting Chrome's cookie database. Use when you need to authenticate API calls using the user's existing browser session — e.g., refreshing expired session cookies, accessing a service the user is logged into, or bootstrapping API access for a tool that uses cookie auth.
Detect repetitive AI defaults for a domain and generate a reusable avoidance profile. Use when asked to "unslop", "de-slop", "remove AI patterns", "make less generic", generate an anti-slop profile, or analyze AI output patterns for any domain (writing, landing pages, emails, code, etc.).
Audit and reconcile Thomas's todo list against all active data sources — calendar, email, customer deal docs, deal tracker spreadsheet, and any future sources. Use when Thomas asks to "review my todos", "what's outstanding", "todo audit", "anything I'm missing", "check my follow-ups", "what's stale", or as part of a Monday morning / Friday EOD review. Also use when he asks about overdue items, missed follow-ups, or wants a pipeline hygiene check.
Design things that AI agents can operate effectively — CLIs, tools, file formats, codebases, context layers, skills, visual assets, and any interface where agents are the primary or frequent consumer. Use when building a CLI for agents to use, structuring a codebase or repo for AI-assisted development, choosing file formats for agent-readable content, designing MCP tools or skills, creating agent-operable assets (HTML templates, markdown-driven workflows), setting up context infrastructure (AGENTS.md, SKILL.md, progressive disclosure), or making any existing system more agent-friendly. Also use when the user asks about agent DX, agent UX, or how to make something easy for agents to work with.
Process sales call recordings into structured customer intelligence. Use when the user asks to process a call transcript, create or update a deal doc, add to the playbook or glossary, or do any work involving call transcripts, deal qualification, or sales reference material.
| name | chrome-cookies |
| description | Extract session cookies from Chrome on macOS by decrypting Chrome's cookie database. Use when you need to authenticate API calls using the user's existing browser session — e.g., refreshing expired session cookies, accessing a service the user is logged into, or bootstrapping API access for a tool that uses cookie auth. |
Extract and decrypt cookies from the user's Chrome browser on macOS. No browser automation, no debug ports, no passwords needed — reads the encrypted cookie SQLite DB directly using the Chrome Safe Storage key from macOS Keychain.
Chrome stores cookies in a SQLite database (~/Library/Application Support/Google/Chrome/<Profile>/Cookies), encrypted with AES-128-CBC. The encryption key is derived from a password stored in macOS Keychain under "Chrome Safe Storage". This script reads both, decrypts, and outputs the plaintext cookie values.
cryptography package (pip install cryptography)The helper script is at the skill directory: extract.py (resolve relative to this SKILL.md).
# Extract all cookies for a domain
python3 $SKILL_DIR/extract.py --domain app.example.com
# Extract specific cookies
python3 $SKILL_DIR/extract.py --domain app.example.com --names session_id auth_token
# Output as curl cookie header
python3 $SKILL_DIR/extract.py --domain github.com --curl
# Output as env vars
python3 $SKILL_DIR/extract.py --domain app.example.com --env
# Get a single cookie value (for scripting)
python3 $SKILL_DIR/extract.py --domain app.example.com --names session_id --value
# Specify Chrome profile (default: auto-detects which profile has the cookies)
python3 $SKILL_DIR/extract.py --domain app.example.com --profile "Profile 1"
# Include subdomains (.example.com matches app.example.com, api.example.com, etc.)
python3 $SKILL_DIR/extract.py --domain example.com --include-subdomains
from extract import extract_cookies
cookies = extract_cookies(domain="app.example.com", names=["session_id", "auth_token"])
# Returns: {"session_id": "abc...", "auth_token": "xyz..."}
--profile.Chrome 145+ blocks --remote-debugging-port on the default profile for security. There is no way to connect agent-browser or any CDP tool to the user's live Chrome session with their cookies. This skill bypasses the browser entirely by reading the cookie database directly.