تشغيل أي مهارة في Manus بنقرة واحدة

consulting-call-processor

النجوم١

التفرعات٠

آخر تحديث٢٤ يونيو ٢٠٢٦ في ٠٤:٢٥

The auto-manage orchestrator. Use whenever new client/deal material lands — a transcript, meeting note, email, or result — or when the user says "process this call", "ingest this", "handle this transcript". Runs the full keep-the-system-current loop end to end.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

sidneyswift

sidneyswift/consulting-plugin

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

متخصصو إدارة المشاريعمهن الأعمال والعمليات المالية·SOC 13-1082

SKILL.md

readonly

name	consulting-call-processor
description	The auto-manage orchestrator. Use whenever new client/deal material lands — a transcript, meeting note, email, or result — or when the user says "process this call", "ingest this", "handle this transcript". Runs the full keep-the-system-current loop end to end.

Consulting Call Processor

The CLAUDE.md auto-manage loop as one skill. Don't stop after a single step — run the whole loop, then report what changed.

Steps

Place the raw file. Save to the right home (content/01-raw/, clients/{client}/meetings/, or pipeline/{stage}/{deal}/), dated YYYY-MM-DD.
Read it.
Extract. Run consulting-content-extraction. If it's a discovery/sales call, also run consulting-discovery-analysis; if the deal is qualified, chain into consulting-proposal-drafting.
Scan the related folder. Open the client/deal folder, read its AGENTS.md dashboard, reconcile against the new info.
Update affected files. Refresh the client AGENTS.md dashboard (status, stakes, $, next action), pipeline/_board.md, and business/metrics/dashboard.html. Capture new stakeholders, decisions, dates.
Move files to match reality. If the deal changed stage, run consulting-deal-stage-mover.
Mine for content + proof. Recurring answers → knowledge/faqs/; wins → trigger consulting-case-study-builder / consulting-testimonial-capture.
Report a short summary of everything changed.

Confirm before inventing client facts; otherwise do the routine filing without asking.

المزيد من هذا المستودع

نفس المستودع

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-call-processor
description	The auto-manage orchestrator. Use whenever new client/deal material lands — a transcript, meeting note, email, or result — or when the user says "process this call", "ingest this", "handle this transcript". Runs the full keep-the-system-current loop end to end.

Consulting Call Processor

The CLAUDE.md auto-manage loop as one skill. Don't stop after a single step — run the whole loop, then report what changed.

Steps

Place the raw file. Save to the right home (content/01-raw/, clients/{client}/meetings/, or pipeline/{stage}/{deal}/), dated YYYY-MM-DD.
Read it.
Extract. Run consulting-content-extraction. If it's a discovery/sales call, also run consulting-discovery-analysis; if the deal is qualified, chain into consulting-proposal-drafting.
Scan the related folder. Open the client/deal folder, read its AGENTS.md dashboard, reconcile against the new info.
Update affected files. Refresh the client AGENTS.md dashboard (status, stakes, $, next action), pipeline/_board.md, and business/metrics/dashboard.html. Capture new stakeholders, decisions, dates.
Move files to match reality. If the deal changed stage, run consulting-deal-stage-mover.
Mine for content + proof. Recurring answers → knowledge/faqs/; wins → trigger consulting-case-study-builder / consulting-testimonial-capture.
Report a short summary of everything changed.

Confirm before inventing client facts; otherwise do the routine filing without asking.