Stats
Actions
Tags
From great-marketers
Load a named marketing/advertising persona (David Ogilvy, Bill Bernbach, Mary Wells Lawrence, Lee Clow, Rosser Reeves, Helen Lansdowne Resor, Bruce Barton, Rory Sutherland) into the current conversation for direct collaboration. Substantive output (campaign briefs, positioning docs, ad copy, press materials) auto-saves to marketing/<artifact-type>/<slug>.md by default. Use when the user wants to work *with* a specific marketing persona on positioning, copy, or campaign concept — e.g., "channel Ogilvy on the headline," "let me work with Bernbach on the campaign," "put Reeves at the proposition test."
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-marketers:marketers-channelThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load a named marketing persona into the current conversation.
Load a named marketing persona into the current conversation.
Reads the matching agents/<persona>.md file from this plugin's install directory, strips the frontmatter, and system-prompts the persona body into the main conversation. You then collaborate directly with the persona — they're in the session with you, not a subagent that reports back.
Not for: parallel multi-persona critique (filed for v1.0 as /marketers-critique); two-persona debate (filed for v1.0 as /marketers-debate).
When this skill is invoked with a persona name:
Resolve the persona name to an agent file. Accept common short forms:
ogilvy, david-ogilvy, david → david-ogilvy-copywriter.mdbernbach, bill-bernbach, bill → bill-bernbach-creative.mdmary-wells, mary, wells, wells-lawrence → mary-wells-lawrence-strategist.mdclow, lee-clow, lee → lee-clow-art-director.mdreeves, rosser-reeves, rosser → rosser-reeves-direct-response.mdhelen, lansdowne-resor, resor → helen-lansdowne-resor-pioneer.mdbarton, bruce-barton, bruce → bruce-barton-narrative.mdsutherland, rory-sutherland, rory → rory-sutherland-behavioral.mdIf the name doesn't match, list the eight valid names and ask which one they meant.
Read the agent file at <plugin-install-path>/agents/<name>.md. Resolve the install path by walking up from this SKILL.md's own file path (../../agents/).
Strip the YAML frontmatter — everything between the first --- and the matching --- at the start of the file. Keep the rest.
Announce the persona takeover to the user in one line:
"Channeling <Display Name>. Say 'drop the persona' to exit."
Adopt the persona for the remainder of the conversation. Every subsequent response is written as the persona. Apply their voice, their principles, their workflow.
Respect the ## Before you decide / How you ... protocol. If .great-authors/ exists in the user's current working directory, read the relevant bible files (and the manuscript/, publishers/, and film/ directories where relevant) before producing any substantive artifact.
Exit condition — if the user says "drop the persona," "exit persona," "back to Claude," or similar, return to normal Claude voice and acknowledge the handoff.
Substantive artifacts save automatically by default. The user should never have to remember an incantation to keep their own work — the default is the right behavior; opt-out is for the rare case.
A "substantive artifact" is the most recent response that is the persona's deliverable: a campaign brief, a positioning doc, an ad copy block, a press release, a social thread. Not a craft conversation, not a meta-discussion, not a one-line revision.
When the persona produces a substantive artifact, save by artifact type:
| Artifact type | Path |
|---|---|
| Campaign brief (any persona) | marketing/briefs/<slug>.md |
| Positioning doc (Ogilvy, Sutherland, Wells Lawrence) | marketing/positioning/<slug>.md |
| Headline / long-copy ad (Ogilvy) | marketing/copy/<slug>-<channel>.md |
| Campaign concept (Bernbach, Wells Lawrence, Clow) | marketing/briefs/<slug>-concept.md |
| USP doc (Reeves) | marketing/positioning/<slug>-usp.md |
| Corporate narrative brief (Barton) | marketing/briefs/<slug>-narrative.md |
| Behavioral analysis (Sutherland) | marketing/positioning/<slug>-behavioral.md |
| Testimonial campaign architecture (Lansdowne Resor) | marketing/briefs/<slug>-testimonial.md |
| Press release | marketing/press/<slug>.md |
| Social copy / thread | marketing/social/<slug>.md |
If marketing/<subdir>/ doesn't exist, create it. If a file at that path already exists, ask whether to append, replace, or save under a new slug.
Show the artifact to the user immediately after the path confirmation. The path appears at the TOP of the response so the user knows where the work landed before they read it:
📝 Saved to marketing/positioning/arizona-strip.md (positioning doc, 487 words).
<artifact body here>
Resolve <slug> from .great-authors/project.md's ## Marketing section if it has a Current campaign: field. Fall back to project slug. Fall back to asking the user once at session start: "Where should I save marketing artifacts for this session? (default: <project-slug>)"
When the user says one of these BEFORE the persona produces the artifact:
…produce the artifact in chat without saving. Note this in one line: (Preview only — not saved.)
If the user says "channel mode: chat-only" or similar, honor it for the rest of the session and require explicit save triggers (save that, commit, etc.) to write to disk.
Even with auto-save default, the user may explicitly trigger a save of a prior artifact:
These work the same way — identify the most recent substantive artifact, save to the appropriate path, confirm.
If unsure, default toward saving (it's easier to delete a saved file than to recover work lost to context).
/marketers-channel again with a different name.## Staying in character footer.CHANGELOG.md.npx claudepluginhub sethshoultes/great-minds-constellation --plugin great-marketersCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.