‹ 首页

write-opinion

@techwolf-ai · 收录于 1 周前

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.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add techwolf-ai/ai-first-toolkit/write-opinion
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- techwolf-ai/ai-first-toolkit/write-opinion
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify techwolf-ai/ai-first-toolkit/write-opinion
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
90GitHub stars
~601最小装载
~839含声明引用
~839文本包总量
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 8b3107b

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
  2. Note topics, arguments, and examples already used
  3. Pay attention to recent patterns to avoid repetitive structures, openings, or phrases
  4. Read guidelines/opinion.md for style rules (includes language and publication targets)
  5. 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:

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
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。