yamz8

This skill should be used when the user asks about "crisis communication", "how to tell the team", "communicating bad news", "employee messaging", "investor communication during crisis", "board communication", "transparency in crisis", "announcing layoffs", "announcing pivot", "stakeholder communication", or needs templates and guidance for communicating during difficult situations.

This skill should be used when the user asks about "company restructuring", "organizational restructuring", "turnaround", "cost cutting", "runway extension", "burn reduction", "bridge financing", "winddown", "shutdown", "acqui-hire", "selling the company", "company sale", "M&A from sell side", or discusses major organizational changes to save or restructure the company.

This skill should be used when the user asks about "prioritization frameworks", "how to prioritize", "Eisenhower matrix", "delegation framework", "how to delegate", "decision frameworks", "how to make decisions", "first principles", "time management for founders", "CEO time allocation", "what should a CEO do", "founder productivity", or discusses managing competing priorities, choosing what to focus on, or structuring their work.

This skill should be used when the user asks about "founder burnout", "startup stress", "work-life balance for founders", "founder mental health", "sustainable pace", "how to avoid burnout", "founder exhaustion", "managing stress as CEO", "founder loneliness", "when to take breaks", or discusses feeling overwhelmed, exhausted, isolated, or questioning whether to continue.

This skill should be used when the user asks about "salary ranges", "equity grants", "compensation benchmarks", "how much to pay", "competitive offer", "market rate", "startup compensation", "equity percentages", "option grants", or mentions specific compensation questions like "what should I pay a senior engineer" or "how much equity for a VP".

This skill should be used when the user asks about "interview questions", "how to interview", "what to ask candidates", "interview process", "hiring process", "scorecard", "evaluation criteria", "behavioral interview", "technical interview", "culture fit", or discusses assessing candidates or designing interview loops.

This skill should be used when the user asks to "track metrics", "calculate ARR", "what metrics should I track", "benchmark my metrics", "understand churn", "calculate LTV", "what is burn multiple", "GMV calculation", "marketplace metrics", or mentions specific metrics like ARR, MRR, NRR, churn, CAC, LTV, burn rate, runway, GMV, take rate, or cohort analysis.

This skill should be used when the user asks to "prepare for a board meeting", "create a board deck", "draft investor update", "prepare board agenda", "calculate runway", "prepare for investor questions", or mentions board meetings, investor updates, board decks, or quarterly updates for a VC-backed startup.

Write viral X (Twitter) threads about technical projects, tools, or workflows. Use this skill whenever the user wants to post something on X/Twitter, write a thread, announce an open source project, share a technical story, or turn something they built into social media content. The skill specializes in making technical content sound genuinely human — no AI vibes, no em dashes, no template phrasing — and structures threads for maximum reach. Trigger this skill for any request involving: "write a tweet", "X post", "Twitter thread", "post about my project", "announce my repo", "viral post", "make this sound human", "thread about what I built", or similar.

Analyze medical DICOM imaging data (MRI, CT, X-ray) from any source — a CD/DVD, USB drive, or local directory. Use this skill whenever the user mentions an MRI scan, CT scan, DICOM files, a medical CD, a radiology disc, or wants to understand, view, or report on any medical imaging study. The skill handles the full pipeline: discovering the data, rendering slice images, analyzing findings across all sequences, and generating structured reports in plain or clinical language. Invoke this skill proactively if the user mentions any of: "MRI", "CT scan", "DICOM", "radiology CD", "medical scan", "shoulder MRI", "brain scan", "x-ray disc", "my doctor gave me a CD", "scan results", or similar.

Scans a git repo for hardcoded secrets, personal info, and sensitive data before it gets published. Checks both current files AND the full git commit history (because secrets in old commits are still exposed on push). Finds API keys, passwords, tokens, home directory paths with usernames, email addresses, private keys, database connection strings, and more. Reports findings by severity with exact file and line locations, and gives actionable remediation steps. Use this skill whenever the user asks to: check if a repo is safe to publish/push/open-source, scan for secrets or credentials, check for personal info, audit before making a repo public, "is this ready to push?", "anything private in here?", or similar pre-publish safety checks. Also use it proactively when the user is about to push or publish a repo and hasn't explicitly asked for a security check — it's better to catch issues early.

Create, update, or improve README files for any software project. Use this skill whenever the user asks to write a README, update an existing one, improve or fix a README, add documentation to a project, or make a repo "look good on GitHub". Also trigger for: "my README sucks", "add a README", "document my project", "README is out of date", "make my repo more discoverable", "add install instructions", "write docs for my project". The skill reads the actual codebase before writing anything, produces READMEs that match the project type, and knows the difference between a library, a CLI tool, a web app, a Claude Code skill, and a script collection.