Total 62,636 skills, Uncategorized has 2147 skills
Showing 12 of 2147 skills
Use when writing a PR body.
Pursue a long-running goal in a single session by co-ordinating subagents.
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use review-animations.
Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed. Covers sticky hover states, tap highlight flashes, the 100vh bug, inputs that zoom the page, laggy taps, pull-to-refresh hijacking scroll, content under the notch, long-press selecting button text, carousels that scroll the wrong way, mismatched status bars, and the rule that you test on real hardware. Use when a web app is being built for or reviewed on mobile, when something "works in Chrome but feels wrong on my phone", when building a PWA, a bottom sheet, a carousel, a full-screen layout, or any touch interaction. For motion itself use animate; for React Native use animate-expo.
Caveman at maximum compression: fragments, one word when one word is enough, each fact once. Invoke only with /ultracave or /caveman ultra. Stays on until "stop caveman" or "normal mode".
Caveman in Classical Chinese: 文言文 register, far fewer characters, technical terms verbatim. Invoke only with /megacave or /caveman wenyan. Stays on until "stop caveman" or "normal mode".
Build and troubleshoot Cloudflare K2 or K2 Streams durable logs. Use for stream setup, producing from Workers or HTTP, configuring retention and inputs, and consuming through subscriptions.
Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.
Designs the tier layer downstream of an existing account fit score - where the cutoffs sit, tier names, rep-to-account capacity caps, the coverage model per tier (touch cadence, channel mix, QBR frequency, executive involvement), coverage-ratio health metrics, and the recalibration cadence. Covers B2B account tiering and B2C key-account tiering through retail/distribution channels. Use whenever the user mentions tiers, strategic/key/growth/long-tail accounts, accounts-per-rep ratios, 1:1 or 1:few or 1:many ABM coverage, or "everything drifted into Tier 1", even without the word tiering. Takes the fit score as input. Do NOT use for building that score (mbfinotti/sales-skills@sales-account-segmentation).
Coach one person through landing and growing a sales career - SDR/BDR entry, SDR-to-AE promotion, and beyond - across B2B SaaS and commission-heavy B2C (real estate, insurance, solar, auto). Covers sales interview prep (mock cold call, sell-me-this-pen, candidate-authored 30-60-90 plan), quantified track-record evidence, sales skill-gap roadmaps, employer diligence, and sales offer evaluation from the candidate's seat, anchored to dated benchmarks (Bridge Group, RepVue, NAR). Use for "sales career", "break into tech sales", "sdr interview prep", "sdr to ae path", "evaluate this sales offer". Does not cover the hiring side (mbfinotti/sales-skills@sales-hiring), job searching or auto-applying, resume file generation, or deal execution tactics.
Before starting any sales project, and before answering a sales request that spans more than one sales topic or names no skill at all, run this router first. It routes the task to exactly one skill in the sales-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared sales-context.md artifact, producing a short-list plus an ordered skill chain. Fires on the state of the conversation rather than the subject matter, at a sales project start, at a periodic sales check-in or recurring sales review, on a mid-project re-route, or on any broad or ambiguous sales request such as "which sales skill do I need" or "where do I start with sales". Covers both altitudes, CRO-altitude planning (motion, ICP, market sizing, segmentation, tiering, org structure, quota, coverage, comp) and execution (outbound, cold calling, discovery, objections, MEDDPICC, recaps, call review, hiring, career). Run it even when sibling skills are already in daily use elsewhere.
Designs how sales quotas are derived for a team or company - top-down vs bottom-up reconciliation, ramp-adjusted capacity modeling (Ramped Rep Equivalents), over-assignment cushion, territory-weighted fair-share allocation, ramp relief policy, and validation against current attainment benchmarks. A macro planning exercise for VP Sales, CRO, and sales ops, covering B2B and B2C. Use whenever the user mentions quotas, targets, attainment, ramping new hires, annual planning, or "how much quota should an AE carry", even without the word quota. Do NOT use for pipeline coverage math (mbfinotti/sales-skills@sales-pipeline-coverage-modeling) or the comp plan that pays against it (mbfinotti/sales-skills@sales-comp-design).