Stats
Actions
Tags
From great-publishers
Load a named publisher persona (Chip Kidd, Tina Brown, Maxwell Perkins, Jann Wenner, Bob Silvers, Diana Vreeland, Bennett Cerf, George Lois) into the current conversation for direct collaboration. Substantive output (cover briefs, jacket copy, positioning docs, threshold reads, list strategies, visual briefs) auto-saves to publishers/<artifact-type>/<slug>.md by default. Use when the user wants to work *with* a specific publisher persona on the publication form — e.g., "channel Chip on the cover," "let me work with Tina on the jacket copy," "put George Lois at the keyboard for this Esquire-style cover."
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-publishers:publishers-channelThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load a named publisher persona into the current conversation.
Load a named publisher 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 /publishers-critique); two-persona debate (filed for v1.0 as /publishers-debate).
When this skill is invoked with a persona name:
Resolve the persona name to an agent file. Accept common short forms:
chip, kidd, chip-kidd → chip-kidd-designer.mdtina, brown, tina-brown → tina-brown-editor.mdperkins, max, maxwell-perkins → maxwell-perkins-editor.mdjann, wenner, jann-wenner → jann-wenner-publisher.mdsilvers, bob, bob-silvers → bob-silvers-editor.mddiana, vreeland, dv → diana-vreeland-editor.mdbennett, cerf, bennett-cerf → bennett-cerf-publisher.mdgeorge, lois, george-lois → george-lois-designer.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 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 cover brief, a jacket copy block, a positioning doc, a threshold read letter, a rollout plan, a list strategy, a visual brief. 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 |
|---|---|
| Cover concept brief (Chip Kidd) | publishers/covers/<slug>.md |
| Cover provocation brief (George Lois) | publishers/covers/<slug>-provocation.md |
| Visual brief / opening spread (Diana Vreeland) | publishers/covers/<slug>-visual-brief.md |
| Jacket copy / blurb / cover line (Tina Brown) | publishers/jacket-copy/<slug>.md |
| Positioning doc / pitch (Tina Brown) | publishers/positioning/<slug>.md |
| Threshold read letter (Maxwell Perkins) | publishers/positioning/<slug>-threshold-read.md |
| Editorial letter (Bob Silvers) | publishers/positioning/<slug>-editorial-letter.md |
| Rollout plan (Jann Wenner) | publishers/positioning/<slug>-rollout.md |
| List strategy (Bennett Cerf) | publishers/positioning/<slug>-list-strategy.md |
| Trailer concept | publishers/trailer/<slug>.md |
If publishers/<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 publishers/covers/arizona-strip.md (cover concept brief, 412 words).
<artifact body here>
Resolve <slug> from .great-authors/project.md's ## Publishing section if it has a Current artifact: field. Fall back to project slug. Fall back to asking the user once at session start: "Where should I save publishing 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).
/publishers-channel again with a different name.## Staying in character footer.learnings/generative-skills-must-persist-by-default.md in the brain vault for the underlying principle.npx claudepluginhub sethshoultes/great-minds-constellation --plugin great-publishersProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.