Claude Skills by manusco

Hiring and People Specialist. Runs a founder's hire end to end with structured, evidence-based rigor: outcome scorecards, interview loops, bias-controlled debriefs, offers, comp bands, and onboarding. Use when defining a role, writing a job description or scorecard, designing an interview loop, evaluating candidates, checking references, setting comp bands, making an offer, or planning a new hire's first 90 days.

Conducts SaaS and B2B market research to identify Existential Data Points (EDPs) that transform solutions from nice-to-have to must-have. Use when asked to research a B2B SaaS vertical, identify industry pains, or discover urgency metrics for outreach.

Identifies which accounts deserve attention now, why, and what action to take next. Covers signal detection, account scoring, brief generation, and customer-facing deck construction. Use when asked to prioritize accounts, build account briefs, prepare customer decks, or audit account expansion potential.

Analyzes sales call transcripts to extract deep persona insights, objection handling metrics, vocabulary libraries, and feature requests. Use when asked to audit discovery calls, extract insights from meeting recordings, or compile prospect feedback.

Generates a structured B2B cold call script using a disarming, permission-based 6-part framework. Use when asked to write a cold call script, how to open a call, how to handle phone objections, or to plan a cold calling sales outbound campaign.

Audits lead lifecycle quality, resolves ownership, maps the customer experience from form fill to follow-up, and generates daily watchlists. Use when asked to audit lead handling, find missed follow-ups, resolve lead owners, map inbound CX, or build a daily lead operating view.

Builds source-backed outbound sequences from CRM data, trigger signals, and campaign context. Use when asked to draft a sales sequence, plan outbound cadences, create follow-up copy, or build event/signal-based outreach.

Sales pipeline analyst. Ingests deal data from CSV, HubSpot, or Salesforce and produces deal-level pipeline inspection, velocity, forecast views, and rep performance analysis. Use when the immediate job is to understand the current pipeline. RevOps owns durable funnel definitions, coverage policy, capacity, territories, quotas, compensation, and forecast governance.

Revenue Operations system owner. Defines funnel stages and exit criteria, coverage policy, sales capacity, territories, quotas, compensation, forecast governance, and deal-desk rules. Use when the durable revenue operating system must be designed or changed. Pipeline owns deal-level ingestion, dashboards, velocity analysis, and a current forecast view.

Sales revenue-motion conductor. Use when a user wants prospecting, account intelligence, outbound sequence, call preparation, CRM hygiene, pipeline review, forecast, and customer-success handoff governed as one revenue motion.

Compatibility entrypoint for end-to-end software delivery. Use when the user explicitly invokes the software delivery skill or an existing workflow targets its skill ID. Confirms software scope, separates unrelated work, then delegates once to resonance-ops-goal, which owns the goal contract, bounded execution, evidence, review, and ship proposal. Do not select this instead of /goal for a new outcome request.

System Architect Specialist. Defines whole-system topology, service contracts, trust zones, data ownership, and durable architecture through C4 models, ADRs, domain maps, and failure registries. Use when work changes system boundaries or cross-system behavior. AI subsystem internals, prompts, retrieval, model routing, and AI evals belong to AI Engineering.

Creates, revises, and checks a project-owned architecture blueprint that defines durable principles, system boundaries, ownership, safe evolution, and controlled exceptions. Use when establishing an architecture constitution, auditing a brownfield system against first principles, planning evolutionary migration, or checking a plan, change, PR, or release for architectural drift.

Turns a rough or overloaded request into a faithful execution brief, then executes a bounded request or routes it when authorized. Use for `/brief`, prompt strengthening, or material ambiguity in a multi-step ask. It preserves intent and labels explicit, inferred, and unresolved content. Grill interrogates a proposed plan. Plan authors the implementation plan. Goal owns autonomous outcome-to-finish execution. Council challenges a completed artifact.

Decision council for challenging a completed analysis, recommendation, or plan, and for reviewing a consequential choice at a high-risk checkpoint. Selects relevant specialist subagents, gathers blind opening positions, runs one rebuttal round and scenario tests, then reconciles evidence into an advisory decision memo. Use when the user asks for a council, expert panel, multidisciplinary challenge, blind-spot review, or high-stakes deliberation. Does not replace /brief, /grill, /plan, /audit,...

Finance and Fundraising Specialist. Builds driver-based financial models, computes unit economics, and prepares founders to raise. Use when modeling revenue, costs, or runway; computing unit economics (CAC, LTV, payback, contribution margin); preparing a fundraise or pitch deck; writing an investor update; or working through cap table and dilution basics.

The pre-build interrogation gate. Stress-tests a plan, design, or goal contract through one-question-at-a-time questioning and targeted risk passes before any code is written, so hidden assumptions surface while they are still cheap to fix. Use before starting a feature, refactor, migration, new project, or when the user says grill me, pressure-test this, poke holes, or challenge this idea. Reaches explicit shared understanding and gates implementation until the user confirms.

Growth Strategist Specialist. Diagnoses growth bottlenecks, sets channel portfolio strategy, and prioritizes experiments across acquisition, activation, retention, referral, and revenue. Use when analyzing AARRR metrics, designing growth loops, choosing launch or channel investment priorities, or diagnosing churn. GTM Thinker challenges one uncommitted hypothesis. Run Campaign prepares an accepted campaign.

GTM hypothesis challenger. Use when a concrete B2B positioning, audience, offer, channel, or campaign concept has not earned commitment. Deconstructs the bet, tests assumptions, compares alternatives, and defines evidence and kill criteria. Growth owns company-wide bottleneck and channel portfolio choices. Run Campaign owns approved campaign preparation.

Implementation-plan author. Turns a confirmed feature, refactor, or architecture goal into an atomic, dependency-aware, verifiable plan using earned research, product, and architecture input. Use when the intended outcome is clear but the implementation sequence is not. It produces the approved plan artifact but does not build it. Brief clarifies an unclear ask, Grill interrogates a proposed plan, and Goal drives an accepted outcome through execution.

Research Specialist. Gathers, verifies, compares, and synthesizes uncertain evidence before building or deciding. Use for technical investigations, option comparisons, contradictions, and non-durable research reports. Do not use for canonical project documentation, Diataxis placement, indexes, supersession, or archival; hand finalized evidence to Librarian.

Venture Validator Specialist. Prevents waste by validating business ideas before building. Use when evaluating a new idea, defining kill criteria, running assumption tests, modeling a Lean Canvas, or deciding whether to pivot or persevere after a customer test.

Customer Success Architect for named post-sale customer relationships. Owns onboarding delivery, account health, QBRs, renewals, expansion, escalations, and the human operating motion behind NRR and GRR. Use when account-level ownership or intervention is required. Lifecycle owns scalable product moments and triggered messaging. Growth owns the cross-funnel portfolio.

Run the Resonance **audit** procedure. Read `.agents/skills/ops/audit/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /audit command to it.

Run the Resonance **blueprint** procedure. Read `.agents/skills/strategy/blueprint/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /blueprint command to it.

Run the Resonance **brief** procedure. Read `.agents/skills/strategy/brief/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /brief command to it.

Run the Resonance **build** procedure. Read `.agents/skills/engineering/build/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /build command to it.

Run the Resonance **call-intelligence** procedure. Read `.agents/skills/sales/call-intelligence/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /call-intelligence command to it.

Run the Resonance **capture** procedure. Read `.agents/skills/ops/librarian/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /capture command to it.

Run the Resonance **cold-call** procedure. Read `.agents/skills/sales/cold-call/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /cold-call command to it.

Run the Resonance **council** procedure. Read `.agents/skills/strategy/council/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /council command to it.

Run the Resonance **debug** procedure. Read `.agents/skills/engineering/debugger/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /debug command to it.

Run the Resonance **design** procedure. Read `.agents/skills/design/designer/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /design command to it.

Run the Resonance **explain** procedure. Read `.agents/skills/ops/explain/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /explain command to it.

Run the Resonance **friction** procedure. Read `.agents/skills/marketing/conversion/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /friction command to it.

Run the Resonance **goal** procedure. Read `.agents/skills/ops/goal/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /goal command to it.

Run the Resonance **grill** procedure. Read `.agents/skills/strategy/grill/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /grill command to it.

Run the Resonance **gtm-thinker** procedure. Read `.agents/skills/strategy/gtm-thinker/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /gtm-thinker command to it.

Run the Resonance **handover** procedure. Read `.agents/skills/ops/handover/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /handover command to it.

Run the Resonance **improve** procedure. Read `.agents/skills/ops/improve/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /improve command to it.

Run the Resonance **incident** procedure. Read `.agents/skills/ops/incident/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /incident command to it.

Run the Resonance **init** procedure. Read `.agents/skills/ops/core/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /init command to it.

Run the Resonance **market-research** procedure. Read `.agents/skills/research/market-research/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /market-research command to it.

Run the Resonance **page-audit** procedure. Read `.agents/skills/ops/page-audit/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /page-audit command to it.

Run the Resonance **plan** procedure. Read `.agents/skills/strategy/plan/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /plan command to it.

Run the Resonance **refactor** procedure. Read `.agents/skills/ops/refactor/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /refactor command to it.

Run the Resonance **retro** procedure. Read `.agents/skills/ops/retro/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /retro command to it.

Run the Resonance **review-pr** procedure. Read `.agents/skills/ops/reviewer/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /review-pr command to it.

Run the Resonance **sales-pipeline** procedure. Read `.agents/skills/sales/pipeline/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /sales-pipeline command to it.

Run the Resonance **search-cycle** procedure. Read `.agents/skills/marketing/run-search-operating-cycle/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /search-cycle command to it.