菜单
The weekly content + system review ritual. Use on "run the Friday review", weekly cadence, or "what should I write this week". Good candidate to wire as a scheduled task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | consulting-friday-review |
| description | The weekly content + system review ritual. Use on "run the Friday review", weekly cadence, or "what should I write this week". Good candidate to wire as a scheduled task. |
signals/ for unused signals — the dated <YYYY-MM-DD>-*.md files (status: new; skip the meta files AGENTS.md/_template.md/_index.md/_archive/; target 15–20 candidates).knowledge/ — repeats are the strongest content signal.integrations/linkedin/engagement/ for winners/outliers → run
consulting-content-recycler (repost with a fresh hook · re-share with context · fan an outlier
into new formats). A winner not recycled is shelf inventory.consulting-content-extraction on any un-processed transcripts in content/01-raw/.consulting-research-miner if the research wiki advanced since integrations/research/_work/LAST_MINED — harvest fresh agent/skill/compound-engineering ideas into signals/ (delta-guarded; no-ops if nothing's new).consulting-content-idea-generator) or draft (→ consulting-content-drafter).Source: Ch. 4 (the Friday Review).
Squeeze every published winner — repost proven posts with a fresh hook, re-share your own winners with added context, and fan one outlier post into multiple new formats. Use on "what should I repost", "recycle my winners", "this post popped, what now", "turn this outlier into more posts", "wring the towel", after an engagement pull shows a post outperforming baseline, or on the Friday review's recycle step. Reads published bundles + engagement data; stages new drafts; never auto-posts.
Write or critique the first line of a LinkedIn post (the hook) using patterns reverse-engineered from real top-performing posts. Use on "write hooks for this", "give me 10 hooks", "fix this hook", "why won't this hook land", "what's a scroll-stopping opener", or whenever drafting/critiquing a post's line 1. This is the dedicated hook engine; consulting-linkedin-post-architect handles whole-post structure and defers here for the hook; consulting-copy-writer governs voice/anti-slop.
Structure a high-performing LinkedIn post — pick the archetype and founder format (build log, documented failure, value post, receipt, contrast hook, milestone chapter), write a scroll-stopping hook, shape the body, format for mobile, choose the in-post CTA, and decide whether to pair an infographic. Use on "write a LinkedIn post", "make this post perform/go viral", "what hook should I use", "structure this for LinkedIn", "turn this insight into a LinkedIn post", "write a build log / failure / receipt / milestone post", or right after consulting-content-drafter. This is the post-STRUCTURE layer; consulting-copy-writer still governs voice/anti-slop, consulting-linkedin-publisher ships it.
Distribute one finished pillar article across every channel the same way — republish the same copy to the owned blog + LinkedIn newsletter + X (as an article, never a thread), ship the always-on companions (a LinkedIn promo post + an email to the list), point every link at the owned canonical URL, then find the live post and monitor its engagement into leads. Use after an article is written or published, on "distribute this", "post it everywhere", "atomize this article", "where else should this go", or when promoting a piece in content/04-published/.
Editorial copy-edit pass on a finished draft, run through a fresh-context subagent reviewer. Use on "copy-edit this", "edit this article", "do an editor pass", "give it a hard edit", "review my draft", "check this for slop", or as the last gate before publishing any long-form article, pillar, post, or email. Dispatches a fresh-eyes subagent that returns structured editor's notes (AI slop, non-conversational phrasing, confusing rhetoric, simpler-rewrite and narrative/storyline opportunities, and anything an editorial-outlet editor would flag); the main agent then triages and implements the accepted edits, then re-checks against the house standard.
Reader-reaction review of a finished draft, run through a fresh-context subagent that ROLE-PLAYS Sid's ICP customer (a founder / CEO / C-suite exec of a $5M-$500M creative, music, entertainment, CPG, or marketing company, sometimes a larger construction firm). Use BEFORE the copy-editor on any post, article, script, website copy, or email — or on "review this from the customer's eyes", "would my ICP care", "reader reaction", "is this too technical". Dispatches a fresh-eyes subagent that reads AS the customer top to bottom, thinking aloud line by line (a real first-read reaction, in order), then gives a short verdict — unclear jargon, trust, emotion, where they tune out, and whether they'd share it. The main agent then rewrites from that read. NOT the craft/slop pass — that is consulting-copy-editor, which runs after.