Claude Skills by FerroxLabs

Build a campaign brief detailed enough that creative can execute without re-asking. Captures goal, KPI, offer, audience, and timeline, infers the one specific angle that makes the campaign distinct, then produces the brief, an asset list with specs, and a per-asset creative spec. Use when the user wants a structured, multi-step process to turn a campaign goal into an executable brief plus an asset list and creative spec. Do NOT use for a single piece of copy or a one-line angle question tha...

Build a customer case study end to end: capture the brief, infer the narrative arc, draft the story, humanize it to the author's voice, then repurpose it into email, LinkedIn, and X-thread derivatives. Use when the user wants a structured multi-step process to turn a customer story or call transcript into a polished case study with derivatives. Do NOT use for a quick testimonial blurb or a single edit that one content skill can produce without the full build-and-repurpose chain.

Deterministic cashflow review over bank CSVs in an inbox. Parses actuals, optionally checks variance against a forecast, and produces a red/yellow/green status report. Use when the user wants a structured pass that turns a directory of bank CSV exports into a cashflow status report. Do NOT use when the directory is empty; halt rather than emit an empty report.

Interactive cashflow review. Parses bank actuals, computes forecast variance and a 30-day projection with red/yellow/green status, then turns it into action recommendations. Use when the user wants a structured multi-step cashflow review from raw bank data to a shipped review document. Do NOT use for a single cashflow lookup an atomic finance skill can answer.

Recommend a channel mix sized to goals and budget, with CAC math per channel and a throughput plan. Infers audience starting temperature (which dictates which channels work), surfaces viable options with CAC ranges, then a budget-optimized mix with break-even math and the creative capacity needed. Use when the user wants a structured, multi-step process to decide where to spend a marketing budget across channels with per-channel CAC economics. Do NOT use for a single-channel tactical questi...

Diagnose a weak sales close and rebuild it as a full Cascade Close (Stack to Vision to Math to Safety Net to Door, plus P.S. and P.P.S.). Use when the user has an existing close that under-converts and wants it diagnosed and rebuilt against the Three Locks and every buyer type. Do NOT use when the user needs a whole sales letter (use wayland-full-sales-asset) or only a headline (use wayland-headline-lab).

Deep competitor research that goes beyond a comp set into positioning gaps and opportunity spaces. Infers the full competitive set (direct, adjacent, status-quo, and nascent threats), profiles each, builds a 2x2 positioning map, identifies gaps, and recommends a counter-position. Use when the user wants a structured, multi-step process for thorough competitor research that ends in a positioning map and counter-positioning recommendation. Do NOT use for a quick lookup of one competitor or a ...

Scan a set of competitors, flag what changed since the last scan, and draft a brief on what is new. A fast, deterministic monitoring pass that resolves its competitor source from an attached list or a wired research source, detects deltas against a prior scan, and writes a weekly brief. Use when the user wants to run a competitor monitoring scan and get a short brief on changes since the last run. Do NOT use for first-time deep competitor research or positioning work; use the competitor dee...

Batch-process a directory of content briefs: scan the briefs, produce a blog draft for each, run a humanize pass over the batch, then build repurpose chains for email, LinkedIn, and X-thread. Use when the user has many content briefs in a folder and wants every one turned into a humanized draft with platform derivatives in a single run. Do NOT use for a single brief or when no corpus of briefs can be resolved; use the single-post blog workflow instead.

Build a 30/60/90-day content calendar mapped to funnel stages, with inferred pillar topics, a per-channel cadence, and repurpose chains for each anchor. Use when the user wants a structured multi-step process to plan a quarter of content tied to funnel stages and topic clusters. Do NOT use for a single post or a one-off idea; use this only when the user wants a full multi-week publishing plan.

Triage a contract end-to-end: identify the contract type, run a clause-by-clause risk review with severity flags, propose red-lines, and produce a counsel-routing list of clauses that require attorney sign-off before execution. Use when the user wants a structured, multi-step legal triage of a contract before signing, including red-line suggestions and an escalation list for counsel. Do NOT use for a single quick question about one clause, or as a substitute for licensed legal advice. This ...

Score existing copy 0-100 against The Donahoe Method, prioritize the rewrites, and present a revised draft. Use when the user has a piece of sales or marketing copy and wants a scored diagnosis plus a Method-aligned, Filter-cleaned revision. Do NOT use when the user wants to write copy from scratch (use wayland-full-sales-asset) or only a quick weak-line cleanup (use wayland-bullshit-clean).

Build a complete course from scratch: outline, per-module slide decks, and a workbook, with the student profile and price tier inferred up front. Use when the user wants a structured multi-step process to produce a full course package (curriculum, decks, workbook) from a single transformation statement. Do NOT use for a single lesson, a one-off slide, or a quick outline that one content skill can produce without the full course build.

Diagnose a stuck deal end-to-end: surface the real objection behind the stated one, identify the lock that is actually blocking the deal, and prescribe the specific next move with exact wording and timing. Use when the user has a single deal that has stalled and wants a structured diagnosis plus a concrete next-move prescription. Do NOT use for reviewing a whole pipeline at once (use wayland-pipeline-batch-review) or for building reusable objection responses (use wayland-objection-library-b...

Prep a tailored discovery call end-to-end: research the prospect, assess ICP fit, build a tailored call script, and surface the red flags to listen for. Use when the user has an upcoming discovery call with a specific prospect and wants a tailored script plus a disqualification checklist before the call. Do NOT use for building a cold outreach sequence (use wayland-outreach-build) or for diagnosing a deal that has already stalled (use wayland-deal-forensic).

Draft a monthly investor update: wins, metrics, lowlights, and asks. The agent gathers the period and data sources, infers the month's narrative shape (build month, breakthrough, slog, or pivot), pulls the metrics, builds the update, and iterates with the user until it ships. Use when the user wants a structured multi-step process to write a single month's investor update from their data. Do NOT use for a batch of historical updates, a one-line status note, or a question one atomic skill ca...

Build an employment agreement bundle: offer letter with at-will language, IP assignment, and restrictive covenants (non-compete / non-solicit) checked against the jurisdiction's enforceability rules, ready for counsel review. Use when the user wants a structured, multi-step process to assemble a full employment-agreement package and needs jurisdictional non-compete flags surfaced. Do NOT use for a single quick offer letter with no IP or restrictive terms, or as a substitute for licensed leg...

Convert a one-time launch into an evergreen funnel that runs on autopilot. Reshapes existing launch assets into an evergreen presentation, ethical scarcity mechanic, automated lead flow, and an evergreen email drip. Use when the user has a finished live launch (webinar replay, email sequence, sales page, cart dates) and wants a structured process to make it run continuously for every new lead. Do NOT use for designing a launch from scratch or for a single asset edit one atomic skill can han...

Build a bottom-up 12-month forecast with explicit assumption checkpoints. Builds a revenue model and an expense model, consolidates them, and produces bear/base/bull scenarios. Use when the user wants a structured multi-step process to build a 12-month financial forecast from the ground up. Do NOT use for a quick projection an atomic finance skill can answer in one step.

Full-stack direct-response funnel design. Maps entry through backend (lead-magnet, tripwire, core offer, backend continuity) with copy specs and a complete ascension ladder, validated against unit economics at every stage. Use when the user wants a structured, multi-step process to design a complete funnel architecture around an offer, from first-touch to lifetime value. Do NOT use for a single funnel stage in isolation or a question one atomic funnel skill can answer; use the dedicated sin...

Full cross-pack product launch workflow. Directs a coordinated launch across positioning, offer architecture, funnel, copy assets, content cadence, sales follow-up, ads creative, and a calendar with dependencies, ending in a post-launch debrief plan. Use when the user wants a structured, multi-step process to plan and assemble a complete launch from brief to ready-to-ship package. Do NOT use for a single asset (one email, one sales page) or a quick question that one atomic skill can answer.

Write a complete long-form direct-response sales letter end-to-end: temperature, four-layer open, three locks, body and bullets, proof, and a Cascade Close. Use when the user wants a full sales letter built from scratch using The Donahoe Method, reviewing at each major beat. Do NOT use when the user only needs an audit of existing copy (use wayland-conversion-audit), a close rebuild (use wayland-close-rebuild), or a VSL (use wayland-vsl-build).

Diagnose an existing funnel. Classifies stages, identifies likely dropoff points against the math, runs a stage-by-stage audit, and produces a prioritized fix list ranked by impact over effort. Use when the user has a live funnel and wants a structured, multi-step diagnosis that finds the leaks and recommends prioritized fixes. Do NOT use to design a new funnel from scratch or for a question one atomic audit skill can answer without the full stage-by-stage diagnosis.

Generate 5-10 ranked headline angles for an offer or page, each with Method reasoning, then refine the winner. Use when the user wants headline options for a page or asset, with the Method logic behind each angle and an interactive refine loop. Do NOT use when the user wants a full sales letter (use wayland-full-sales-asset) or a copy audit (use wayland-conversion-audit).

Build a compensation band for a role end to end: gather the role brief, research market data, recommend a min/mid/max range with rationale, then add a comp philosophy and base/equity/bonus structure recommendation. Use when the user wants a structured, multi-step process to produce a defensible comp band and memo for a specific role. Do NOT use for a single quick salary lookup or a one-line range that one atomic skill can answer.

Build an employee handbook from scratch, section by section: determine required sections from jurisdiction and stage, then draft foundational, policy, and operational sections plus an attestation, with a review checkpoint after each block. Use when the user wants a structured, long-form, multi-step process to produce a complete draft employee handbook they review as it is built. Do NOT use for a single policy paragraph or a one-section edit that one atomic skill can answer.

Build a complete hiring loop for an open role: job description, screening rubric, full interview kit, and offer-letter template, anchored to an inferred comp band, with review checkpoints between each artifact. Use when the user wants a structured, multi-step process to produce every artifact needed to run a hiring loop for one role. Do NOT use for a single job-description draft or one interview question that one atomic skill can answer.

Build a complete onboarding package for a new hire: a first-week plan, a 30/60/90-day milestone plan, and a paperwork checklist, shaped to the role and level, with review checkpoints before shipping. Use when the user wants a structured, multi-step process to produce a full onboarding package for a specific new hire. Do NOT use for a single onboarding checklist item or a one-line first-day note that one atomic skill can answer.

Run a performance review end to end: gather inputs, set a rating baseline, draft the review with specific examples per dimension, then build a development plan with goals and timelines, with review checkpoints before shipping the packet. Use when the user wants a structured, multi-step process to prep a complete performance-review packet for one employee. Do NOT use for a single piece of review feedback or one goal that one atomic skill can answer.

Build an Ideal Customer Profile from existing customer data and market signals: infer segments, pick the best-fit segment, write the full profile, and define the disqualifiers. Use when the user wants to define who their best customers are and produce a reusable ICP document with explicit disqualifiers. Do NOT use for prepping a single discovery call (use wayland-discovery-prep) or building a cold outreach sequence (use wayland-outreach-build).

Pre-launch readiness audit workflow. Builds a required-asset checklist for the launch type, runs a gap analysis with severity flags against what is already built, and produces a go/no-go recommendation with rationale. Use when the user wants a structured pre-launch audit to decide whether the launch is ready to go. Do NOT use when the user wants to build launch assets from scratch (use the full launch workflow) or has a single quick question.

During-launch daily status workflow. Pulls live launch metrics from the available data sources, flags issues against those metrics, and drafts a daily standup. Runs fast and deterministically with no required user interaction. Use during an active launch when the user wants a quick daily pull of metrics, issues, and a standup draft. Do NOT use for pre-launch planning or building assets, and never fabricate metrics when a data source is missing.

Pick one product listing from an inventory source, run a quick audit on it, and produce targeted improvement recommendations. A fast, deterministic triage pass over a catalog. Use when the user wants to surface a single weak listing from their inventory and get an immediate audit plus recommendations. Do NOT use when the user already has the specific listing in hand and just wants a deep rewrite (use the full listing-optimize workflow instead).

Audit and optimize a single product listing end to end: diagnose the conversion bottleneck, run a full audit, rewrite the listing, and produce an A/B test plan to validate the change. Use when the user wants a structured multi-step process to improve one listing's copy, structure, and conversion levers. Do NOT use for a quick catalog triage pass (use listing-audit-pick) or a single-line copy tweak.

Run the pre-open market brief: scan the watchlist with the bundled market-open-report script, render a standalone HTML brief into the deliverables directory named in the run instructions, then report its path and state plainly whether the run was complete, partial, or empty. Use when the user wants the morning report, the daily brief, or a pre-open scan of their watchlist, run unattended on a schedule or on demand. Do NOT use for reading a live TradingView chart, for intraday signals, or fo...

Draft a mutual or unilateral NDA that is jurisdiction-aware and tailored to the parties and purpose: infer the right form, recommend key terms, draft the agreement, and iterate to a counsel-ready draft. Use when the user wants a structured process to produce an NDA draft tailored to a specific counterparty, purpose, and governing law. Do NOT use for a one-line question about NDAs, or as a substitute for licensed legal advice. The output is a draft; counsel review is required before execution.

Build a reusable objection-handling library: gather and infer the objections for a niche, categorize them by the Three Locks, write a response template per objection, then produce per-buyer-type variants. Use when the user wants a durable, categorized objection library with response templates and buyer-type variants they can reuse across deals. Do NOT use for diagnosing one specific stuck deal (use wayland-deal-forensic) or building a cold outreach sequence (use wayland-outreach-build).

Guided offer build using The Donahoe Method. Works through four locks in sequence: positioning, stack, pricing, and guarantee, with expert-level reasoning the user confirms or overrides at each lock. Use when the user wants a structured, multi-step process to build or sharpen a sales offer from a single product one-liner into a complete offer document. Do NOT use for single-step copy edits or questions a single atomic skill can answer without building the full four-lock offer.

Build a cold outreach sequence: ICP-targeted, multi-touch cadence with per-touch copy and response branches for when prospects engage, ignore, or object. Use when the user wants a complete cold outreach kit: a recommended cadence, a full multi-touch sequence, and follow-up branches. Do NOT use for prepping a single discovery call (use wayland-discovery-prep) or building an ICP from scratch (use wayland-icp-build).

Friday pipeline review: resolve a pipeline data source, scan deal records to identify stuck deals past a staleness threshold, and draft quick forensics on the top three. Use when the user wants a fast batch sweep of their open pipeline to find stuck deals and get a first-pass diagnosis on the worst three. Do NOT use for a deep diagnosis of one specific deal (use wayland-deal-forensic) or for building an objection library (use wayland-objection-library-build).

Build a complete legal policy stack for a product: Terms of Service, Privacy Policy, Refund Policy + EULA, and Cookie / Acceptable Use, all aligned to the product type, jurisdictions, and compliance requirements (GDPR, CCPA, HIPAA). Use when the user wants a structured, multi-step process to produce the full set of user-facing legal policies for a product before launch. Do NOT use for a single policy in isolation, or as a substitute for licensed legal advice. Outputs are drafts; counsel rev...

Positioning sprint that ends in a defensible position statement and a per-audience messaging matrix. Infers the competitive set, maps competitors, audits the brand against that map, recommends a position (what you stand for, against, and who it is not for), then translates it into messaging per audience. Use when the user wants a structured, multi-step process to define or sharpen market positioning and produce messaging tailored to each audience segment. Do NOT use for a single tagline twe...

Build a due-diligence readiness pack for a fundraising round: anticipated DD question set, a recommended data-room folder structure, per-question response drafts, and a readiness checklist showing what is done versus what still needs gathering. The agent infers the question set for the stage and investor archetype, then structures, drafts, and checklists the responses. Use when the user wants a structured multi-step process to prepare for investor due diligence and assemble a data-room-ready...

Stress-test pricing across bear/base/bull scenarios. Covers elasticity, contribution margin, and LTV/CAC implications, ending in a recommendation memo. Use when the user wants a structured multi-step process to test a price change across scenarios before committing. Do NOT use for a single pricing question an atomic finance skill can answer.

Re-launch planning workflow. Takes a prior launch's results, infers the priority fix list, builds a structured debrief of what worked versus what did not, and produces a relaunch plan with the specific changes to make next time. Use when the user has already run a launch and wants a structured process to debrief it and plan the relaunch. Do NOT use for a first-time launch with no prior results (use the full launch workflow) or a single quick question.

Project runway across bear/base/bull scenarios with a date-of-zero per scenario and action triggers. Use when the user wants a structured multi-step process to project cash runway and set the rules for what to do as cash falls. Do NOT use for a single runway number an atomic finance skill can answer.

Launch a new SKU end to end: gather the product brief, recommend pricing and a naming approach, build the listing, then build the post-purchase thank-you page and the upsell flow, with review gates before shipping the launch package. Use when the user wants a structured multi-step process to take a new product from idea to a complete, launch-ready package. Do NOT use for editing an existing live listing or a single pricing question.

Investigate customer churn end to end: gather the brief, infer hypotheses to test, run a full investigation, synthesize a root cause, then build an action plan and ship the report. Use when the user wants a structured, multi-step process to diagnose churn root causes and produce an action plan they review as it is built. Do NOT use for a single churn-rate lookup or a one-line guess that one atomic skill can answer.

Build a self-serve knowledge-base article from a recurring support ticket: infer search intent, draft the article, then add an if-this-then-that troubleshooting tree. Use when the user wants a structured, multi-step process to turn a representative ticket and its resolution into a published-quality KB article with a troubleshooting tree. Do NOT use for a one-paragraph FAQ answer or a single edit that one atomic skill can answer.

Build a reusable support macro library from recurring ticket patterns: identify the patterns, draft reply templates with personalization slots, then organize them into a category index. Use when the user wants a structured, multi-step process to turn a sample of recurring tickets into a complete macro library with templates and a lookup index. Do NOT use for a single canned reply or one template that one atomic skill can answer.