Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkills › Authors › wastedcode › Page 3

wastedcode

@wastedcode on GitHub →

166 Claude Code skills authored by wastedcode.

updated 2026-11-15 · showing 121–166 of 166 by quality score

Average Pro QualityScore: 65.3/100

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

Use when the question is "how do we reach buyers at all?" — distribution / go-to-market strategy. Run the Bullseye (brainstorm → cheap-test a few → focus the ONE that works) and…
Use whenever a surface will be seen on more than one screen size or input — which is almost always (62%+ of web traffic is mobile).
Use the moment prod is broken/degraded or an alert fires — declare an incident, take command, mitigate before diagnosing, and communicate on a cadence.
Use at the end of an evaluation — would this pitch still be on your mind at dinner, or does it blur into the other AI/SaaS pitches? Name the one compounding idea, and the single…
Use when surfacing findings — lead with the unmet need and what to do about it, ranked by confidence; never dump a transcript or a deck. The output is a decision, not data.
Use when code does anything cryptographic — hashing passwords, encrypting data, signing tokens, generating randomness — catch the common crypto misuse and never let anyone roll…
Use when you have findings to report — grade each by real-world risk (P0–P3) with a specific minimal remediation, block only real exploitable harm, and name accepted risk out loud.
Use when a build is proposed with no path to reach users — force distribution (channel + activation + retention loop) into the product decision.
Use before you run anything — statically walk every user journey end-to-end (happy path plus the error, empty, returning-user, and cancel states) by reading flow + spec + code, to…
Use before writing any copy, when copy sounds like the team talking to itself, or when you need the raw language for headlines and messaging.
Use before calling any design done, and for anything with concurrency, persistence, or external dependencies — risk-storm the design: attack it, then decide resilient vs fail-fast…
Use whenever the system spawns processes, sessions, jobs, workers, or connections (background daemons, tmux/PTY sessions, worker pools, cron jobs, subprocesses) — model the full…
Use when evaluating the core insight or differentiation — test whether the "secret" is earned or faked.
Use to turn a raw transcript/doc into structured knowledge — break it into nuggets (one observation + its receipt + a tag), then build themes UP from the codes; never a wall of…
Use in a crowded/competitive space, when prospects keep comparing you to a rival, when "why you over X?" has no crisp answer, or to build battlecards.
Use when deciding whether a deal is real and worth your effort, or what's missing to win it — qualify with MEDDPICC (Metrics, Economic Buyer, Decision criteria/process, Paper…
Use when a verdict rests on a measured quantity rather than a single deterministic assertion — a noisy/probabilistic output, a performance number, an accuracy or conversion rate.
Use when the build implies quality beyond "it works" — sweep the non-functional surface: performance under load, accessibility, the obvious security holes, and…
Use when handing an initiative or a chunk of work to the engineer — produce a brief with C4-level structure, the exact contract, acceptance, file/seam pointers, illustrative code,…
Use when consulted EARLY on a design or proposal (before the build) — say plainly what it would take to ship this safely while it's still cheap to change, and escalate…
Use when AI is in the loop — generating copy/variants at scale, personalizing messaging, or summarizing customer calls/competitive intel, and as the anti-AI-tell scrub on any…
Use first, before any copy — when positioning is unwritten, vague, aspirational, or being re-improvised per artifact.
Use when price, discount, or terms come up at the deal's end — hold value, trade don't give (every concession buys something back), use tactical empathy and calibrated questions.
Use before building on or committing to a vendor/runtime (cloud, PaaS, serverless, queue, DB, third-party API) — read the actual pricing, runtime-limits, and execution-model docs…
Use when filing a finding — write the bug report as a persuasive document that gets it fixed (Kaner's bug advocacy): exact repro, expected vs actual, severity, and the expectation…
Use to sequence your work on a change — make it work, then make it right, then make it fast, in that order; keep one concern per change; don't tangle a feature with a refactor.
Use before any account, call, or outreach — research the buyer from THEIR side (their world, what they use today + what it costs, the trigger event, who pays vs.
Use when running a founder meeting or generating the questions you'd ask — the texture of the conversation, not a diligence checklist.
Use when assessing defensibility and timing — why won't the incumbent (or a well-funded lab) just do this, and what's the durable moat once the easy parts commoditize.
Use when a load-bearing fact is unknown — ask the founder the few questions you cannot responsibly default; propose defaults for the reversible ones; fill placeholders, never…
Use when reporting status or accepting work — keep the board honest (in-progress only if truly in progress, done only if verified done) and CHECK the definition of done against…
Use to decide where to spend a finite testing budget — prioritize by risk (likelihood × impact), hammering data loss, auth, the core flow, and money first, and right-size the…
Use when scoping or describing a feature — reframe it as the job the user is hiring it for (the outcome in their words), not the feature itself.
Use when entering a codebase, before any design or estimate, or when your mental model has gone stale — read width AND depth and refresh the C4-level picture; a design from a skim…
Use whenever sources disagree — record the contradicting evidence as its own signal against the belief, never average a real disagreement into false consensus.
Use before gathering — pick the method by the question (attitudinal vs behavioral, qual vs quant), match the source to what you need to learn, and right-size the rigor to the…
Use mid-cycle on any multi-stakeholder deal — map the buying committee, multi-thread across it, develop a real champion (power + self-interest), TEST them, and reach the economic…
Use when making the actual call — a clear invest / pass with conviction, the single risk you'd underwrite, and the coaching you'd give either way.
Use when a new field, surface, boundary, or piece of state is introduced — map every hop from user input to persisted state to read-back, find where data can silently drop, and…
Use before writing or changing any non-trivial code, especially in an unfamiliar codebase — understand the problem, the brief, and the surrounding code first; never start typing…
Use before calling your own change done, and when reviewing someone else's PR — review against scope, conventions, and what could break; be useful and specific, not a nitpick gate.
Use when reviewing config, env handling, CI/CD, logging, or anything that touches credentials — secrets never in repo or logs, short-lived and least-scope, with insecure defaults…
Use when deciding what to say where — a cold ad vs. a homepage vs. a pricing page vs. a re-engagement email — or when copy is pitching the offer to people who don't yet know they…
Use when designing a module/function/API or when tempted to add abstraction "for the future" — reduce complexity; build deep modules with simple interfaces; the simplest thing…
Use when forecasting, reviewing pipeline, or reporting deal status — enforce stage exit criteria, honest forecast categories, and kill zombie deals.
Use throughout gathering and synthesis — name the biases that distort findings (sampling, leading, sponsor, social-desirability, confirmation, your own priors) and design and…
Search all 166 skills by wastedcode →