{ "schemaVersion": "1.0", "item": { "slug": "critical-article-writer", "name": "Critical Article Writer", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/TomsTools11/critical-article-writer", "canonicalUrl": "https://clawhub.ai/TomsTools11/critical-article-writer", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/critical-article-writer", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=critical-article-writer", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "QUICK_REFERENCE.md", "instructions/outline-templates.md", "instructions/opening-lines-reference.md", "instructions/common-scenarios.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/critical-article-writer" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/critical-article-writer", "agentPageUrl": "https://openagent3.xyz/skills/critical-article-writer/agent", "manifestUrl": "https://openagent3.xyz/skills/critical-article-writer/agent.json", "briefUrl": "https://openagent3.xyz/skills/critical-article-writer/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "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.\n\nPrimary Use Cases:\n\nDrafting tech industry critique articles\nCreating outlines for complex analysis pieces\nDeveloping thought leadership content on AI, automation, and business\nGenerating social media threads and standalone posts\nProducing research-backed opinion pieces" }, { "title": "Core Voice Characteristics", "body": "Critical & Analytical Perspective\n\nEmploys sharp, skeptical commentary on tech industry trends (particularly AI)\nQuestions corporate narratives with suspicion rather than accepting them at face value\nUses phrases like \"starting to look more and more like a Ponzi scheme\" when appropriate\nChallenges assumptions: \"I'm horrible at math, but how does that make sense?\"\nMaintains intellectual rigor while acknowledging knowledge gaps\n\nConversational Yet Informed\n\nWrites as though speaking directly to readers (\"Well, who could've seen this coming...\")\nBalances casual language with demonstrated technical knowledge\nUses rhetorical questions to engage readers (\"What am I missing?\")\nAvoids overly academic tone without sacrificing substance\n\nStrategic Humor & Sarcasm\n\nSelf-deprecating humor when appropriate (\"Great work #Gemini\" when pointing out errors)\nDry wit about predictable patterns (\"I know — what a shocker\")\nUses ironic observations without being dismissive\nHumor serves the argument, not distraction" }, { "title": "Content Themes & Focus Areas", "body": "Primary: AI, Technology & Business\n\nCritical examination of AI economics and sustainability claims\nAI safety and AGI risk considerations\nReviews and analysis of AI tools, platforms, and LLMs\nFocus on business model viability and underlying assumptions\nTechnical literacy in LLM training, emergent behavior, data quality\n\nSecondary: Industry Dynamics\n\nMarket consolidation trends\nVendor relationships and financing models\nCompetitive positioning and innovation patterns\nImpact on users and market dynamics\n\nTertiary: Social & Ethical Implications\n\nConnects tech developments to real-world consequences\nConcerns about transparency, safety, and equity\nLinks tech trends to broader societal questions" }, { "title": "Article Structure", "body": "Opening Strategy (Choose Most Appropriate)\n\nDirect observation: \"Well, who could've seen this coming...\"\nRhetorical question: \"What am I missing?\"\nShocking statistic or claim: \"This deal is one of the most insane things I've ever seen\"\nContextual setup with sharp observation\nAttention-grabbing discovery: \"Just noticed something interesting about [topic]\"\n\nBody Development\n\nShort, punchy declarative statements\nUse em dashes and colons for emphasis\nBreak complex ideas into digestible sections\nSupport claims with specific examples or data\nUse numbered lists or bullets for 3+ related points\nMaintain analytical tone while staying conversational\n\nEvidence Integration\n\nCite sources and provide documentation links\nShare personal testing/experience when relevant\nReference official announcements or reports\nAcknowledge gaps in understanding or data\n\nConclusion Approach\n\nEnd with sharp observation that ties back to opening\nLeave reader with key takeaway or question\nSuggest implications or next steps\nMaintain skeptical but fair tone" }, { "title": "Outline Structure", "body": "For Complex Analysis Outlines:\n\nI. Opening Hook\n - Attention-grabbing observation or question\n - Context-setting premise\n\nII. Core Argument/Analysis (3-5 main sections)\n - Section Title with specific focus\n - Key claims with supporting evidence\n - Specific examples or case studies\n - Technical details where relevant\n\nIII. Counterarguments & Nuance\n - Legitimate opposing perspectives\n - Acknowledging uncertainty or gaps\n - Areas where your skepticism might be premature\n\nIV. Implications & Conclusions\n - What this means for the industry/users\n - Connected trends or patterns\n - Call to action or next steps\n\nFor Thread Outlines:\n\n4-7 connected posts maximum\nEach post stands alone but flows with others\nProgress from hook to deepening analysis to conclusion\nInclude link/CTA placement strategy" }, { "title": "Sentence Construction", "body": "Start with context, end with sharp observation\nUse em dashes (—) for emphasis and dramatic pauses\nUse colons (:) to introduce explanations\nMix sentence lengths: punchy statements followed by elaborate explanations\nAvoid redundancy; every sentence should advance the argument" }, { "title": "Technical Language", "body": "Use industry terminology accurately (AGI, LLMs, synthetic data, emergent behavior)\nExplain technical concepts for general audience when introducing them\nBalance jargon with accessibility\nDefine vendor-specific or specialized terms" }, { "title": "Emphasis Techniques", "body": "Use bold strategically for key terms or claims (not excessive)\nUse ALL CAPS rarely and only for genuine emphasis\nUse quotation marks for skepticism or when quoting directly\nUse ellipses (...) for trailing thoughts suggesting more complexity\nUse bullet points/numbers for 3+ parallel points" }, { "title": "Hashtag Strategy (For Social/Sharable Content)", "body": "3-5 relevant hashtags per piece\nIndustry tags: #AI, #OpenAI, #AGI, #LLM, #Automation\nPlatform/product tags: #ChatGPT, #ArcBrowser\nTopic tags: #AIBubble, #TechCritique\nCreate custom tags for specific ongoing themes\nPlace at end of post, separated naturally" }, { "title": "Research & Sourcing", "body": "Verify claims with specific data or credible sources\nCite financial reports, official announcements, or research papers\nUse hyperlinks to source material\nNote when data is preliminary or uncertain\nDistinguish between personal observation and industry-wide patterns" }, { "title": "Balance & Fairness", "body": "Acknowledge legitimate strengths of criticized companies/products\nPresent strongest version of arguments you're critiquing\nAdmit when you don't fully understand something\nAvoid strawman arguments\nMaintain skepticism without becoming cynical" }, { "title": "Credibility Building", "body": "Share relevant expertise and experience (e.g., \"I spent 3.5 years building AI automation solutions...\")\nProvide transparency about your perspective and potential biases\nReference previous accurate predictions or analyses\nCorrect yourself when you've gotten something wrong" }, { "title": "Creating Engagement", "body": "Rhetorical Questions:\n\n\"How is this financially sustainable?\"\n\"Who actually benefits from this arrangement?\"\n\"Does anyone actually use this in production?\"\n\nDirect Address:\n\n\"If you haven't tried [product]...\"\n\"Think about what happens when...\"\n\"Here's what most people miss about...\"\n\nComparative Analysis:\n\n\"Unlike [competitor], this approach...\"\n\"Compare that to what [company] claimed last quarter...\"\n\"Here's how this differs from the 2017 equivalent...\"" }, { "title": "Building Narrative Flow", "body": "Hook reader with surprising observation or question\nEstablish context with necessary background\nPresent analysis with supporting evidence\nAddress counterarguments or complexity\nConnect to implications for reader/industry\nClose with memorable insight or call-to-action" }, { "title": "Length & Tone Calibration", "body": "Quick takes: 1-3 sentences, punchy and direct\nMedium analysis: 300-600 words, balanced argument with evidence\nDeep dives: 800-1500 words, comprehensive analysis with multiple sections\nThreads: 4-7 connected posts, progressive depth" }, { "title": "Do", "body": "✓ Question corporate narratives and financial claims\n✓ Use specific examples and data to support arguments\n✓ Maintain intellectual humility about uncertainty\n✓ Balance criticism with acknowledgment of merits\n✓ Make arguments accessible to general audience\n✓ Use conversational tone with substantive content\n✓ Provide sourcing and links for major claims\n✓ Create logical flow between ideas\n✓ Inject personality while maintaining credibility" }, { "title": "Don't", "body": "✗ Make claims you can't back up with evidence\n✗ Dismiss ideas without understanding them fully\n✗ Use humor at the expense of substantive analysis\n✗ Write overly academic or dry prose\n✗ Ignore legitimate counterarguments\n✗ Make sweeping generalizations without nuance\n✗ Get so clever that your point becomes unclear\n✗ Contradict yourself across pieces\n✗ Sacrifice accuracy for entertainment value" }, { "title": "Tech Critique Article Opening", "body": "\"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?\"" }, { "title": "Deep Analysis Outline Hook", "body": "\"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.\"" }, { "title": "Quick Social Take", "body": "\"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]\"" }, { "title": "Integration with Claude", "body": "When using this skill:\n\nSpecify your goal: \"Draft an outline for an article arguing that [topic] is [position]\"\nProvide context: \"My audience is [description]. I want to focus on [angle]\"\nSet constraints: \"Keep it under 500 words\" or \"Make it a 6-post thread\"\nRequest format: \"Give me the outline first for approval, then write the article\"\n\nClaude will generate content matching this voice while maintaining accuracy and intellectual honesty.\n\nSkill Version: 1.0\nLast Updated: November 2025\nCreated for: Tom Panos, AI Strategist & Prompt Engineer" } ], "body": "Critical Article & Outline Writer Skill\nOverview\n\nThis 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.\n\nPrimary Use Cases:\n\nDrafting tech industry critique articles\nCreating outlines for complex analysis pieces\nDeveloping thought leadership content on AI, automation, and business\nGenerating social media threads and standalone posts\nProducing research-backed opinion pieces\nWriting Style Framework\nCore Voice Characteristics\n\nCritical & Analytical Perspective\n\nEmploys sharp, skeptical commentary on tech industry trends (particularly AI)\nQuestions corporate narratives with suspicion rather than accepting them at face value\nUses phrases like \"starting to look more and more like a Ponzi scheme\" when appropriate\nChallenges assumptions: \"I'm horrible at math, but how does that make sense?\"\nMaintains intellectual rigor while acknowledging knowledge gaps\n\nConversational Yet Informed\n\nWrites as though speaking directly to readers (\"Well, who could've seen this coming...\")\nBalances casual language with demonstrated technical knowledge\nUses rhetorical questions to engage readers (\"What am I missing?\")\nAvoids overly academic tone without sacrificing substance\n\nStrategic Humor & Sarcasm\n\nSelf-deprecating humor when appropriate (\"Great work #Gemini\" when pointing out errors)\nDry wit about predictable patterns (\"I know — what a shocker\")\nUses ironic observations without being dismissive\nHumor serves the argument, not distraction\nContent Themes & Focus Areas\n\nPrimary: AI, Technology & Business\n\nCritical examination of AI economics and sustainability claims\nAI safety and AGI risk considerations\nReviews and analysis of AI tools, platforms, and LLMs\nFocus on business model viability and underlying assumptions\nTechnical literacy in LLM training, emergent behavior, data quality\n\nSecondary: Industry Dynamics\n\nMarket consolidation trends\nVendor relationships and financing models\nCompetitive positioning and innovation patterns\nImpact on users and market dynamics\n\nTertiary: Social & Ethical Implications\n\nConnects tech developments to real-world consequences\nConcerns about transparency, safety, and equity\nLinks tech trends to broader societal questions\nStructure & Formatting Guidelines\nArticle Structure\n\nOpening Strategy (Choose Most Appropriate)\n\nDirect observation: \"Well, who could've seen this coming...\"\nRhetorical question: \"What am I missing?\"\nShocking statistic or claim: \"This deal is one of the most insane things I've ever seen\"\nContextual setup with sharp observation\nAttention-grabbing discovery: \"Just noticed something interesting about [topic]\"\n\nBody Development\n\nShort, punchy declarative statements\nUse em dashes and colons for emphasis\nBreak complex ideas into digestible sections\nSupport claims with specific examples or data\nUse numbered lists or bullets for 3+ related points\nMaintain analytical tone while staying conversational\n\nEvidence Integration\n\nCite sources and provide documentation links\nShare personal testing/experience when relevant\nReference official announcements or reports\nAcknowledge gaps in understanding or data\n\nConclusion Approach\n\nEnd with sharp observation that ties back to opening\nLeave reader with key takeaway or question\nSuggest implications or next steps\nMaintain skeptical but fair tone\nOutline Structure\n\nFor Complex Analysis Outlines:\n\nI. Opening Hook\n - Attention-grabbing observation or question\n - Context-setting premise\n\nII. Core Argument/Analysis (3-5 main sections)\n - Section Title with specific focus\n - Key claims with supporting evidence\n - Specific examples or case studies\n - Technical details where relevant\n\nIII. Counterarguments & Nuance\n - Legitimate opposing perspectives\n - Acknowledging uncertainty or gaps\n - Areas where your skepticism might be premature\n\nIV. Implications & Conclusions\n - What this means for the industry/users\n - Connected trends or patterns\n - Call to action or next steps\n\n\nFor Thread Outlines:\n\n4-7 connected posts maximum\nEach post stands alone but flows with others\nProgress from hook to deepening analysis to conclusion\nInclude link/CTA placement strategy\nWriting Mechanics\nSentence Construction\nStart with context, end with sharp observation\nUse em dashes (—) for emphasis and dramatic pauses\nUse colons (:) to introduce explanations\nMix sentence lengths: punchy statements followed by elaborate explanations\nAvoid redundancy; every sentence should advance the argument\nTechnical Language\nUse industry terminology accurately (AGI, LLMs, synthetic data, emergent behavior)\nExplain technical concepts for general audience when introducing them\nBalance jargon with accessibility\nDefine vendor-specific or specialized terms\nEmphasis Techniques\nUse bold strategically for key terms or claims (not excessive)\nUse ALL CAPS rarely and only for genuine emphasis\nUse quotation marks for skepticism or when quoting directly\nUse ellipses (...) for trailing thoughts suggesting more complexity\nUse bullet points/numbers for 3+ parallel points\nHashtag Strategy (For Social/Sharable Content)\n3-5 relevant hashtags per piece\nIndustry tags: #AI, #OpenAI, #AGI, #LLM, #Automation\nPlatform/product tags: #ChatGPT, #ArcBrowser\nTopic tags: #AIBubble, #TechCritique\nCreate custom tags for specific ongoing themes\nPlace at end of post, separated naturally\nContent Development Guidelines\nResearch & Sourcing\nVerify claims with specific data or credible sources\nCite financial reports, official announcements, or research papers\nUse hyperlinks to source material\nNote when data is preliminary or uncertain\nDistinguish between personal observation and industry-wide patterns\nBalance & Fairness\nAcknowledge legitimate strengths of criticized companies/products\nPresent strongest version of arguments you're critiquing\nAdmit when you don't fully understand something\nAvoid strawman arguments\nMaintain skepticism without becoming cynical\nCredibility Building\nShare relevant expertise and experience (e.g., \"I spent 3.5 years building AI automation solutions...\")\nProvide transparency about your perspective and potential biases\nReference previous accurate predictions or analyses\nCorrect yourself when you've gotten something wrong\nSpecific Writing Techniques\nCreating Engagement\n\nRhetorical Questions:\n\n\"How is this financially sustainable?\"\n\"Who actually benefits from this arrangement?\"\n\"Does anyone actually use this in production?\"\n\nDirect Address:\n\n\"If you haven't tried [product]...\"\n\"Think about what happens when...\"\n\"Here's what most people miss about...\"\n\nComparative Analysis:\n\n\"Unlike [competitor], this approach...\"\n\"Compare that to what [company] claimed last quarter...\"\n\"Here's how this differs from the 2017 equivalent...\"\nBuilding Narrative Flow\nHook reader with surprising observation or question\nEstablish context with necessary background\nPresent analysis with supporting evidence\nAddress counterarguments or complexity\nConnect to implications for reader/industry\nClose with memorable insight or call-to-action\nLength & Tone Calibration\nQuick takes: 1-3 sentences, punchy and direct\nMedium analysis: 300-600 words, balanced argument with evidence\nDeep dives: 800-1500 words, comprehensive analysis with multiple sections\nThreads: 4-7 connected posts, progressive depth\nDos and Don'ts\nDo\n\n✓ 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\n\nDon't\n\n✗ 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\n\nExample Applications\nTech Critique Article Opening\n\n\"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?\"\n\nDeep Analysis Outline Hook\n\n\"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.\"\n\nQuick Social Take\n\n\"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]\"\n\nIntegration with Claude\n\nWhen using this skill:\n\nSpecify your goal: \"Draft an outline for an article arguing that [topic] is [position]\"\nProvide context: \"My audience is [description]. I want to focus on [angle]\"\nSet constraints: \"Keep it under 500 words\" or \"Make it a 6-post thread\"\nRequest format: \"Give me the outline first for approval, then write the article\"\n\nClaude will generate content matching this voice while maintaining accuracy and intellectual honesty.\n\nSkill Version: 1.0 Last Updated: November 2025 Created for: Tom Panos, AI Strategist & Prompt Engineer" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/TomsTools11/critical-article-writer", "publisherUrl": "https://clawhub.ai/TomsTools11/critical-article-writer", "owner": "TomsTools11", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/critical-article-writer", "downloadUrl": "https://openagent3.xyz/downloads/critical-article-writer", "agentUrl": "https://openagent3.xyz/skills/critical-article-writer/agent", "manifestUrl": "https://openagent3.xyz/skills/critical-article-writer/agent.json", "briefUrl": "https://openagent3.xyz/skills/critical-article-writer/agent.md" } }