All authors
Claude Skills by tonone-ai
github.com/tonone-ai918 skills5 installs963 views
- Crest RoadmapBuild a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".Votes: 0GitHub stars: 71
- CrestProduct strategist — roadmaps, competitive analysis, OKRs, strategic narratives. Use when asked to "build a roadmap", "analyze competitors", "write a strategy memo", "prioritize features", or "set OKRs".Votes: 0GitHub stars: 71
- Cut IconDesign an icon system spec or audit existing icons for consistency and accessibility. Use when asked to "design an icon system", "audit our icons", or "are our icons consistent".Votes: 0GitHub stars: 71
- Cut IllustrateSpec or critique custom illustrations — style, composition, and brand alignment. Use when asked to "spec an illustration", "critique this illustration", or "define an illustration style".Votes: 0GitHub stars: 71
- Cut ReconAudit existing icons and illustrations in a codebase — find inconsistencies, unoptimized SVGs, and accessibility gaps. Use when asked to "audit our icons and illustrations", "find unoptimized SVGs", or "find inconsistent assets".Votes: 0GitHub stars: 71
- Deal CloseClose a specific deal — diagnose why a deal is stalling, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", or "help me get to yes".Votes: 0GitHub stars: 71
- Deal OutreachCold outbound sequence builder — produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign".Votes: 0GitHub stars: 71
- Deal PipelineDesign or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".Votes: 0GitHub stars: 71
- Deal PlaybookWrite sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".Votes: 0GitHub stars: 71
- Deal PricingDesign pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".Votes: 0GitHub stars: 71
- Deal ProposalB2B proposal generator — takes deal context (ICP, pain, pricing tier, timeline) and produces a complete proposal document with executive summary, problem statement, solution, pricing table, implementation timeline, ROI case, and next steps. Use when asked to "write a proposal", "draft our deck for this deal", "build a proposal for this customer", or "generate a proposal".Votes: 0GitHub stars: 71
- Deal QualifyMEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".Votes: 0GitHub stars: 71
- Deal ReconRevenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".Votes: 0GitHub stars: 71
- DealRevenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing. Use when asked to "price this deal", "build a sales playbook", "close an enterprise deal", or "manage the B2B pipeline".Votes: 0GitHub stars: 71
- Deploy CanaryPlan and execute canary releases for model updates — traffic splitting, rollback triggers, success metrics. Use when asked to "canary the new model", "roll out this model safely", or "set up a traffic split for a model update".Votes: 0GitHub stars: 71
- Deploy ReconAudit current model deployment topology — serving config, latency profile, version inventory. Use when asked "what models are deployed", "audit our serving setup", or "inventory our model versions".Votes: 0GitHub stars: 71
- Deploy ServeDesign and configure model serving infrastructure — endpoint scaling, batching, GPU allocation. Use when asked to "serve this model", "design an inference endpoint", or "size GPU allocation for serving".Votes: 0GitHub stars: 71
- Draft FlowUse when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".Votes: 0GitHub stars: 71
- Draft IaInformation architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".Votes: 0GitHub stars: 71
- Draft LandingUse when asked to structure a landing page, design page layout for conversion, or plan landing page information architecture. Examples: "landing page structure for SaaS", "conversion-optimized layout"Votes: 0GitHub stars: 71
- Draft PatternsUse when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX"Votes: 0GitHub stars: 71
- Draft ReconUI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.Votes: 0GitHub stars: 71
- Draft ReviewUsability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".Votes: 0GitHub stars: 71
- Draft WireframeWireframe a screen — text/ASCII by default, or hand-drawn HTML when the user says "sketch", "hand-drawn", "lo-fi HTML", "whiteboard", "graph paper", or "visual wireframe". Text mode produces a buildable ASCII spec Form and Prism can act on. HTML mode produces a single self-contained file with graph-paper background, marker headlines, sticky-note annotations, and hatched chart placeholders — looks like a designer's whiteboard, commits to nothing.Votes: 0GitHub stars: 71
- DraftUX designer — user flows, information architecture, wireframes, and interaction design. Use when asked to "design a user flow", "map the IA", "wireframe this screen", or "review UX before shipping".Votes: 0GitHub stars: 71
- Drift AlertDesign drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".Votes: 0GitHub stars: 71
- Drift MonitorDesign a drift monitoring system for a production ML model. Use when asked to "monitor this model in production", "detect data drift", or "set up ML monitoring".Votes: 0GitHub stars: 71
- Drift ReconAudit existing ML monitoring — find gaps in drift coverage and missing alerts. Use when asked to "audit our ML monitoring", "are our models monitored", or "find drift coverage gaps".Votes: 0GitHub stars: 71
- Echo FeedbackFeedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".Votes: 0GitHub stars: 71
- Echo InterviewRun a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".Votes: 0GitHub stars: 71
- Echo JobsJobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".Votes: 0GitHub stars: 71
- Echo ReconUser research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.Votes: 0GitHub stars: 71
- Echo SegmentUser segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".Votes: 0GitHub stars: 71
- EchoUser researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis. Use when asked to "run user interviews", "build personas", "synthesize feedback", or "find the job-to-be-done".Votes: 0GitHub stars: 71
- Edge CdnDesign a CDN configuration — caching rules, TTLs, and origin shield setup. Use when asked to "configure the CDN", "set cache headers", or "set up an origin shield".Votes: 0GitHub stars: 71
- Edge ReconAudit existing CDN and edge configuration — find cache misses, missing headers, and performance gaps. Use when asked to "audit our CDN", "why is our cache hit rate low", or "find edge config gaps".Votes: 0GitHub stars: 71
- Edge RouteDesign an edge routing and geo-distribution strategy — latency routing, failover, and edge logic. Use when asked to "geo-route our traffic", "reduce global latency", or "design edge failover".Votes: 0GitHub stars: 71
- Embed DesignDesign embedding pipelines — model selection, batching, normalization, index refresh strategy. Use when asked to "design an embedding pipeline", "which embedding model should we use", or "how should we batch embeddings".Votes: 0GitHub stars: 71
- Embed ReconAudit embedding infrastructure — model drift, index freshness, query latency, coverage gaps. Use when asked to "audit our embeddings", "is our index stale", or "find embedding coverage gaps".Votes: 0GitHub stars: 71
- Embed SearchOptimize similarity search — ANN index tuning, hybrid search, reranking, query expansion. Use when asked to "improve similarity search", "tune the ANN index", or "add hybrid search".Votes: 0GitHub stars: 71
- Eval AnalyzeAnalyze A/B test results — statistical significance, practical significance, and segmentation. Use when asked to "analyze our A/B test", "is this result significant", or "read these experiment results".Votes: 0GitHub stars: 71
- Eval DesignDesign an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".Votes: 0GitHub stars: 71
- Eval ReconAudit existing experimentation infrastructure and past experiments for methodology issues. Use when asked to "audit our experiments", "is our experimentation sound", or "review past test methodology".Votes: 0GitHub stars: 71
- Evals AnalyzeAnalyze LLM eval results — score breakdowns by category, regression detection vs baseline, failure clustering. Use when asked to "analyze our eval results", "did the model regress", or "cluster the eval failures".Votes: 0GitHub stars: 71
- Evals DesignDesign an LLM eval — task schema, scoring rubric, dataset composition, and pass/fail thresholds. Use when asked to "design an LLM eval", "write a scoring rubric", or "how do we measure this model".Votes: 0GitHub stars: 71
- Evals HarnessDesign eval harnesses — task schemas, metrics, dataset versioning, eval-as-code patterns. Use when asked to "build an eval harness", "set up eval-as-code", or "version our eval datasets".Votes: 0GitHub stars: 71
- Evals ReconAudit existing eval coverage — gaps, metric validity, benchmark leakage, dataset freshness. Use when asked "what eval coverage do we have", "audit our evals", or "check for benchmark leakage".Votes: 0GitHub stars: 71
- Evals RegressBuild automated regression suites — golden sets, threshold alerting, CI integration for model changes. Use when asked to "catch model regressions in CI", "build a golden set", or "automate eval regression".Votes: 0GitHub stars: 71
- Feat EngineerDesign and implement a feature engineering pipeline for a ML problem. Use when asked to "engineer features for this model", "what features should we build", or "design feature transformations".Votes: 0GitHub stars: 71
- Feat ReconAudit feature engineering code for leakage, quality issues, and pipeline correctness. Use when asked to "audit our feature pipeline", "is there data leakage", or "find feature quality issues".Votes: 0GitHub stars: 71