Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

consulting-content-extraction

Sterne1

Forks0

Aktualisiert30. Juni 2026 um 20:38

Extract reusable content, insights, and knowledge-base entries from a call transcript or meeting note. Use whenever a new transcript lands in content/01-raw/ or a client's meetings/ folder, after any client/sales call, or when the user says "extract content", "mine this call", "turn this into posts/insights". Powers the content flywheel ("never answer the same question twice").

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

sidneyswift

sidneyswift/consulting-plugin

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Marktforschungsanalysten und MarketingspezialistenWirtschafts- und Finanzberufe·SOC 13-1161

SKILL.md

readonly

name	consulting-content-extraction
description	Extract reusable content, insights, and knowledge-base entries from a call transcript or meeting note. Use whenever a new transcript lands in content/01-raw/ or a client's meetings/ folder, after any client/sales call, or when the user says "extract content", "mine this call", "turn this into posts/insights". Powers the content flywheel ("never answer the same question twice").

Consulting Content Extraction

Turn a raw transcript into compounding assets.

When to run

Automatically after any new transcript is saved (content/01-raw/ or clients/{client}/meetings/), or on request.

Steps

Read the transcript.
Extract and output, grouped:
- Quotable insights shared about AI/consulting
- Useful analogies or frameworks used
- Industry-specific examples given
- Questions that revealed deep insight
- Moments that reframed the client's thinking
Format each as a candidate LinkedIn post or blog topic.
Deposit results as atomic signals in signals/ — one file per item, each with frontmatter (schema
- lifecycle in signals/AGENTS.md): a traversable source (the transcript path + line/quote you pulled it from), type, hook, intent, formats, status: new. This is the owned write-step for the reservoir:
- Reusable explanation / durable POV → a type: insight signal (status: evergreen).
- Post/blog candidate → a type: content-idea signal (status: new).
- Recurring question already answered before → knowledge/faqs/ (reference knowledge, not a signal).
If the same topic now appears 2+ times, flag it as a strong content piece.

Mehr aus diesem Repository

gleiches 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-content-extraction
description	Extract reusable content, insights, and knowledge-base entries from a call transcript or meeting note. Use whenever a new transcript lands in content/01-raw/ or a client's meetings/ folder, after any client/sales call, or when the user says "extract content", "mine this call", "turn this into posts/insights". Powers the content flywheel ("never answer the same question twice").

Consulting Content Extraction

Turn a raw transcript into compounding assets.

When to run

Automatically after any new transcript is saved (content/01-raw/ or clients/{client}/meetings/), or on request.

Steps

Read the transcript.
Extract and output, grouped:
- Quotable insights shared about AI/consulting
- Useful analogies or frameworks used
- Industry-specific examples given
- Questions that revealed deep insight
- Moments that reframed the client's thinking
Format each as a candidate LinkedIn post or blog topic.
Deposit results as atomic signals in signals/ — one file per item, each with frontmatter (schema
- lifecycle in signals/AGENTS.md): a traversable source (the transcript path + line/quote you pulled it from), type, hook, intent, formats, status: new. This is the owned write-step for the reservoir:
- Reusable explanation / durable POV → a type: insight signal (status: evergreen).
- Post/blog candidate → a type: content-idea signal (status: new).
- Recurring question already answered before → knowledge/faqs/ (reference knowledge, not a signal).
If the same topic now appears 2+ times, flag it as a strong content piece.