Run any Skill in Manus with one click

consulting-followup-sequencer

Stars1

Forks0

UpdatedJuly 5, 2026 at 15:33

Generate the timed follow-up cadence for a deal, personalized to the client's stated stakes. Use after a call or proposal, on "draft follow-ups", "they went quiet", "what do I send next".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sidneyswift

sidneyswift/consulting-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	consulting-followup-sequencer
description	Generate the timed follow-up cadence for a deal, personalized to the client's stated stakes. Use after a call or proposal, on "draft follow-ups", "they went quiet", "what do I send next".

Consulting Follow-Up Sequencer

Voice + gate: write in consulting-copy-writer voice, then run every draft through consulting-outbound-email (read context, route, reader-POV check) before staging.

Steps

Pull the deal's specifics: the outcome discussed, the stakes in their words, the next-meeting date.
Fill the templates in library/email-templates/:
- Same-day thank-you
- 24h value-add (attach a relevant resource/case study)
- Proposal delivery (within 48h, suggest a Loom)
If silent, generate the Day 5 / 10 / 15 sequence (max 3 touches), each referencing their stakes, not your proposal.
Stage in Gmail (optional). Offer to drop each touch into Gmail as a draft via integrations/gmail/_work/create_draft.py --to <addr> --subject "..." --body-file <file> (creates a draft; only sends with --send + a typed confirmation). Save drafts next to the deal (e.g. pipeline/01-leads/<deal>/followups.md).
Offer to set reminders / a scheduled task for the cadence.

Output: ready-to-send emails (optionally staged as Gmail drafts). Source: Ch. 14 (48-Hour Rule + follow-up sequence).

More from this repository

same repository

consulting-content-recycler

sidneyswift/consulting-plugin

Squeeze every published winner — repost proven posts with a fresh hook, re-share your own winners with added context, and fan one outlier post into multiple new formats. Use on "what should I repost", "recycle my winners", "this post popped, what now", "turn this outlier into more posts", "wring the towel", after an engagement pull shows a post outperforming baseline, or on the Friday review's recycle step. Reads published bundles + engagement data; stages new drafts; never auto-posts.

2026-07-091

consulting-friday-review

sidneyswift/consulting-plugin

The weekly content + system review ritual. Use on "run the Friday review", weekly cadence, or "what should I write this week". Good candidate to wire as a scheduled task.

2026-07-091

consulting-linkedin-hooks

sidneyswift/consulting-plugin

Write or critique the first line of a LinkedIn post (the hook) using patterns reverse-engineered from real top-performing posts. Use on "write hooks for this", "give me 10 hooks", "fix this hook", "why won't this hook land", "what's a scroll-stopping opener", or whenever drafting/critiquing a post's line 1. This is the dedicated hook engine; consulting-linkedin-post-architect handles whole-post structure and defers here for the hook; consulting-copy-writer governs voice/anti-slop.

2026-07-091

consulting-linkedin-post-architect

sidneyswift/consulting-plugin

Structure a high-performing LinkedIn post — pick the archetype and founder format (build log, documented failure, value post, receipt, contrast hook, milestone chapter), write a scroll-stopping hook, shape the body, format for mobile, choose the in-post CTA, and decide whether to pair an infographic. Use on "write a LinkedIn post", "make this post perform/go viral", "what hook should I use", "structure this for LinkedIn", "turn this insight into a LinkedIn post", "write a build log / failure / receipt / milestone post", or right after consulting-content-drafter. This is the post-STRUCTURE layer; consulting-copy-writer still governs voice/anti-slop, consulting-linkedin-publisher ships it.

2026-07-091

consulting-content-distribution

sidneyswift/consulting-plugin

Distribute one finished pillar article across every channel the same way — republish the same copy to the owned blog + LinkedIn newsletter + X (as an article, never a thread), ship the always-on companions (a LinkedIn promo post + an email to the list), point every link at the owned canonical URL, then find the live post and monitor its engagement into leads. Use after an article is written or published, on "distribute this", "post it everywhere", "atomize this article", "where else should this go", or when promoting a piece in content/04-published/.

2026-07-051

consulting-copy-editor

sidneyswift/consulting-plugin

Editorial copy-edit pass on a finished draft, run through a fresh-context subagent reviewer. Use on "copy-edit this", "edit this article", "do an editor pass", "give it a hard edit", "review my draft", "check this for slop", or as the last gate before publishing any long-form article, pillar, post, or email. Dispatches a fresh-eyes subagent that returns structured editor's notes (AI slop, non-conversational phrasing, confusing rhetoric, simpler-rewrite and narrative/storyline opportunities, and anything an editorial-outlet editor would flag); the main agent then triages and implements the accepted edits, then re-checks against the house standard.

2026-07-051

name	consulting-followup-sequencer
description	Generate the timed follow-up cadence for a deal, personalized to the client's stated stakes. Use after a call or proposal, on "draft follow-ups", "they went quiet", "what do I send next".

Consulting Follow-Up Sequencer

Voice + gate: write in consulting-copy-writer voice, then run every draft through consulting-outbound-email (read context, route, reader-POV check) before staging.

Steps

Pull the deal's specifics: the outcome discussed, the stakes in their words, the next-meeting date.
Fill the templates in library/email-templates/:
- Same-day thank-you
- 24h value-add (attach a relevant resource/case study)
- Proposal delivery (within 48h, suggest a Loom)
If silent, generate the Day 5 / 10 / 15 sequence (max 3 touches), each referencing their stakes, not your proposal.
Stage in Gmail (optional). Offer to drop each touch into Gmail as a draft via integrations/gmail/_work/create_draft.py --to <addr> --subject "..." --body-file <file> (creates a draft; only sends with --send + a typed confirmation). Save drafts next to the deal (e.g. pipeline/01-leads/<deal>/followups.md).
Offer to set reminders / a scheduled task for the cadence.

Output: ready-to-send emails (optionally staged as Gmail drafts). Source: Ch. 14 (48-Hour Rule + follow-up sequence).