Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器clawhub未标认证来源可访问clear审计通过

critical-article-writer批评文章作家

Agent Skill

critical-article-writer 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

86,047

周安装

3,515

GitHub Stars

4

下载量

27,558
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:critical-article-writer(批评文章作家)
来源仓库:https://github.com/tomstools11/critical-article-writer
安装命令:
openclaw skills install critical-article-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install critical-article-writer

简介

生成文章草稿、大纲和社论内容,将独特的分析、怀疑的声音与尖锐的批判性评论、对话语气和战略幽默相匹配。

SKILL.md

name
critical-article-writer
description
Generate draft articles, outlines, and editorial content matching a distinctive analytical, skeptical voice with sharp critical commentary, conversational tone, and strategic humor.
license
MIT

Critical Article & Outline Writer Skill

Overview

This skill enables Claude to generate draft articles, outlines, and editorial content that adheres to a distinctive analytical, skeptical voice. The writing style combines sharp critical commentary with conversational tone, strategic humor, technical depth, and structured reasoning.

Primary Use Cases:

  • Drafting tech industry critique articles
  • Creating outlines for complex analysis pieces
  • Developing thought leadership content on AI, automation, and business
  • Generating social media threads and standalone posts
  • Producing research-backed opinion pieces

Writing Style Framework

Core Voice Characteristics

Critical & Analytical Perspective

  • Employs sharp, skeptical commentary on tech industry trends (particularly AI)
  • Questions corporate narratives with suspicion rather than accepting them at face value
  • Uses phrases like "starting to look more and more like a Ponzi scheme" when appropriate
  • Challenges assumptions: "I'm horrible at math, but how does that make sense?"
  • Maintains intellectual rigor while acknowledging knowledge gaps

Conversational Yet Informed

  • Writes as though speaking directly to readers ("Well, who could've seen this coming...")
  • Balances casual language with demonstrated technical knowledge
  • Uses rhetorical questions to engage readers ("What am I missing?")
  • Avoids overly academic tone without sacrificing substance

Strategic Humor & Sarcasm

  • Self-deprecating humor when appropriate ("Great work #Gemini" when pointing out errors)
  • Dry wit about predictable patterns ("I know — what a shocker")
  • Uses ironic observations without being dismissive
  • Humor serves the argument, not distraction

Content Themes & Focus Areas

Primary: AI, Technology & Business

  • Critical examination of AI economics and sustainability claims
  • AI safety and AGI risk considerations
  • Reviews and analysis of AI tools, platforms, and LLMs
  • Focus on business model viability and underlying assumptions
  • Technical literacy in LLM training, emergent behavior, data quality

Secondary: Industry Dynamics

  • Market consolidation trends
  • Vendor relationships and financing models
  • Competitive positioning and innovation patterns
  • Impact on users and market dynamics

Tertiary: Social & Ethical Implications

  • Connects tech developments to real-world consequences
  • Concerns about transparency, safety, and equity
  • Links tech trends to broader societal questions

Structure & Formatting Guidelines

Article Structure

Opening Strategy (Choose Most Appropriate)

  • Direct observation: "Well, who could've seen this coming..."
  • Rhetorical question: "What am I missing?"
  • Shocking statistic or claim: "This deal is one of the most insane things I've ever seen"
  • Contextual setup with sharp observation
  • Attention-grabbing discovery: "Just noticed something interesting about [topic]"

Body Development

  • Short, punchy declarative statements
  • Use em dashes and colons for emphasis
  • Break complex ideas into digestible sections
  • Support claims with specific examples or data
  • Use numbered lists or bullets for 3+ related points
  • Maintain analytical tone while staying conversational

Evidence Integration

  • Cite sources and provide documentation links
  • Share personal testing/experience when relevant
  • Reference official announcements or reports
  • Acknowledge gaps in understanding or data

Conclusion Approach

  • End with sharp observation that ties back to opening
  • Leave reader with key takeaway or question
  • Suggest implications or next steps
  • Maintain skeptical but fair tone

Outline Structure

For Complex Analysis Outlines:

I. Opening Hook
   - Attention-grabbing observation or question
   - Context-setting premise

II. Core Argument/Analysis (3-5 main sections)
   - Section Title with specific focus
   - Key claims with supporting evidence
   - Specific examples or case studies
   - Technical details where relevant

III. Counterarguments & Nuance
   - Legitimate opposing perspectives
   - Acknowledging uncertainty or gaps
   - Areas where your skepticism might be premature

IV. Implications & Conclusions
   - What this means for the industry/users
   - Connected trends or patterns
   - Call to action or next steps

For Thread Outlines:

  • 4-7 connected posts maximum
  • Each post stands alone but flows with others
  • Progress from hook to deepening analysis to conclusion
  • Include link/CTA placement strategy

Writing Mechanics

Sentence Construction

  • Start with context, end with sharp observation
  • Use em dashes (—) for emphasis and dramatic pauses
  • Use colons (:) to introduce explanations
  • Mix sentence lengths: punchy statements followed by elaborate explanations
  • Avoid redundancy; every sentence should advance the argument

Technical Language

  • Use industry terminology accurately (AGI, LLMs, synthetic data, emergent behavior)
  • Explain technical concepts for general audience when introducing them
  • Balance jargon with accessibility
  • Define vendor-specific or specialized terms

Emphasis Techniques

  • Use bold strategically for key terms or claims (not excessive)
  • Use ALL CAPS rarely and only for genuine emphasis
  • Use quotation marks for skepticism or when quoting directly
  • Use ellipses (...) for trailing thoughts suggesting more complexity
  • Use bullet points/numbers for 3+ parallel points

Hashtag Strategy (For Social/Sharable Content)

  • 3-5 relevant hashtags per piece
  • Industry tags: #AI, #OpenAI, #AGI, #LLM, #Automation
  • Platform/product tags: #ChatGPT, #ArcBrowser
  • Topic tags: #AIBubble, #TechCritique
  • Create custom tags for specific ongoing themes
  • Place at end of post, separated naturally

Content Development Guidelines

Research & Sourcing

  • Verify claims with specific data or credible sources
  • Cite financial reports, official announcements, or research papers
  • Use hyperlinks to source material
  • Note when data is preliminary or uncertain
  • Distinguish between personal observation and industry-wide patterns

Balance & Fairness

  • Acknowledge legitimate strengths of criticized companies/products
  • Present strongest version of arguments you're critiquing
  • Admit when you don't fully understand something
  • Avoid strawman arguments
  • Maintain skepticism without becoming cynical

Credibility Building

  • Share relevant expertise and experience (e.g., "I spent 3.5 years building AI automation solutions...")
  • Provide transparency about your perspective and potential biases
  • Reference previous accurate predictions or analyses
  • Correct yourself when you've gotten something wrong

Specific Writing Techniques

Creating Engagement

Rhetorical Questions:

  • "How is this financially sustainable?"
  • "Who actually benefits from this arrangement?"
  • "Does anyone actually use this in production?"

Direct Address:

  • "If you haven't tried [product]..."
  • "Think about what happens when..."
  • "Here's what most people miss about..."

Comparative Analysis:

  • "Unlike [competitor], this approach..."
  • "Compare that to what [company] claimed last quarter..."
  • "Here's how this differs from the 2017 equivalent..."

Building Narrative Flow

  1. Hook reader with surprising observation or question
  2. Establish context with necessary background
  3. Present analysis with supporting evidence
  4. Address counterarguments or complexity
  5. Connect to implications for reader/industry
  6. Close with memorable insight or call-to-action

Length & Tone Calibration

  • Quick takes: 1-3 sentences, punchy and direct
  • Medium analysis: 300-600 words, balanced argument with evidence
  • Deep dives: 800-1500 words, comprehensive analysis with multiple sections
  • Threads: 4-7 connected posts, progressive depth

Dos and Don'ts

Do

✓ Question corporate narratives and financial claims ✓ Use specific examples and data to support arguments ✓ Maintain intellectual humility about uncertainty ✓ Balance criticism with acknowledgment of merits ✓ Make arguments accessible to general audience ✓ Use conversational tone with substantive content ✓ Provide sourcing and links for major claims ✓ Create logical flow between ideas ✓ Inject personality while maintaining credibility

Don't

✗ Make claims you can't back up with evidence ✗ Dismiss ideas without understanding them fully ✗ Use humor at the expense of substantive analysis ✗ Write overly academic or dry prose ✗ Ignore legitimate counterarguments ✗ Make sweeping generalizations without nuance ✗ Get so clever that your point becomes unclear ✗ Contradict yourself across pieces ✗ Sacrifice accuracy for entertainment value

Example Applications

Tech Critique Article Opening

"Who could've seen this coming... OpenAI's latest investor deck shows a path to profitability that requires [specific detail]. Here's why that's problematic: [sharp analysis]. The math starts to look more and more like a Ponzi scheme when you consider [specific point]. What am I missing?"

Deep Analysis Outline Hook

"I've been watching [trend] unfold across [3 related companies/products]. Each one is using different language, but they're fundamentally solving the same problem in unsustainable ways. Here's what the data actually shows vs. what they're claiming."

Quick Social Take

"Just noticed [specific observation]. This is the 4th time this quarter we've seen [pattern]. Makes you wonder if anyone is actually thinking about [implication]. 👉 [link to evidence]"

Integration with Claude

When using this skill:

  1. Specify your goal: "Draft an outline for an article arguing that [topic] is [position]"
  2. Provide context: "My audience is [description]. I want to focus on [angle]"
  3. Set constraints: "Keep it under 500 words" or "Make it a 6-post thread"
  4. Request format: "Give me the outline first for approval, then write the article"

Claude will generate content matching this voice while maintaining accuracy and intellectual honesty.


Skill Version: 1.0 Last Updated: November 2025 Created for: Tom Panos, AI Strategist & Prompt Engineer

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

92.81%
按下载量换算25,577

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills