Claude Skills by tonone-ai

Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.

Design a color palette with semantic tokens for a brand or product.

Audit existing color usage in a codebase — find inconsistencies, hardcoded values, and contrast failures.

Audit or refactor a design token system for color — naming, structure, and coverage.

Design a compromise assessment — hunting scope, methodology, and evidence collection.

Analyze indicators of compromise — enrichment, attribution, and response recommendations.

Design a threat hunting program — maturity assessment, hunting calendar, and playbook library.

Content brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal link targets, word count, CTA, and competitive gap analysis. Use when asked to "write a content brief", "brief this blog post", "plan this article", or "what should we cover for [keyword]".

Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".

Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".

Topic cluster architecture builder — takes a core topic and maps the full cluster with 1 pillar page, 6-10 supporting posts, internal linking map, keyword targets, and estimated monthly search volume per piece. Use when asked to "build a content cluster", "map our SEO cluster for [topic]", "create a topic cluster", or "what should our pillar page be about".

Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".

Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".

Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.

SEO strategy and keyword research — build topic clusters, keyword gap analysis, on-page audit, and prioritized SEO roadmap. Use when asked to "improve our SEO", "do keyword research", "build a topic cluster", or "why aren't we ranking".

Operational efficiency audit — identify waste, redundancy, and friction across processes, tools, and team workflows. Use when asked to "audit our operations for waste", "where are we inefficient", "what tools are we paying for but not using", or "reduce operational overhead".

Design meeting and communication cadence — what meetings to run, how often, who attends, and what decisions they make. Use when asked to "design our meeting structure", "what meetings should we have", "reduce meeting load", or "build our operating rhythm".

Build or audit compliance program — SOC2, GDPR, HIPAA, or ISO 27001 readiness assessment, gap analysis, and remediation roadmap. Use when asked to "do we need SOC2", "are we GDPR compliant", "what does our compliance program need", or "build a security policy".

Draft or review legal ops documents — NDA, MSA, SaaS agreement review checklist, vendor contract terms. Use when asked to "review this contract", "draft an NDA", "what should I look for in this agreement", or "build our contract review process".

Design and run OKR program — company objectives, team key results, cascade design, and quarterly review cadence. Use when asked to "design our OKRs", "are our OKRs good", "cascade goals to teams", or "run a quarterly OKR review".

Document or redesign a business process — standard operating procedure (SOP), process map, RACI, and owner assignment. Use when asked to "document this process", "write a runbook", "design how we handle X", or "map the process for Y".

Operations reconnaissance — audit process documentation, vendor contracts, compliance posture, OKR health, and cross-functional friction points to understand where operations is the bottleneck. Use when asked to "audit our operations", "where are we slow", "what processes are broken", or "before designing a compliance program".

Manage vendor relationships — vendor selection scorecard, contract review checklist, renewal tracking, and vendor consolidation audit. Use when asked to "evaluate this vendor", "review this contract", "track vendor renewals", or "reduce our SaaS spend".

Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".

Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".

Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".

Optimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".

Write churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to "prevent churn", "save at-risk customers", "win back churned customers", or "build a save play".

Quarterly Business Review template generator — takes account info (ARR tier, adoption metrics, goals) and produces a complete QBR deck outline and talking points. Use when asked to "prepare a QBR", "build a quarterly review", "write our QBR agenda", or "create QBR talking points for this account".

Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.

Customer segmentation model builder — tiers customers by ARR, health, and expansion potential; defines CS motion per tier; maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", "build a customer segmentation model", or "who gets high-touch vs. digital".

Design a Kubernetes cluster architecture — node pools, RBAC, networking, and workload config.

Design or audit Kubernetes RBAC — roles, bindings, service accounts, and least-privilege model.

Audit an existing Kubernetes cluster — find misconfigurations, security gaps, and resource issues.

Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".

Use when asked to select chart types for analytics dashboards, choose BI visualizations, or design data displays. Examples: "best chart for sales data", "dashboard visualization for metrics", "analytics chart selection"

Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".

Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".

Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".

Build a reporting pipeline — scheduled reports with SQL queries, delivery via Slack or email, threshold alerts, and historical comparison. Use when asked for "automated reports", "scheduled report", "email digest", or "Slack alerts for metrics".

Draft DMCA takedown notice or counter-notice.

Prepare a regulatory filing, disclosure notice, or government submission.

Survey pending and required regulatory filings.

A/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".

Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".

Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".

Metrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".

Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.