{
  "schemaVersion": "1.0",
  "item": {
    "slug": "content-research-writer-cn",
    "name": "Content Research Writer Cn",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/guohongbin-git/content-research-writer-cn",
    "canonicalUrl": "https://clawhub.ai/guohongbin-git/content-research-writer-cn",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/content-research-writer-cn",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=content-research-writer-cn",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "_meta.json"
    ],
    "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. 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. 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-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.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/content-research-writer-cn"
    },
    "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/content-research-writer-cn",
    "agentPageUrl": "https://openagent3.xyz/skills/content-research-writer-cn/agent",
    "manifestUrl": "https://openagent3.xyz/skills/content-research-writer-cn/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/content-research-writer-cn/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. 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. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Content Research Writer",
        "body": "This skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style."
      },
      {
        "title": "When to Use This Skill",
        "body": "Writing blog posts, articles, or newsletters\nCreating educational content or tutorials\nDrafting thought leadership pieces\nResearching and writing case studies\nProducing technical documentation with sources\nWriting with proper citations and references\nImproving hooks and introductions\nGetting section-by-section feedback while writing"
      },
      {
        "title": "What This Skill Does",
        "body": "Collaborative Outlining: Helps you structure ideas into coherent outlines\nResearch Assistance: Finds relevant information and adds citations\nHook Improvement: Strengthens your opening to capture attention\nSection Feedback: Reviews each section as you write\nVoice Preservation: Maintains your writing style and tone\nCitation Management: Adds and formats references properly\nIterative Refinement: Helps you improve through multiple drafts"
      },
      {
        "title": "Setup Your Writing Environment",
        "body": "Create a dedicated folder for your article:\n\nmkdir ~/writing/my-article-title\ncd ~/writing/my-article-title\n\nCreate your draft file:\n\ntouch article-draft.md\n\nOpen Claude Code from this directory and start writing."
      },
      {
        "title": "Basic Workflow",
        "body": "Start with an outline:\n\nHelp me create an outline for an article about [topic]\n\nResearch and add citations:\n\nResearch [specific topic] and add citations to my outline\n\nImprove the hook:\n\nHere's my introduction. Help me make the hook more compelling.\n\nGet section feedback:\n\nI just finished the \"Why This Matters\" section. Review it and give feedback.\n\nRefine and polish:\n\nReview the full draft for flow, clarity, and consistency."
      },
      {
        "title": "Instructions",
        "body": "When a user requests writing assistance:\n\nUnderstand the Writing Project\nAsk clarifying questions:\n\nWhat's the topic and main argument?\nWho's the target audience?\nWhat's the desired length/format?\nWhat's your goal? (educate, persuade, entertain, explain)\nAny existing research or sources to include?\nWhat's your writing style? (formal, conversational, technical)\n\n\n\nCollaborative Outlining\nHelp structure the content:\n# Article Outline: [Title]\n\n## Hook\n- [Opening line/story/statistic]\n- [Why reader should care]\n\n## Introduction\n- Context and background\n- Problem statement\n- What this article covers\n\n## Main Sections\n\n### Section 1: [Title]\n- Key point A\n- Key point B\n- Example/evidence\n- [Research needed: specific topic]\n\n### Section 2: [Title]\n- Key point C\n- Key point D\n- Data/citation needed\n\n### Section 3: [Title]\n- Key point E\n- Counter-arguments\n- Resolution\n\n## Conclusion\n- Summary of main points\n- Call to action\n- Final thought\n\n## Research To-Do\n- [ ] Find data on [topic]\n- [ ] Get examples of [concept]\n- [ ] Source citation for [claim]\n\nIterate on outline:\n\nAdjust based on feedback\nEnsure logical flow\nIdentify research gaps\nMark sections for deep dives\n\n\n\nConduct Research\nWhen user requests research on a topic:\n\nSearch for relevant information\nFind credible sources\nExtract key facts, quotes, and data\nAdd citations in requested format\n\nExample output:\n## Research: AI Impact on Productivity\n\nKey Findings:\n\n1. **Productivity Gains**: Studies show 40% time savings for \n   content creation tasks [1]\n\n2. **Adoption Rates**: 67% of knowledge workers use AI tools \n   weekly [2]\n\n3. **Expert Quote**: \"AI augments rather than replaces human \n   creativity\" - Dr. Jane Smith, MIT [3]\n\nCitations:\n[1] McKinsey Global Institute. (2024). \"The Economic Potential \n    of Generative AI\"\n[2] Stack Overflow Developer Survey (2024)\n[3] Smith, J. (2024). MIT Technology Review interview\n\nAdded to outline under Section 2.\n\n\n\nImprove Hooks\nWhen user shares an introduction, analyze and strengthen:\nCurrent Hook Analysis:\n\nWhat works: [positive elements]\nWhat could be stronger: [areas for improvement]\nEmotional impact: [current vs. potential]\n\nSuggested Alternatives:\nOption 1: [Bold statement]\n\n[Example]\nWhy it works: [explanation]\n\nOption 2: [Personal story]\n\n[Example]\nWhy it works: [explanation]\n\nOption 3: [Surprising data]\n\n[Example]\nWhy it works: [explanation]\n\nQuestions to hook:\n\nDoes it create curiosity?\nDoes it promise value?\nIs it specific enough?\nDoes it match the audience?\n\n\n\nProvide Section-by-Section Feedback\nAs user writes each section, review for:\n# Feedback: [Section Name]\n\n## What Works Well ✓\n- [Strength 1]\n- [Strength 2]\n- [Strength 3]\n\n## Suggestions for Improvement\n\n### Clarity\n- [Specific issue] → [Suggested fix]\n- [Complex sentence] → [Simpler alternative]\n\n### Flow\n- [Transition issue] → [Better connection]\n- [Paragraph order] → [Suggested reordering]\n\n### Evidence\n- [Claim needing support] → [Add citation or example]\n- [Generic statement] → [Make more specific]\n\n### Style\n- [Tone inconsistency] → [Match your voice better]\n- [Word choice] → [Stronger alternative]\n\n## Specific Line Edits\n\nOriginal:\n> [Exact quote from draft]\n\nSuggested:\n> [Improved version]\n\nWhy: [Explanation]\n\n## Questions to Consider\n- [Thought-provoking question 1]\n- [Thought-provoking question 2]\n\nReady to move to next section!\n\n\n\nPreserve Writer's Voice\nImportant principles:\n\nLearn their style: Read existing writing samples\nSuggest, don't replace: Offer options, not directives\nMatch tone: Formal, casual, technical, friendly\nRespect choices: If they prefer their version, support it\nEnhance, don't override: Make their writing better, not different\n\nAsk periodically:\n\n\"Does this sound like you?\"\n\"Is this the right tone?\"\n\"Should I be more/less [formal/casual/technical]?\"\n\n\n\nCitation Management\nHandle references based on user preference:\nInline Citations:\nStudies show 40% productivity improvement (McKinsey, 2024).\n\nNumbered References:\nStudies show 40% productivity improvement [1].\n\n[1] McKinsey Global Institute. (2024)...\n\nFootnote Style:\nStudies show 40% productivity improvement^1\n\n^1: McKinsey Global Institute. (2024)...\n\nMaintain a running citations list:\n## References\n\n1. Author. (Year). \"Title\". Publication.\n2. Author. (Year). \"Title\". Publication.\n...\n\n\n\nFinal Review and Polish\nWhen draft is complete, provide comprehensive feedback:\n# Full Draft Review\n\n## Overall Assessment\n\n**Strengths**:\n- [Major strength 1]\n- [Major strength 2]\n- [Major strength 3]\n\n**Impact**: [Overall effectiveness assessment]\n\n## Structure & Flow\n- [Comments on organization]\n- [Transition quality]\n- [Pacing assessment]\n\n## Content Quality\n- [Argument strength]\n- [Evidence sufficiency]\n- [Example effectiveness]\n\n## Technical Quality\n- Grammar and mechanics: [assessment]\n- Consistency: [assessment]\n- Citations: [completeness check]\n\n## Readability\n- Clarity score: [evaluation]\n- Sentence variety: [evaluation]\n- Paragraph length: [evaluation]\n\n## Final Polish Suggestions\n\n1. **Introduction**: [Specific improvements]\n2. **Body**: [Specific improvements]\n3. **Conclusion**: [Specific improvements]\n4. **Title**: [Options if needed]\n\n## Pre-Publish Checklist\n- [ ] All claims sourced\n- [ ] Citations formatted\n- [ ] Examples clear\n- [ ] Transitions smooth\n- [ ] Call to action present\n- [ ] Proofread for typos\n\nReady to publish! 🚀"
      },
      {
        "title": "Example 1: Teresa Torres's Workflow",
        "body": "User: \"I'm writing an article about continuous discovery. Help me create an outline.\"\n\nProcess:\n\nCollaborates on outline structure\nIdentifies research needs\nUser starts writing introduction\nReviews and improves the hook\nUser writes each section\nProvides feedback after each section\nConducts research and adds citations\nFinal review of complete draft\nPolish and prep for publishing\n\nResult: Well-researched, properly cited article written in Teresa's voice with strong structure and flow."
      },
      {
        "title": "Example 2: Research-Heavy Article",
        "body": "User: \"I'm writing about AI's impact on product management. Help me find current data and examples.\"\n\nOutput:\n\n## Research Compiled\n\n### Recent Data\n- Gartner: 80% of PMs will use AI tools by 2025 [1]\n- Survey: 45% report faster feature shipping [2]\n- Case study: Airbnb's AI-assisted prioritization [3]\n\n### Expert Quotes\n- \"AI amplifies PM judgment, not replaces it\" - Marty Cagan\n- [Additional quotes with citations]\n\n### Real Examples\n1. **Company A**: Used AI for user research synthesis\n   - Result: 60% time savings\n   - Source: [citation]\n\n2. **Company B**: AI-powered roadmap analysis\n   - Result: Better stakeholder alignment\n   - Source: [citation]\n\nAll added to your outline with proper citations."
      },
      {
        "title": "Example 3: Hook Improvement",
        "body": "User's Original Hook:\n\n\"Product management is changing because of AI. In this article, I'll discuss some ways AI affects product managers.\"\n\nImproved Options:\n\nOption 1 (Data-driven):\n\n\"Last month, I asked AI to analyze 500 customer interviews. It took 30 minutes instead of 3 weeks. Product management will never be the same.\"\n\nOption 2 (Question):\n\n\"What if you could talk to every customer, read every review, and analyze every support ticket—all before your morning coffee?\"\n\nOption 3 (Story):\n\n\"Sarah spent two weeks building the wrong feature. Not because she didn't understand her users, but because she couldn't process the hundreds of interviews fast enough to spot the pattern.\""
      },
      {
        "title": "Example 4: Section Feedback",
        "body": "User: \"Just finished my 'Common Mistakes' section. Thoughts?\"\n\nResponse:\n\n# Feedback: Common Mistakes Section\n\n## What Works Well ✓\n- Strong examples (the Slack notification story)\n- Clear structure (3 mistakes, clean layout)\n- Practical advice for each mistake\n\n## Suggestions\n\n### Make It More Specific\nYour second point says \"Bad prioritization\" but could be stronger:\n\nCurrent:\n> \"Many teams prioritize badly by focusing on features instead of outcomes.\"\n\nSuggested:\n> \"I've watched teams ship 14 features in a quarter yet move none of their key metrics. They prioritized activity over progress.\"\n\n### Add Data\nThe third mistake would benefit from evidence:\n> \"[Add citation]: Studies show teams without regular user contact are 3x more likely to build unused features [needs source]\"\n\n### Flow Improvement\nConsider reordering: Mistake 3 → Mistake 2 → Mistake 1\nThis builds from small to big impact.\n\nReady for the next section!"
      },
      {
        "title": "Blog Post Workflow",
        "body": "Outline together\nResearch key points\nWrite introduction → get feedback\nWrite body sections → feedback each\nWrite conclusion → final review\nPolish and edit"
      },
      {
        "title": "Newsletter Workflow",
        "body": "Discuss hook ideas\nQuick outline (shorter format)\nDraft in one session\nReview for clarity and links\nQuick polish"
      },
      {
        "title": "Technical Tutorial Workflow",
        "body": "Outline steps\nWrite code examples\nAdd explanations\nTest instructions\nAdd troubleshooting section\nFinal review for accuracy"
      },
      {
        "title": "Thought Leadership Workflow",
        "body": "Brainstorm unique angle\nResearch existing perspectives\nDevelop your thesis\nWrite with strong POV\nAdd supporting evidence\nCraft compelling conclusion"
      },
      {
        "title": "Pro Tips",
        "body": "Work in VS Code: Better than web Claude for long-form writing\nOne section at a time: Get feedback incrementally\nSave research separately: Keep a research.md file\nVersion your drafts: article-v1.md, article-v2.md, etc.\nRead aloud: Use feedback to identify clunky sentences\nSet deadlines: \"I want to finish the draft today\"\nTake breaks: Write, get feedback, pause, revise"
      },
      {
        "title": "File Organization",
        "body": "Recommended structure for writing projects:\n\n~/writing/article-name/\n├── outline.md          # Your outline\n├── research.md         # All research and citations\n├── draft-v1.md         # First draft\n├── draft-v2.md         # Revised draft\n├── final.md            # Publication-ready\n├── feedback.md         # Collected feedback\n└── sources/            # Reference materials\n    ├── study1.pdf\n    └── article2.md"
      },
      {
        "title": "For Research",
        "body": "Verify sources before citing\nUse recent data when possible\nBalance different perspectives\nLink to original sources"
      },
      {
        "title": "For Feedback",
        "body": "Be specific about what you want: \"Is this too technical?\"\nShare your concerns: \"I'm worried this section drags\"\nAsk questions: \"Does this flow logically?\"\nRequest alternatives: \"What's another way to explain this?\""
      },
      {
        "title": "For Voice",
        "body": "Share examples of your writing\nSpecify tone preferences\nPoint out good matches: \"That sounds like me!\"\nFlag mismatches: \"Too formal for my style\""
      },
      {
        "title": "Related Use Cases",
        "body": "Creating social media posts from articles\nAdapting content for different audiences\nWriting email newsletters\nDrafting technical documentation\nCreating presentation content\nWriting case studies\nDeveloping course outlines"
      }
    ],
    "body": "Content Research Writer\n\nThis skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style.\n\nWhen to Use This Skill\nWriting blog posts, articles, or newsletters\nCreating educational content or tutorials\nDrafting thought leadership pieces\nResearching and writing case studies\nProducing technical documentation with sources\nWriting with proper citations and references\nImproving hooks and introductions\nGetting section-by-section feedback while writing\nWhat This Skill Does\nCollaborative Outlining: Helps you structure ideas into coherent outlines\nResearch Assistance: Finds relevant information and adds citations\nHook Improvement: Strengthens your opening to capture attention\nSection Feedback: Reviews each section as you write\nVoice Preservation: Maintains your writing style and tone\nCitation Management: Adds and formats references properly\nIterative Refinement: Helps you improve through multiple drafts\nHow to Use\nSetup Your Writing Environment\n\nCreate a dedicated folder for your article:\n\nmkdir ~/writing/my-article-title\ncd ~/writing/my-article-title\n\n\nCreate your draft file:\n\ntouch article-draft.md\n\n\nOpen Claude Code from this directory and start writing.\n\nBasic Workflow\nStart with an outline:\nHelp me create an outline for an article about [topic]\n\nResearch and add citations:\nResearch [specific topic] and add citations to my outline\n\nImprove the hook:\nHere's my introduction. Help me make the hook more compelling.\n\nGet section feedback:\nI just finished the \"Why This Matters\" section. Review it and give feedback.\n\nRefine and polish:\nReview the full draft for flow, clarity, and consistency.\n\nInstructions\n\nWhen a user requests writing assistance:\n\nUnderstand the Writing Project\n\nAsk clarifying questions:\n\nWhat's the topic and main argument?\nWho's the target audience?\nWhat's the desired length/format?\nWhat's your goal? (educate, persuade, entertain, explain)\nAny existing research or sources to include?\nWhat's your writing style? (formal, conversational, technical)\n\nCollaborative Outlining\n\nHelp structure the content:\n\n# Article Outline: [Title]\n\n## Hook\n- [Opening line/story/statistic]\n- [Why reader should care]\n\n## Introduction\n- Context and background\n- Problem statement\n- What this article covers\n\n## Main Sections\n\n### Section 1: [Title]\n- Key point A\n- Key point B\n- Example/evidence\n- [Research needed: specific topic]\n\n### Section 2: [Title]\n- Key point C\n- Key point D\n- Data/citation needed\n\n### Section 3: [Title]\n- Key point E\n- Counter-arguments\n- Resolution\n\n## Conclusion\n- Summary of main points\n- Call to action\n- Final thought\n\n## Research To-Do\n- [ ] Find data on [topic]\n- [ ] Get examples of [concept]\n- [ ] Source citation for [claim]\n\n\nIterate on outline:\n\nAdjust based on feedback\nEnsure logical flow\nIdentify research gaps\nMark sections for deep dives\n\nConduct Research\n\nWhen user requests research on a topic:\n\nSearch for relevant information\nFind credible sources\nExtract key facts, quotes, and data\nAdd citations in requested format\n\nExample output:\n\n## Research: AI Impact on Productivity\n\nKey Findings:\n\n1. **Productivity Gains**: Studies show 40% time savings for \n   content creation tasks [1]\n\n2. **Adoption Rates**: 67% of knowledge workers use AI tools \n   weekly [2]\n\n3. **Expert Quote**: \"AI augments rather than replaces human \n   creativity\" - Dr. Jane Smith, MIT [3]\n\nCitations:\n[1] McKinsey Global Institute. (2024). \"The Economic Potential \n    of Generative AI\"\n[2] Stack Overflow Developer Survey (2024)\n[3] Smith, J. (2024). MIT Technology Review interview\n\nAdded to outline under Section 2.\n\n\nImprove Hooks\n\nWhen user shares an introduction, analyze and strengthen:\n\nCurrent Hook Analysis:\n\nWhat works: [positive elements]\nWhat could be stronger: [areas for improvement]\nEmotional impact: [current vs. potential]\n\nSuggested Alternatives:\n\nOption 1: [Bold statement]\n\n[Example] Why it works: [explanation]\n\nOption 2: [Personal story]\n\n[Example] Why it works: [explanation]\n\nOption 3: [Surprising data]\n\n[Example] Why it works: [explanation]\n\nQuestions to hook:\n\nDoes it create curiosity?\nDoes it promise value?\nIs it specific enough?\nDoes it match the audience?\n\nProvide Section-by-Section Feedback\n\nAs user writes each section, review for:\n\n# Feedback: [Section Name]\n\n## What Works Well ✓\n- [Strength 1]\n- [Strength 2]\n- [Strength 3]\n\n## Suggestions for Improvement\n\n### Clarity\n- [Specific issue] → [Suggested fix]\n- [Complex sentence] → [Simpler alternative]\n\n### Flow\n- [Transition issue] → [Better connection]\n- [Paragraph order] → [Suggested reordering]\n\n### Evidence\n- [Claim needing support] → [Add citation or example]\n- [Generic statement] → [Make more specific]\n\n### Style\n- [Tone inconsistency] → [Match your voice better]\n- [Word choice] → [Stronger alternative]\n\n## Specific Line Edits\n\nOriginal:\n> [Exact quote from draft]\n\nSuggested:\n> [Improved version]\n\nWhy: [Explanation]\n\n## Questions to Consider\n- [Thought-provoking question 1]\n- [Thought-provoking question 2]\n\nReady to move to next section!\n\n\nPreserve Writer's Voice\n\nImportant principles:\n\nLearn their style: Read existing writing samples\nSuggest, don't replace: Offer options, not directives\nMatch tone: Formal, casual, technical, friendly\nRespect choices: If they prefer their version, support it\nEnhance, don't override: Make their writing better, not different\n\nAsk periodically:\n\n\"Does this sound like you?\"\n\"Is this the right tone?\"\n\"Should I be more/less [formal/casual/technical]?\"\n\nCitation Management\n\nHandle references based on user preference:\n\nInline Citations:\n\nStudies show 40% productivity improvement (McKinsey, 2024).\n\n\nNumbered References:\n\nStudies show 40% productivity improvement [1].\n\n[1] McKinsey Global Institute. (2024)...\n\n\nFootnote Style:\n\nStudies show 40% productivity improvement^1\n\n^1: McKinsey Global Institute. (2024)...\n\n\nMaintain a running citations list:\n\n## References\n\n1. Author. (Year). \"Title\". Publication.\n2. Author. (Year). \"Title\". Publication.\n...\n\n\nFinal Review and Polish\n\nWhen draft is complete, provide comprehensive feedback:\n\n# Full Draft Review\n\n## Overall Assessment\n\n**Strengths**:\n- [Major strength 1]\n- [Major strength 2]\n- [Major strength 3]\n\n**Impact**: [Overall effectiveness assessment]\n\n## Structure & Flow\n- [Comments on organization]\n- [Transition quality]\n- [Pacing assessment]\n\n## Content Quality\n- [Argument strength]\n- [Evidence sufficiency]\n- [Example effectiveness]\n\n## Technical Quality\n- Grammar and mechanics: [assessment]\n- Consistency: [assessment]\n- Citations: [completeness check]\n\n## Readability\n- Clarity score: [evaluation]\n- Sentence variety: [evaluation]\n- Paragraph length: [evaluation]\n\n## Final Polish Suggestions\n\n1. **Introduction**: [Specific improvements]\n2. **Body**: [Specific improvements]\n3. **Conclusion**: [Specific improvements]\n4. **Title**: [Options if needed]\n\n## Pre-Publish Checklist\n- [ ] All claims sourced\n- [ ] Citations formatted\n- [ ] Examples clear\n- [ ] Transitions smooth\n- [ ] Call to action present\n- [ ] Proofread for typos\n\nReady to publish! 🚀\n\nExamples\nExample 1: Teresa Torres's Workflow\n\nUser: \"I'm writing an article about continuous discovery. Help me create an outline.\"\n\nProcess:\n\nCollaborates on outline structure\nIdentifies research needs\nUser starts writing introduction\nReviews and improves the hook\nUser writes each section\nProvides feedback after each section\nConducts research and adds citations\nFinal review of complete draft\nPolish and prep for publishing\n\nResult: Well-researched, properly cited article written in Teresa's voice with strong structure and flow.\n\nExample 2: Research-Heavy Article\n\nUser: \"I'm writing about AI's impact on product management. Help me find current data and examples.\"\n\nOutput:\n\n## Research Compiled\n\n### Recent Data\n- Gartner: 80% of PMs will use AI tools by 2025 [1]\n- Survey: 45% report faster feature shipping [2]\n- Case study: Airbnb's AI-assisted prioritization [3]\n\n### Expert Quotes\n- \"AI amplifies PM judgment, not replaces it\" - Marty Cagan\n- [Additional quotes with citations]\n\n### Real Examples\n1. **Company A**: Used AI for user research synthesis\n   - Result: 60% time savings\n   - Source: [citation]\n\n2. **Company B**: AI-powered roadmap analysis\n   - Result: Better stakeholder alignment\n   - Source: [citation]\n\nAll added to your outline with proper citations.\n\nExample 3: Hook Improvement\n\nUser's Original Hook:\n\n\"Product management is changing because of AI. In this article, I'll discuss some ways AI affects product managers.\"\n\nImproved Options:\n\nOption 1 (Data-driven):\n\n\"Last month, I asked AI to analyze 500 customer interviews. It took 30 minutes instead of 3 weeks. Product management will never be the same.\"\n\nOption 2 (Question):\n\n\"What if you could talk to every customer, read every review, and analyze every support ticket—all before your morning coffee?\"\n\nOption 3 (Story):\n\n\"Sarah spent two weeks building the wrong feature. Not because she didn't understand her users, but because she couldn't process the hundreds of interviews fast enough to spot the pattern.\"\n\nExample 4: Section Feedback\n\nUser: \"Just finished my 'Common Mistakes' section. Thoughts?\"\n\nResponse:\n\n# Feedback: Common Mistakes Section\n\n## What Works Well ✓\n- Strong examples (the Slack notification story)\n- Clear structure (3 mistakes, clean layout)\n- Practical advice for each mistake\n\n## Suggestions\n\n### Make It More Specific\nYour second point says \"Bad prioritization\" but could be stronger:\n\nCurrent:\n> \"Many teams prioritize badly by focusing on features instead of outcomes.\"\n\nSuggested:\n> \"I've watched teams ship 14 features in a quarter yet move none of their key metrics. They prioritized activity over progress.\"\n\n### Add Data\nThe third mistake would benefit from evidence:\n> \"[Add citation]: Studies show teams without regular user contact are 3x more likely to build unused features [needs source]\"\n\n### Flow Improvement\nConsider reordering: Mistake 3 → Mistake 2 → Mistake 1\nThis builds from small to big impact.\n\nReady for the next section!\n\nWriting Workflows\nBlog Post Workflow\nOutline together\nResearch key points\nWrite introduction → get feedback\nWrite body sections → feedback each\nWrite conclusion → final review\nPolish and edit\nNewsletter Workflow\nDiscuss hook ideas\nQuick outline (shorter format)\nDraft in one session\nReview for clarity and links\nQuick polish\nTechnical Tutorial Workflow\nOutline steps\nWrite code examples\nAdd explanations\nTest instructions\nAdd troubleshooting section\nFinal review for accuracy\nThought Leadership Workflow\nBrainstorm unique angle\nResearch existing perspectives\nDevelop your thesis\nWrite with strong POV\nAdd supporting evidence\nCraft compelling conclusion\nPro Tips\nWork in VS Code: Better than web Claude for long-form writing\nOne section at a time: Get feedback incrementally\nSave research separately: Keep a research.md file\nVersion your drafts: article-v1.md, article-v2.md, etc.\nRead aloud: Use feedback to identify clunky sentences\nSet deadlines: \"I want to finish the draft today\"\nTake breaks: Write, get feedback, pause, revise\nFile Organization\n\nRecommended structure for writing projects:\n\n~/writing/article-name/\n├── outline.md          # Your outline\n├── research.md         # All research and citations\n├── draft-v1.md         # First draft\n├── draft-v2.md         # Revised draft\n├── final.md            # Publication-ready\n├── feedback.md         # Collected feedback\n└── sources/            # Reference materials\n    ├── study1.pdf\n    └── article2.md\n\nBest Practices\nFor Research\nVerify sources before citing\nUse recent data when possible\nBalance different perspectives\nLink to original sources\nFor Feedback\nBe specific about what you want: \"Is this too technical?\"\nShare your concerns: \"I'm worried this section drags\"\nAsk questions: \"Does this flow logically?\"\nRequest alternatives: \"What's another way to explain this?\"\nFor Voice\nShare examples of your writing\nSpecify tone preferences\nPoint out good matches: \"That sounds like me!\"\nFlag mismatches: \"Too formal for my style\"\nRelated Use Cases\nCreating social media posts from articles\nAdapting content for different audiences\nWriting email newsletters\nDrafting technical documentation\nCreating presentation content\nWriting case studies\nDeveloping course outlines"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/guohongbin-git/content-research-writer-cn",
    "publisherUrl": "https://clawhub.ai/guohongbin-git/content-research-writer-cn",
    "owner": "guohongbin-git",
    "version": "1.0.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/content-research-writer-cn",
    "downloadUrl": "https://openagent3.xyz/downloads/content-research-writer-cn",
    "agentUrl": "https://openagent3.xyz/skills/content-research-writer-cn/agent",
    "manifestUrl": "https://openagent3.xyz/skills/content-research-writer-cn/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/content-research-writer-cn/agent.md"
  }
}