Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

consulting-comms-logger

Étoiles1

Forks0

Mis à jour24 juin 2026 à 00:43

Log a single comms event on a deal/client (you sent, they replied, it was opened, you got a message) and reconcile state. Use on "I sent that", "he replied", "they opened it", "got a reply from {name}", "just emailed {name}", or a screenshot of a sent/received message. Faithfully records the as-sent/as-received text + the engagement signal (open != reply), then updates the deal AGENTS.md, _board.md, any active followups sequence, and whose ball it is. NOT consulting-call-processor (the heavy "new material -> extract + mine" loop for transcripts/notes/results) and NOT consulting-inbox-triage (the radar for what needs a reply across deals) -- this is the light "log one touch and reconcile" move.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

sidneyswift

sidneyswift/consulting-plugin

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name

consulting-comms-logger

description

Consulting Comms Logger

The fast path for after a touch happens. Email skills (consulting-outbound-email, consulting-followup-sequencer) own drafting; this skill owns recording the event and reconciling the deal once a message has actually gone out or come in. Git is the episodic memory, so a logged touch must leave the dashboards true.

Scope one deal. Load only that entity's folder + its live Attio/Gmail (deal-scoped loading). Logging only — never auto-send, never fabricate.

Steps

Identify the deal/client. Locate pipeline/<stage>/<deal>/ or clients/<client>/. If you can't tell which deal, ask.
Capture the event faithfully (evidence discipline).
- As-sent / as-received text, verbatim — what actually went out, not the draft you think was sent. From a screenshot, transcribe exactly. Note the provenance ("logged from Sid's word" vs. "screenshot" vs. "live Gmail"), since a screenshot is stronger than a paraphrase.
- Channel + timestamp (thread subject, LinkedIn, etc.), in the user's timezone.
- Engagement signal, read literally: an open / read-receipt is engagement, not a reply; a reply is not a commitment. Quote the source (Superhuman receipt, screenshot, live Gmail). Never upgrade a signal into momentum ("opened in 2 min" = watching the thread, still no reply/booking/decision).
- Missing detail? Get it from the live source, not a stale snapshot (e.g. a cc email: the synced integrations/gmail/threads/<deal>.json predates today's reply, so query Gmail live). Never guess an address or name.
Decide the ball + posture. Who owes the next move now (mirror pull_threads.py logic): a question/ask to you = needs you; a forward commitment ("I'll get back to you") = on them; an open with no reply = still on them. When the ball is on them, the posture is don't chase (let consulting-lead-temperature set the objective if a touch is warranted).
Reconcile every state surface (the actual job):
- Deal AGENTS.md: the ## Reality "where it stands" line, the 📧 Email signal log (append dated), the Next action, and the ball. Keep the [MISSING] list honest (resolve what this event answered: a timeline, a stakeholder, who-signs).
- pipeline/_board.md row (or the client board).
- Active followups.md: STOP the sequence the moment they reply (mark queued touches VOID); otherwise advance it. A reply kills the nudge cadence.
- New stakeholder surfaced? Capture them: live email lookup + a dedup-safe Attio add (check by email before creating; dry-run then apply) and add to the dashboard roster.
Reconcile-on-touch (Attio). A comms touch usually does not change the deal stage, but verify live and fix any drift (Attio wins on stage, the repo on artifacts). Don't copy the CRM in.
Report + commit. Summarize what changed in one or two lines; the commit is the memory. Offer to commit (don't auto-commit unless asked).

Worked example (Stellar, 2026-06-23)

One thread, three touches logged in a session, dashboards kept true throughout:

Touch 1 sent 12:43pm ET -> logged as-sent text; opened ~2 min later logged as engaged, not a reply (open != reply); ball stayed on Morten.
Morten replied 12:47pm (partner-gated, no timeline) cc'ing a new stakeholder (Ryan Peterson) -> followups sequence STOPPED (Touch 2/3 voided); new stakeholder captured live from Gmail and added dedup-safe to Attio; Next action + board + email-signal reconciled; ball read as on him.
Reply-all sent 3:19pm -> ball back on Ryan/partners; "don't chase"; watch date set.

Heavy intake (transcript / note / result) -> consulting-call-processor.
"What across all deals needs a reply?" -> consulting-inbox-triage.
Drafting the next touch -> consulting-followup-sequencer + consulting-outbound-email.
Posture/score -> consulting-lead-temperature. CRM mechanics -> integrations/attio/crm-sync.md.

Plus depuis ce dépôt

même dépôt

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-comms-logger

description

Consulting Comms Logger

Scope one deal. Load only that entity's folder + its live Attio/Gmail (deal-scoped loading). Logging only — never auto-send, never fabricate.

Steps

Identify the deal/client. Locate pipeline/<stage>/<deal>/ or clients/<client>/. If you can't tell which deal, ask.
Capture the event faithfully (evidence discipline).
- As-sent / as-received text, verbatim — what actually went out, not the draft you think was sent. From a screenshot, transcribe exactly. Note the provenance ("logged from Sid's word" vs. "screenshot" vs. "live Gmail"), since a screenshot is stronger than a paraphrase.
- Channel + timestamp (thread subject, LinkedIn, etc.), in the user's timezone.
- Engagement signal, read literally: an open / read-receipt is engagement, not a reply; a reply is not a commitment. Quote the source (Superhuman receipt, screenshot, live Gmail). Never upgrade a signal into momentum ("opened in 2 min" = watching the thread, still no reply/booking/decision).
- Missing detail? Get it from the live source, not a stale snapshot (e.g. a cc email: the synced integrations/gmail/threads/<deal>.json predates today's reply, so query Gmail live). Never guess an address or name.
Decide the ball + posture. Who owes the next move now (mirror pull_threads.py logic): a question/ask to you = needs you; a forward commitment ("I'll get back to you") = on them; an open with no reply = still on them. When the ball is on them, the posture is don't chase (let consulting-lead-temperature set the objective if a touch is warranted).
Reconcile every state surface (the actual job):
- Deal AGENTS.md: the ## Reality "where it stands" line, the 📧 Email signal log (append dated), the Next action, and the ball. Keep the [MISSING] list honest (resolve what this event answered: a timeline, a stakeholder, who-signs).
- pipeline/_board.md row (or the client board).
- Active followups.md: STOP the sequence the moment they reply (mark queued touches VOID); otherwise advance it. A reply kills the nudge cadence.
- New stakeholder surfaced? Capture them: live email lookup + a dedup-safe Attio add (check by email before creating; dry-run then apply) and add to the dashboard roster.
Reconcile-on-touch (Attio). A comms touch usually does not change the deal stage, but verify live and fix any drift (Attio wins on stage, the repo on artifacts). Don't copy the CRM in.
Report + commit. Summarize what changed in one or two lines; the commit is the memory. Offer to commit (don't auto-commit unless asked).

Worked example (Stellar, 2026-06-23)

One thread, three touches logged in a session, dashboards kept true throughout:

Touch 1 sent 12:43pm ET -> logged as-sent text; opened ~2 min later logged as engaged, not a reply (open != reply); ball stayed on Morten.
Morten replied 12:47pm (partner-gated, no timeline) cc'ing a new stakeholder (Ryan Peterson) -> followups sequence STOPPED (Touch 2/3 voided); new stakeholder captured live from Gmail and added dedup-safe to Attio; Next action + board + email-signal reconciled; ball read as on him.
Reply-all sent 3:19pm -> ball back on Ryan/partners; "don't chase"; watch date set.

Heavy intake (transcript / note / result) -> consulting-call-processor.
"What across all deals needs a reply?" -> consulting-inbox-triage.
Drafting the next touch -> consulting-followup-sequencer + consulting-outbound-email.
Posture/score -> consulting-lead-temperature. CRM mechanics -> integrations/attio/crm-sync.md.

consulting-comms-logger

Consulting Comms Logger

Steps

Worked example (Stellar, 2026-06-23)

Related

Consulting Comms Logger

Steps

Worked example (Stellar, 2026-06-23)

Related