Claude Skill

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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download techwolf-ai-ai-first-toolkit-plugins_content-studio_skills_write-opinion-2ee7841.zip · 2 KB

techwolf-ai/ai-first-toolkit 129 5 forks MIT Updated 1d ago

Part of techwolf-ai/ai-first-toolkit — 20 skills

Install

skills CLI npx skills add https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/content-studio/skills/write-opinion

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install techwolf-ai-ai-first-toolkit@llmmart

Git git clone https://github.com/techwolf-ai/ai-first-toolkit.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole techwolf-ai/ai-first-toolkit collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Write Opinion Piece

You are helping write an opinion piece for the author.

Before Writing

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
Read guidelines/opinion.md for style rules (includes language and publication targets)
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

Develop the angle and core argument
Write in the language specified in the style guide
Check character count against ~3500 target with wc -m
Save to content/posts/ with type: opinion, stage: 02-drafts

Validation

After saving the draft, run the character count checker:

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:

date -u +"%Y%m%d-%H%M%S"  # For slug
date -u +"%Y-%m-%dT%H:%M:%S.000Z"  # For created/lastUpdated

Files (ai-first-toolkit)

scripts

check-char-count.sh 981 B

#!/bin/bash
# Validates opinion piece character count is near target (~3500 characters).
# Usage: check-char-count.sh <yaml-file>

FILE="$1"
if [ -z "$FILE" ]; then
  echo "Usage: check-char-count.sh <yaml-file>"
  exit 1
fi

if [ ! -f "$FILE" ]; then
  echo "FAIL: File not found: $FILE"
  exit 1
fi

# Extract content field (everything after "content: |-" until next top-level key or EOF)
CONTENT=$(sed -n '/^content: |-/,/^[a-zA-Z]/{ /^content: |-/d; /^[a-zA-Z]/d; p; }' "$FILE")

if [ -z "$CONTENT" ]; then
  echo "FAIL: No content field found in $FILE"
  exit 1
fi

CHAR_COUNT=$(echo "$CONTENT" | wc -m | tr -d ' ')

if [ "$CHAR_COUNT" -lt 3000 ]; then
  echo "WARN: $CHAR_COUNT characters (target: ~3500). Too short by $((3000 - CHAR_COUNT)) characters."
  exit 1
elif [ "$CHAR_COUNT" -gt 4000 ]; then
  echo "WARN: $CHAR_COUNT characters (target: ~3500). Too long by $((CHAR_COUNT - 4000)) characters."
  exit 1
else
  echo "PASS: $CHAR_COUNT characters (target: ~3500)"
fi

SKILL.md 2.7 KB

---
name: write-opinion
description: Write or develop an opinion piece (opiniestuk/op-ed). Use when asked to write opinion articles, newspaper pieces, or similar long-form opinion content.
---

# 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
```