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

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

webinar-brief

Étoiles4

Forks0

Mis à jour7 mai 2026 à 01:34

When the user wants to draft, write, refine, or fill out a webinar brief. Trigger phrases include "write the brief", "draft the brief", "fill out the brief", "webinar brief content", "structure the outline", "polish the brief", "objective and core message". Run this AFTER `webinar-project-init` has scaffolded the brief skeleton AND the user has had at least one topic-defining conversation with the partner.

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

TravisDFoster

TravisDFoster/claude-growth-engine

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

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

SKILL.md

readonly

name	webinar-brief
description	When the user wants to draft, write, refine, or fill out a webinar brief. Trigger phrases include "write the brief", "draft the brief", "fill out the brief", "webinar brief content", "structure the outline", "polish the brief", "objective and core message". Run this AFTER `webinar-project-init` has scaffolded the brief skeleton AND the user has had at least one topic-defining conversation with the partner.
metadata	{"version":"0.1.0"}

Webinar Brief

Fill out the brief content (<speaker-slug>.md) section by section, working from notes the user provides from partner conversations.

Prerequisites

The brief file exists (created by webinar-project-init)
Frontmatter is filled (title, date, partner, etc.)
The user has notes / transcripts / themes from partner discussions

Inputs to gather

If not already in the file or provided by the user, ask for:

Partner's POV on the topic — their angle, what they want to say
Specific failure points or problems being addressed
Giveaway details (what + value to attendee)
Polling question ideas (if any)

Sections to fill, in order

Each builds on the previous — don't jump around:

Objective (Primary, Secondary, Strategic) — anchors everything else
Core Message — single sentence + 2–4 supporting pillars
Description for Marketing Copy / Key Learnings — feeds emails, LinkedIn, registration page
Structure / Outline (60 minutes) — section by section, with leads/supports per segment
Target Audience — Roles, Org Profile, Psychographic
What Attendees Will Learn — concrete takeaways per learning area
Partner's Perspective — partner's title, synopsis, attendee outcomes (in their voice)
Polling Questions — 3–5 self-diagnostic questions
Promotion Plan — themes, sample subject lines, sample post angle

Cerkl context to apply

Foundations ICP fit: test each section against the Foundations buyer (HR generalist, ops lead, 50–500 person company). If a section reads like enterprise-evaluator content, flag it.
Diagnosis-and-guiding-policy alignment: per the marketing guiding policy, webinars should reach pre-evaluation buyers, not category-aware ones. The CTA must be Foundations sign-up (frictionless), never "request a demo".
Voice differentiation: the Partner's Perspective section preserves the partner's voice. Don't sanitize it into Cerkl voice.

Reference

The Matt Frost brief is the gold-standard example for tone, depth, and structure. Mine it for patterns when stuck.

Output

Write directly to <speaker-slug>.md. Replace placeholder brackets with content; keep the existing structure intact.

Push update

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

Plus depuis ce dépôt

même dépôt

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-brief
description	When the user wants to draft, write, refine, or fill out a webinar brief. Trigger phrases include "write the brief", "draft the brief", "fill out the brief", "webinar brief content", "structure the outline", "polish the brief", "objective and core message". Run this AFTER `webinar-project-init` has scaffolded the brief skeleton AND the user has had at least one topic-defining conversation with the partner.
metadata	{"version":"0.1.0"}

Webinar Brief

Fill out the brief content (<speaker-slug>.md) section by section, working from notes the user provides from partner conversations.

Prerequisites

The brief file exists (created by webinar-project-init)
Frontmatter is filled (title, date, partner, etc.)
The user has notes / transcripts / themes from partner discussions

Inputs to gather

If not already in the file or provided by the user, ask for:

Partner's POV on the topic — their angle, what they want to say
Specific failure points or problems being addressed
Giveaway details (what + value to attendee)
Polling question ideas (if any)

Sections to fill, in order

Each builds on the previous — don't jump around:

Objective (Primary, Secondary, Strategic) — anchors everything else
Core Message — single sentence + 2–4 supporting pillars
Description for Marketing Copy / Key Learnings — feeds emails, LinkedIn, registration page
Structure / Outline (60 minutes) — section by section, with leads/supports per segment
Target Audience — Roles, Org Profile, Psychographic
What Attendees Will Learn — concrete takeaways per learning area
Partner's Perspective — partner's title, synopsis, attendee outcomes (in their voice)
Polling Questions — 3–5 self-diagnostic questions
Promotion Plan — themes, sample subject lines, sample post angle

Cerkl context to apply

Foundations ICP fit: test each section against the Foundations buyer (HR generalist, ops lead, 50–500 person company). If a section reads like enterprise-evaluator content, flag it.
Diagnosis-and-guiding-policy alignment: per the marketing guiding policy, webinars should reach pre-evaluation buyers, not category-aware ones. The CTA must be Foundations sign-up (frictionless), never "request a demo".
Voice differentiation: the Partner's Perspective section preserves the partner's voice. Don't sanitize it into Cerkl voice.

Reference

The Matt Frost brief is the gold-standard example for tone, depth, and structure. Mine it for patterns when stuck.

Output

Write directly to <speaker-slug>.md. Replace placeholder brackets with content; keep the existing structure intact.

Push update

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