AlphaMoatによると、2026-09時点でCritical Article Writerのダウンロード数は3,832、スター数は4で、AIスキル全体5,078件中2,735位、コンテンツ制作では362件中190位です。
| プラットフォーム | インストール数 | ダウンロード数 | スター数 | コメント |
|---|---|---|---|---|
| ClawHub ↗ | 118 | 3668 | 4 | - |
| SkillHub ↗ | 199 | 3832 | 4 | — |
プラットフォームごとに集計方法と集計時点が異なります。
主文では業界批評、複雑な分析の構成、意見記事、ソーシャル投稿を扱い、会話調の批評、技術的な深さ、構造化された推論を組み合わせます。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-09 | 3832 | — | 4 |
| 2026-08 | 3531 | +4.0% | 4 |
| 2026-07 | 3396 | +8.7% | 4 |
| 2026-06 | 3123 | +4.8% | 4 |
| 2026-05 | 2981 | — | 4 |
| 2026-03 | 2527 | — | 4 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- 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
文章に残る AI らしさを見つけて取り除き、人が書いたように読める文章にします。
AI が書いた文章の典型的な痕跡を見つけ、意味を保ったまま自然な文章に書き直す文章編集スキルです。
AI が生成した文章の痕跡を見つけて取り除く中国語の編集スキルです。
wechat-search は WeChat の人気記事を検索し、関連度、人気、鮮度で結果を整理します。
公開された短編動画の共有リンクからタイトル、概要、口播テキストを抽出し、改写版も作ります。
humanizer は中国語と英語の文章を自然な表現に整えるための編集ガイドです。
Web 小説の各章をファイルに書き、会話では要約と位置だけを返します。
複数のマーケティング手法をひとつのスキルにまとめ、依頼内容に合うモジュールへ振り分けるスキルです。
プロンプトの書き方、システム指示の設計、プロンプト改善を扱う助言型のスキルです。
書き手自身の語り口でブログや長文を書きます。
Professional resume builder with PDF export, ATS optimization, and analysis capabilities. Use when users need to (1) Create new resumes from scratch, (2) Customize/tailor existing resumes for specific roles, (3) Analyze resumes and provide improvement recommendations, (4) Convert resumes to ATS-friendly PDF format. Supports chronological, functional, and combination resume formats.
データ月:2026-09 · ダウンロード数、スター数、インストール数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。