write-opinion
Write or develop an opinion piece (opiniestuk/op-ed). Use when asked to write opinion articles, newspaper pieces, or similar long-form opinion content.
git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit /tmp/write-opinion && cp -r /tmp/write-opinion/plugins/content-studio/skills/write-opinion ~/.claude/skills/write-opinionSKILL.md
# Write Opinion Piece You are helping write an opinion piece for the author. ## Before Writing 1. Run `./scripts/print-published.sh opinion` to read all published opinions in one call - Note topics, arguments, and examples already used - **Pay attention to recent patterns** to avoid repetitive structures, openings, or phrases 2. Read `guidelines/opinion.md` for style rules (includes language and publication targets) 3. Read `references/professional-profile.md` for background ## Avoid Repetitive Patterns When reading recent pieces, actively note and vary: **Openings:** If recent pieces start with scene-setting in a specific location, try a different concrete opening (an action, a quote, a surprising fact) **Sentence rhythm:** Vary between punchy short sentences and longer flowing ones **Closing formulas:** Don't repeat the same forward-looking structure - find fresh ways to land the argument **Examples:** Rotate between local and international examples; between industry, government, and everyday life **Rhetorical devices:** If recent pieces use lists or parallel structure heavily, try a different approach The goal is a consistent voice with varied execution. Each piece should feel fresh while still sounding like the author. ## Style Requirements - Target ~3500 characters (use `wc -m` to verify) - Write in the language specified in `guidelines/opinion.md` - Open with concrete scene-setting (time, place, action) - Strong, vivid verbs - Short punchy paragraphs (2-4 sentences) - Double dashes (--) for emphasis - Forward-looking, grounded close ## Process 1. Develop the angle and core argument 2. Write in the language specified in the style guide 3. Check character count against ~3500 target with `wc -m` 4. Save to content/posts/ with type: opinion, stage: 02-drafts ## Validation After saving the draft, run the character count checker: ```bash scripts/check-char-count.sh <yaml-file> ``` Adjust the content if the character count is outside the 3000-4000 range. ## Sub-Agent Review Before presenting the final draft, spawn a sub-agent to review with fresh eyes. The reviewer should: - Check voice consistency against `guidelines/opinion.md` - Verify the opening is concrete (time, place, action) not abstract - Flag any overlap with published opinion pieces - Check for weak verbs, overly long paragraphs, or generic phrasing Incorporate the reviewer's feedback before finalizing. ## Creating New Files Get timestamp first: ```bash date -u +"%Y%m%d-%H%M%S" # For slug date -u +"%Y-%m-%dT%H:%M:%S.000Z" # For created/lastUpdated ```
Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac. Use when the user wants to recall something they did before but can't find it , phrasings like "where did I work on X", "find that session where I…", "when did I last do Y", "pull up the conversation about Z", "that time I built/tried/discussed …". Searches by kind (code/cowork), time range, title, working directory, or free-text content across all transcripts.
Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would reduce iteration. Use when the user asks to "analyse my Claude use", "build a task profile", "what tasks do I do with Claude", "where am I spending tokens", "what skills would help me", or mentions reviewing past sessions for patterns. Produces profile.csv (shareable), explorer.html (personal coaching view with AI-first principle comparison + token-spend chart), and skill-proposals.md.
Personal diagnosis of where your Claude Code + Cowork spend goes. Reads local transcripts, prints your conversation length distribution, marathon share, cache rebuild costs, and per-project diagnosis (good projects and problem projects) right in the terminal. Then offers a deeper dive that fans out parallel Haiku subagents over your most expensive (and most efficient) sessions and writes a tight Markdown report. Use when the user asks "why is my Claude spend so high", "where am I burning tokens", "diagnose my Claude habits", "audit my Claude usage", or asks for a personal token-cost diagnosis.
Analyze, re-engineer, or bootstrap projects to align with AI-first design principles. Use when asked to review, audit, improve, 'ai-firstify', or start a new project. Performs deep analysis across 7 dimensions, actively restructures existing projects, or guides new project setup through discovery questions. Based on the 9 design principles and 7 design patterns from the TechWolf AI-First Bootcamp.
Analyze engagement patterns across published posts to identify what works. Use when asked to review performance, find successful patterns, or optimize future content.
Generate LinkedIn post ideas from external sources (files, URLs, research). Use when the user provides source material (PDFs, URLs, articles) to brainstorm topics. NOT for writing or developing drafts - use write-linkedin-post instead.
Generate opinion piece ideas from recent LinkedIn posts (last 30 days). Use when asked to find opinion topics, brainstorm article ideas, or cross-pollinate content between LinkedIn and opinion pieces.
Entry point for the TechWolf content-studio plugin. Use to understand the workflow, pick the right content skill, or start setup for a new author/repository.