Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

webinar-linkedin-posts

Sterne4

Forks0

Aktualisiert8. Mai 2026 um 03:54

When the user wants webinar LinkedIn promo posts — intro post, partner mirror, partner thought-leadership post, last-minute boost posts. Trigger phrases include "linkedin posts", "linkedin promo", "linkedin webinar posts", "thought leadership post", "boost posts", "webinar social posts". Run this AFTER the brief is filled out.

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

TravisDFoster

TravisDFoster/claude-growth-engine

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	webinar-linkedin-posts
description	When the user wants webinar LinkedIn promo posts — intro post, partner mirror, partner thought-leadership post, last-minute boost posts. Trigger phrases include "linkedin posts", "linkedin promo", "linkedin webinar posts", "thought leadership post", "boost posts", "webinar social posts". Run this AFTER the brief is filled out.
metadata	{"version":"0.1.0"}

Webinar LinkedIn Posts

Produce the 5-post LinkedIn lineup for one webinar. Two voices (Cerkl + partner), three cadence positions, one partner thought-leadership piece.

Prerequisites

Brief is filled out (especially: title, date, time, key learnings, partner perspective, social snippet)
Tracking URLs exist: cerkl_linkedin and <partner>_linkedin

The 5 posts

#	Post	Voice	Send	Tracking URL
1	Intro post	Cerkl (company page or Tarek)	T-3w	`cerkl_linkedin`
2	Intro mirror	Partner	T-10d	`<partner>_linkedin`
3	Thought-leadership	Partner	T-10d	`<partner>_linkedin`
4	Boost (last-minute reg push)	Cerkl	T-2d	`cerkl_linkedin`
5	Boost (last-minute reg push)	Partner	T-2d	`<partner>_linkedin`

For the boost posts (#4 and #5), provide 2–3 angle options (urgency, conversational, short-and-direct) so the user can pick.

Universal LinkedIn rules

Reach is suppressed when the post body contains an outbound link. Put the registration link in the first comment, not the post body. Reference it at the end as "🔗 Registration link in comments". Hashtags: 2–3 max.

This applies to all 5 posts.

Cerkl context to apply

Foundations ICP: HR generalist scrolling LinkedIn — lead with the problem they're feeling, not the product category
Voice differentiation: Cerkl posts are sharper and more declarative. Partner posts are personal and story-led. Don't make them sound the same.
No "demo" or "talk to sales" CTA — registration is the only ask

Reference

matt-frost-linkedin.md — gold-standard structure (intro post + day-before with multiple angle options)
linkedin-writing-guide.md — Cerkl LinkedIn voice and format
Generic skill (input only): /Users/travisfoster/claude-code/cerkl/marketing/skills/social-content/SKILL.md

Output

Write to <speaker-slug>-linkedin.md in the event folder. Structure:

# LinkedIn Posts — <Webinar Title>

**Webinar:** ...
**Date:** YYYY-MM-DD
**Cerkl tracking URL:** ...
**Partner tracking URL:** ...

> LinkedIn note: registration link goes in the first comment, not post body.

---

## Post #1 — Intro (Cerkl, T-3w, post YYYY-MM-DD)
...

## Post #2 — Intro mirror (Partner, T-10d, post YYYY-MM-DD)
...

## Post #3 — Thought-leadership (Partner, T-10d, post YYYY-MM-DD)
...

## Post #4 — Boost (Cerkl, T-2d, post YYYY-MM-DD)
### Option A — Urgency
...
### Option B — Conversational
...
### Option C — Short and direct
...

## Post #5 — Boost (Partner, T-2d, post YYYY-MM-DD)
### Option A — ...
...

Push update

After producing the posts, append an update block to the relevant file in personal-assistant/projects/. See ../../CLAUDE.md for the protocol.

Mehr aus diesem Repository

gleiches Repository

md-to-drive

TravisDFoster/claude-growth-engine

User-invoked skill to upload one or more local Markdown files to Travis's Google Drive as native Google Docs (not as .md attachments) using the gws CLI. Default destination is the "Claude-Uploads" folder at Drive root. Trigger phrases include "upload to drive", "convert to google doc", "send this to claude-uploads", "publish these to drive", "drop these markdown files into drive", "make google docs from these". For batches of 2+ files, dispatch one parallel subagent per file.

2026-07-014

linkedin-editing

TravisDFoster/claude-growth-engine

Edit a LinkedIn draft before its copy lands in the Jira CSV. Two quick passes (hook/tightness, then a hard compliance gate) plus a scaled score. Enforces linkedin-writing-guide.md so voice/policy rules are checked by a fresh pass, not self-graded by the drafter. Use inside linkedin-process.md (Step 4.5) or standalone on any drafts/ file.

2026-07-014

webinar-promo-emails

TravisDFoster/claude-growth-engine

When the user wants webinar promotional emails — the 3-email sequence (intro at T-10d, value reiteration at T-3d, last reminder at T-1d) for both Cerkl and the partner, plus the 1:1 sales outreach snippet reps paste into active deals. Trigger phrases include "promo emails", "webinar emails", "email sequence", "promotional emails", "draft the emails", "T-10 email", "day-before email", "last reminder email", "sales outreach snippet", "sales email template", "something for sales to send", "1:1 rep outreach". Run this AFTER the brief is filled out.

2026-07-014

deal-health-analyst

TravisDFoster/claude-growth-engine

Sub-agent brief for the Deal Report's inference pass — reads ONE flagged deal's cleaned email threads + structural metrics and returns sentiment, the open next-step, and a short risk narrative. Invoked only on deals the rules band watch/at_risk (or a deal Travis names). Never sets the band; explains it.

2026-07-014

html-to-pdf

TravisDFoster/claude-growth-engine

When the user wants to convert a rendered HTML file to a PDF, when a process is generating a print-format deliverable (one-pager, slide handout, designed report), when the final step of a render pipeline needs to produce a .pdf sibling. Triggers on phrases like "render to PDF," "save as PDF," "convert to PDF," "print this." Built-in verify gate: runs html-overflow-detector first; if the HTML has layout overflow, the PDF is NOT written and the caller is told to apply remediation. Invoked automatically by one-pager-process.md as the final step after md-to-html.

2026-07-014

webinar-canva-render

TravisDFoster/claude-growth-engine

Render the full Canva asset pack for one webinar by dispatching one parallel sub-agent per manifest in the event's canva-manifests/ folder. Each sub-agent invokes template-fill against its assigned manifest and returns the Canva edit URL. The orchestrator appends each URL to its manifest YAML (primary source-of-truth) and mirrors the URL into the Drive MAP's Deliverable column (bonus for the internal team). Trigger phrases: 'render the canva assets for [webinar]', 'kick off canva render for rachel', 'run the asset pack render', 'fill all the webinar templates'. Inputs: event-folder path + headshot Canva asset ID. Output: chat-printed roll-up of role → URL + warnings + manual_drag_required list.

2026-06-174

name	webinar-linkedin-posts
description	When the user wants webinar LinkedIn promo posts — intro post, partner mirror, partner thought-leadership post, last-minute boost posts. Trigger phrases include "linkedin posts", "linkedin promo", "linkedin webinar posts", "thought leadership post", "boost posts", "webinar social posts". Run this AFTER the brief is filled out.
metadata	{"version":"0.1.0"}

Webinar LinkedIn Posts

Produce the 5-post LinkedIn lineup for one webinar. Two voices (Cerkl + partner), three cadence positions, one partner thought-leadership piece.

Prerequisites

Brief is filled out (especially: title, date, time, key learnings, partner perspective, social snippet)
Tracking URLs exist: cerkl_linkedin and <partner>_linkedin

The 5 posts

#	Post	Voice	Send	Tracking URL
1	Intro post	Cerkl (company page or Tarek)	T-3w	`cerkl_linkedin`
2	Intro mirror	Partner	T-10d	`<partner>_linkedin`
3	Thought-leadership	Partner	T-10d	`<partner>_linkedin`
4	Boost (last-minute reg push)	Cerkl	T-2d	`cerkl_linkedin`
5	Boost (last-minute reg push)	Partner	T-2d	`<partner>_linkedin`

For the boost posts (#4 and #5), provide 2–3 angle options (urgency, conversational, short-and-direct) so the user can pick.

Universal LinkedIn rules

Reach is suppressed when the post body contains an outbound link. Put the registration link in the first comment, not the post body. Reference it at the end as "🔗 Registration link in comments". Hashtags: 2–3 max.

This applies to all 5 posts.

Cerkl context to apply

Foundations ICP: HR generalist scrolling LinkedIn — lead with the problem they're feeling, not the product category
Voice differentiation: Cerkl posts are sharper and more declarative. Partner posts are personal and story-led. Don't make them sound the same.
No "demo" or "talk to sales" CTA — registration is the only ask

Reference

matt-frost-linkedin.md — gold-standard structure (intro post + day-before with multiple angle options)
linkedin-writing-guide.md — Cerkl LinkedIn voice and format
Generic skill (input only): /Users/travisfoster/claude-code/cerkl/marketing/skills/social-content/SKILL.md

Output

Write to <speaker-slug>-linkedin.md in the event folder. Structure:

# LinkedIn Posts — <Webinar Title>

**Webinar:** ...
**Date:** YYYY-MM-DD
**Cerkl tracking URL:** ...
**Partner tracking URL:** ...

> LinkedIn note: registration link goes in the first comment, not post body.

---

## Post #1 — Intro (Cerkl, T-3w, post YYYY-MM-DD)
...

## Post #2 — Intro mirror (Partner, T-10d, post YYYY-MM-DD)
...

## Post #3 — Thought-leadership (Partner, T-10d, post YYYY-MM-DD)
...

## Post #4 — Boost (Cerkl, T-2d, post YYYY-MM-DD)
### Option A — Urgency
...
### Option B — Conversational
...
### Option C — Short and direct
...

## Post #5 — Boost (Partner, T-2d, post YYYY-MM-DD)
### Option A — ...
...

Push update

After producing the posts, append an update block to the relevant file in personal-assistant/projects/. See ../../CLAUDE.md for the protocol.