How do I install the Resonance Sales Run Revenue Motion skill?

Run npx skillmds@latest add manusco/resonance-sales-run-revenue-motion in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Resonance Sales Run Revenue Motion safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Resonance Sales Run Revenue Motion?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Resonance Sales Run Revenue Motion free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Resonance Sales Run Revenue Motion?

manusco (@manusco) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Resonance Sales Run Revenue Motion by manusco

Name: Resonance Sales Run Revenue Motion
Author: manusco

Resonance Sales Run Revenue Motion

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.

manusco Updated Sep 17, 2026

File contents

resonance-sales-run-revenue-motion: govern the path from target account to handoff

Role: revenue-motion conductor. Input: target accounts, ICP, territory, quota goal, campaign request, or pipeline problem. Output: account plan, outreach sequence, call plan, CRM mutation proposal, forecast, and handoff notes. Definition of Done: The motion names the buyer, jurisdiction, contact basis, buyer action, CRM source of truth, forecast method, next step, and handoff owner. No outreach or CRM mutation occurs without approval.

Pipeline

Scope: define ICP, segment, territory, jurisdiction, CRM source, goal, and send authority. -> gate: no unknown recipient basis.
Account intelligence: invoke resonance-sales-account-intelligence and resonance-sales-lead-ops. -> gate: target list has provenance and confidence.
Compliance: invoke resonance-ops-legal when outreach rules, privacy, recording, or regulated claims are relevant. -> gate: no risky send path is treated as safe by default.
Sequence and call: invoke outbound-sequence and call-intelligence for message and conversation assets. -> gate: claims, objections, and buyer action are explicit.
Pipeline and RevOps: invoke pipeline and revops for stages, hygiene, forecast, and owner actions. -> gate: forecast uses observed conversion or is labeled unweighted or assumption-based.
Handoff: invoke customer-success when the motion touches expansion, renewal, onboarding, or post-sale risk.
Approval: present exact sends, CRM mutations, and follow-up actions for human consent.

Recovery

Contact provenance is missing -> stop or downgrade to research-only.
CRM mutation is ambiguous -> draft the change, do not execute it.
Forecast probabilities are unobserved -> label them assumptions or use an unweighted view.

Operating Standard

Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory; when .resonance/ledger/ exists it is the system of record for decisions, lessons, metrics, customers, and experiments, while 02_memory.md keeps [lib] notes and pointers).

Execution note: Use the host's native file, search, shell, browser, and delegation tools. Follow the procedure and verify material claims with evidence. Keep internal reasoning private and report decisions, actions, and results clearly.

---name: resonance-sales-run-revenue-motiondescription: 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.---# resonance-sales-run-revenue-motion: govern the path from target account to handoff> **Role:** revenue-motion conductor.> **Input:** target accounts, ICP, territory, quota goal, campaign request, or pipeline problem.> **Output:** account plan, outreach sequence, call plan, CRM mutation proposal, forecast, and handoff notes.> **Definition of Done:** The motion names the buyer, jurisdiction, contact basis, buyer action, CRM source of truth, forecast method, next step, and handoff owner. No outreach or CRM mutation occurs without approval.## Pipeline1. **Scope:** define ICP, segment, territory, jurisdiction, CRM source, goal, and send authority. -> gate: no unknown recipient basis.2. **Account intelligence:** invoke `resonance-sales-account-intelligence` and `resonance-sales-lead-ops`. -> gate: target list has provenance and confidence.3. **Compliance:** invoke `resonance-ops-legal` when outreach rules, privacy, recording, or regulated claims are relevant. -> gate: no risky send path is treated as safe by default.4. **Sequence and call:** invoke outbound-sequence and call-intelligence for message and conversation assets. -> gate: claims, objections, and buyer action are explicit.5. **Pipeline and RevOps:** invoke pipeline and revops for stages, hygiene, forecast, and owner actions. -> gate: forecast uses observed conversion or is labeled unweighted or assumption-based.6. **Handoff:** invoke customer-success when the motion touches expansion, renewal, onboarding, or post-sale risk.7. **Approval:** present exact sends, CRM mutations, and follow-up actions for human consent.## Recovery- Contact provenance is missing -> stop or downgrade to research-only.- CRM mutation is ambiguous -> draft the change, do not execute it.- Forecast probabilities are unobserved -> label them assumptions or use an unweighted view.## Operating StandardApply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory; when `.resonance/ledger/` exists it is the system of record for decisions, lessons, metrics, customers, and experiments, while `02_memory.md` keeps `[lib]` notes and pointers).> **Execution note:** Use the host's native file, search, shell, browser, and delegation tools. Follow the procedure and verify material claims with evidence. Keep internal reasoning private and report decisions, actions, and results clearly.

Frequently asked questions