メニュー
Run the 72-hour retrospective on a published draft and save the conclusion in retros/. Use when the user says "retro this post", "review how this performed", or wants to update the draft lifecycle after publishing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Turn one approved idea brief or one raw user thought into a finished LinkedIn post in the owner's voice. Use when the user says "write a post", "draft this thought", "turn this into a LinkedIn post", "polish this for LinkedIn", picks an approved idea from post-ideator, or hands over raw material. Works from that single input only, grounded in the post corpus and post-patterns for voice and shape.
Generate the image-generation prompts for a multi-slide LinkedIn carousel from a `format: carousel` draft — one paste-ready prompt per slide, in a consistent hand-drawn visual system, with each tool's pros/cons rendered in-image and a reserved blank band for the product logo. Use when a carousel draft is approved, the user says "carousel image", "slide prompts for this", "generate the carousel", or `post-cycle` reaches the visual step on a carousel draft. Writes an index `concepts/<date>-<slug>/prompt.md` plus `slide-NN.md` files, updates the draft's `concept_path`, and prints each slide prompt for the user to paste into their image tool. Trigger phrases: "post-carousel", "carousel image", "slide prompts".
Critique one draft against the approved idea brief, the archive winners, and the pattern report. Use when the user says "review this draft", "should I publish this", "critique this post", or after post-writer completes a draft. Approves only strong drafts and returns a single rewrite plan when rejecting.
Run the full LinkedIn post pipeline end-to-end in one go — briefing (if missing), top-posts + patterns context, ideator shortlist, writer draft, critic verdict. Use when the user says "full cycle", "run the pipeline", "do the whole flow", "post-cycle", "give me a post end to end", or wants a single command that replaces invoking topics-briefing, post-ideator, post-writer, and post-critic separately. Optionally accepts an idea number to pick from a freshly generated shortlist.
Generate the image-generation prompt for a `format: decision-tree` LinkedIn post — a single clean hand-drawn flowchart that routes the reader from a root question to a recommendation across 3 to 5 labelled branches, with the question rendered as the in-image title. Use when a decision-tree draft is approved, the user says "flowchart image", "decision tree image", "render the tree", or `post-cycle` reaches the visual step on a decision-tree draft. Saves the prompt to `concepts/<date>-<slug>/prompt.md`, updates the draft's `concept_path`, and prints the prompt to paste into an image tool. Trigger phrases: "post-flowchart", "flowchart image", "decision tree image".
Find LinkedIn post angles that can reach technical builders right now, but only when the angle is specific, differentiated, and defensible. Use when the user says "what should I post about", "pitch me ideas", "give me post angles", "find a topic", "ideate a post", or asks for fresh material without supplying a thought. Returns 3 to 5 scored idea briefs and writes shortlisted ones into ideas/YYYY-MM-DD.md.
| name | post-retro |
| description | Run the 72-hour retrospective on a published draft and save the conclusion in retros/. Use when the user says "retro this post", "review how this performed", or wants to update the draft lifecycle after publishing. |
Run this 72 hours after a draft is published.
This is the analyst stage — emit end once the retro file is written, per office-emit-end.
drafts/YYYY-MM-DD-<slug>.mdbun run post-patternsThe draft frontmatter should include:
published_urlpublished_atimpressions_24himpressions_72hlikes_72hcomments_72hshares_72hIf these are missing, ask for the missing metrics or tell the user exactly which fields still need to be filled in.
Every retro must answer:
topic_family + source_type posts?Save one markdown file to retros/YYYY-MM-DD-<slug>.md with YAML frontmatter:
---
draft_file: drafts/YYYY-MM-DD-<slug>.md
topic_family: security
source_type: news
published_url: ...
published_at: ...
impressions_24h: 1200
impressions_72h: 1800
likes_72h: 45
comments_72h: 7
shares_72h: 3
beat_median_impressions: true
beat_peer_group: false
discussion_validated: true
hook_matched_body: true
decision: modify
summary: Strong reach, but the comment thread drifted away from the intended angle.
---
The body should explain the decision in a few short paragraphs and name one concrete thing to repeat, modify, or stop.