{
  "schemaVersion": "1.0",
  "item": {
    "slug": "community-intel",
    "name": "Community Intel",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/npfaerber/community-intel",
    "canonicalUrl": "https://clawhub.ai/npfaerber/community-intel",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/community-intel",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=community-intel",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.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. 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/community-intel"
    },
    "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/community-intel",
    "agentPageUrl": "https://openagent3.xyz/skills/community-intel/agent",
    "manifestUrl": "https://openagent3.xyz/skills/community-intel/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/community-intel/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": "Community Intel",
        "body": "Automated community intelligence gathering and trend monitoring for open-source projects and products."
      },
      {
        "title": "Requirements",
        "body": "Web search and fetch capabilities (web_search, web_fetch tools)\nOptional: Discord channel for posting reports (message tool)\nOptional: Email integration for delivering reports (AgentMail, Resend, or any email skill)"
      },
      {
        "title": "How It Works",
        "body": "Run as a nightly or weekly cron job. The agent searches multiple platforms for mentions of a target project/product, reads full threads, and compiles a structured intelligence report. Over time, it learns which sources are productive and adjusts accordingly."
      },
      {
        "title": "Configuration",
        "body": "Set these in your cron message or workspace config:\n\nPROJECT_NAME: \"YourProject\"\nSEARCH_TERMS: [\"yourproject\", \"your-project\", \"YourProject\"]\nSUBREDDITS: [\"r/yourproject\", \"r/selfhosted\", \"r/programming\"]\nINTEL_FILE: \"memory/project-intel.md\"       # cumulative findings log\nDISCORD_CHANNEL: \"\"                          # optional: channel ID for posting\nEMAIL_TO: \"\"                                 # optional: email for delivery"
      },
      {
        "title": "Primary (search every run)",
        "body": "SourceWhat to searchBest forRedditProject subreddit + related subsUse cases, complaints, tipsHacker Newssite:news.ycombinator.com + project nameTechnical discussion, launchesGitHubIssues, discussions, new reposBug reports, feature requests, forksTwitter/XProject name + hashtagsViral moments, announcements"
      },
      {
        "title": "Secondary (rotate or check weekly)",
        "body": "SourceWhat to searchBest forYouTubeProject name + \"tutorial\" / \"review\"Adoption trends, developer contentBlog postsMedium, Substack, dev.toDeep dives, experience reportsProduct HuntLaunches building on the projectEcosystem growthAcademic papersArXiv, Google ScholarResearch using/studying the project"
      },
      {
        "title": "OpenClaw Cron Setup",
        "body": "Add via CLI:\n\nopenclaw cron add \\\n  --name \"Community Intel\" \\\n  --schedule \"45 22 * * *\" \\\n  --tz \"America/Chicago\" \\\n  --session-target isolated \\\n  --timeout 600 \\\n  --message \"$(cat <<'EOF'\nYou are doing community research for [PROJECT_NAME].\n\nSearch for mentions across Reddit, Twitter/X, Hacker News, GitHub, and YouTube.\nLook for: interesting use cases, creative integrations, tips and tricks,\nnew tools, complaints, security issues, and feature requests.\n\nSteps:\n1. Read [INTEL_FILE] for context on past findings and best sources\n2. Search each platform for [SEARCH_TERMS]\n3. Go deep -- read full threads, follow links, check comments\n4. Compile findings into a structured summary\n5. Append findings to [INTEL_FILE] with today's date and run number\n6. Post summary to Discord channel [DISCORD_CHANNEL] (if configured)\n7. Rate each source 1-3 stars based on today's yield\n\nBe thorough. Quality over speed. If a source has nothing new, note that\nso we can deprioritize it over time.\nEOF\n)\"\n\nOr add via config.patch:\n\n{\n  \"cron\": [{\n    \"name\": \"Community Intel\",\n    \"schedule\": \"45 22 * * *\",\n    \"tz\": \"America/Chicago\",\n    \"sessionTarget\": \"isolated\",\n    \"timeout\": 600,\n    \"message\": \"You are doing community research for [PROJECT_NAME]...\"\n  }]\n}"
      },
      {
        "title": "Report Format",
        "body": "Each run produces a report in this structure:\n\n### YYYY-MM-DD (run N) -- Research Run\n\n**Headline:** [one-line summary of biggest findings]\n\n**🔥 Cool Use Cases**\n- [Description with source link]\n\n**💡 Tips & Tricks**\n- [Practical discovery with details]\n\n**🛠️ New Tools / Integrations**\n- [New project, tool, or integration discovered]\n\n**📢 Community Buzz**\n- [Sentiment, complaints, praise, trends]\n\n**🔒 Security / Risks**\n- [Any security findings, vulnerabilities, concerns]\n\n**📊 Source Quality**\n- Reddit: ⭐⭐⭐ (active discussions)\n- HN: ⭐⭐ (one thread)\n- Twitter: ⭐ (quiet day)\n- YouTube: ⭐⭐⭐ (new tutorials)"
      },
      {
        "title": "Intel File Structure",
        "body": "Maintain a cumulative intel file (INTEL_FILE) with three sections:\n\n# [PROJECT_NAME] Intel\n\n## Best Sources (updated YYYY-MM-DD, run N)\n- **Reddit** ⭐⭐⭐ -- Active community, good use cases\n- **Hacker News** ⭐⭐ -- Occasional deep technical threads\n- **GitHub** ⭐⭐ -- Steady issue flow\n- **Twitter/X** ⭐ -- Mostly retweets, low signal\n- **YouTube** ⭐⭐⭐ -- Tutorial explosion lately\n\n## Community Resources Discovered\n- [tool-name](url) -- Description\n- [directory-site](url) -- Curated list of projects\n\n## Findings Log\n### YYYY-MM-DD (run N)\n... (newest first, oldest at bottom)\n\nThe agent reads this file at the start of each run to:\n\nKnow which sources to prioritize\nAvoid reporting duplicate findings\nTrack trends over time (\"X was a complaint in run 5, fixed by run 12\")"
      },
      {
        "title": "Research Techniques",
        "body": "Search query patterns that work well:\n\n\"project-name\" site:reddit.com -- Reddit mentions\n\"project-name\" site:news.ycombinator.com -- HN threads\n\"project-name\" tutorial OR guide OR setup -- How-to content\n\"project-name\" vs OR alternative OR competitor -- Competitive landscape\n\"project-name\" security OR vulnerability OR CVE -- Security issues\n\"project-name\" after:YYYY-MM-DD -- Only recent results\n\nReading threads effectively:\n\nDon't stop at the title. The real insights are in comment replies.\nLook for upvote counts -- high-upvote comments often contain the most useful info.\nCheck who's commenting. Maintainers, power users, and industry people carry more signal.\nNote when the same complaint appears across multiple platforms -- that's a real issue."
      },
      {
        "title": "Tips",
        "body": "Quality over speed. Read full threads, don't just skim titles.\nTrack source quality. Rate each source 1-3 stars per run. Deprioritize sources that consistently yield nothing.\nNote sentiment shifts. \"People used to complain about X, now they praise it\" is valuable signal.\nFlag security issues immediately. Don't wait for the next scheduled run.\nKeep the findings log trimmed. Archive entries older than 30 days to a separate file to keep the intel file under 100KB.\nSearch variations. Try the project name with and without hyphens, abbreviations, and common misspellings.\nTrack run numbers. Increment each run so you can reference \"this was first spotted in run 14\" for trend tracking."
      }
    ],
    "body": "Community Intel\n\nAutomated community intelligence gathering and trend monitoring for open-source projects and products.\n\nRequirements\nWeb search and fetch capabilities (web_search, web_fetch tools)\nOptional: Discord channel for posting reports (message tool)\nOptional: Email integration for delivering reports (AgentMail, Resend, or any email skill)\nHow It Works\n\nRun as a nightly or weekly cron job. The agent searches multiple platforms for mentions of a target project/product, reads full threads, and compiles a structured intelligence report. Over time, it learns which sources are productive and adjusts accordingly.\n\nConfiguration\n\nSet these in your cron message or workspace config:\n\nPROJECT_NAME: \"YourProject\"\nSEARCH_TERMS: [\"yourproject\", \"your-project\", \"YourProject\"]\nSUBREDDITS: [\"r/yourproject\", \"r/selfhosted\", \"r/programming\"]\nINTEL_FILE: \"memory/project-intel.md\"       # cumulative findings log\nDISCORD_CHANNEL: \"\"                          # optional: channel ID for posting\nEMAIL_TO: \"\"                                 # optional: email for delivery\n\nResearch Sources\nPrimary (search every run)\nSource\tWhat to search\tBest for\nReddit\tProject subreddit + related subs\tUse cases, complaints, tips\nHacker News\tsite:news.ycombinator.com + project name\tTechnical discussion, launches\nGitHub\tIssues, discussions, new repos\tBug reports, feature requests, forks\nTwitter/X\tProject name + hashtags\tViral moments, announcements\nSecondary (rotate or check weekly)\nSource\tWhat to search\tBest for\nYouTube\tProject name + \"tutorial\" / \"review\"\tAdoption trends, developer content\nBlog posts\tMedium, Substack, dev.to\tDeep dives, experience reports\nProduct Hunt\tLaunches building on the project\tEcosystem growth\nAcademic papers\tArXiv, Google Scholar\tResearch using/studying the project\nOpenClaw Cron Setup\n\nAdd via CLI:\n\nopenclaw cron add \\\n  --name \"Community Intel\" \\\n  --schedule \"45 22 * * *\" \\\n  --tz \"America/Chicago\" \\\n  --session-target isolated \\\n  --timeout 600 \\\n  --message \"$(cat <<'EOF'\nYou are doing community research for [PROJECT_NAME].\n\nSearch for mentions across Reddit, Twitter/X, Hacker News, GitHub, and YouTube.\nLook for: interesting use cases, creative integrations, tips and tricks,\nnew tools, complaints, security issues, and feature requests.\n\nSteps:\n1. Read [INTEL_FILE] for context on past findings and best sources\n2. Search each platform for [SEARCH_TERMS]\n3. Go deep -- read full threads, follow links, check comments\n4. Compile findings into a structured summary\n5. Append findings to [INTEL_FILE] with today's date and run number\n6. Post summary to Discord channel [DISCORD_CHANNEL] (if configured)\n7. Rate each source 1-3 stars based on today's yield\n\nBe thorough. Quality over speed. If a source has nothing new, note that\nso we can deprioritize it over time.\nEOF\n)\"\n\n\nOr add via config.patch:\n\n{\n  \"cron\": [{\n    \"name\": \"Community Intel\",\n    \"schedule\": \"45 22 * * *\",\n    \"tz\": \"America/Chicago\",\n    \"sessionTarget\": \"isolated\",\n    \"timeout\": 600,\n    \"message\": \"You are doing community research for [PROJECT_NAME]...\"\n  }]\n}\n\nReport Format\n\nEach run produces a report in this structure:\n\n### YYYY-MM-DD (run N) -- Research Run\n\n**Headline:** [one-line summary of biggest findings]\n\n**🔥 Cool Use Cases**\n- [Description with source link]\n\n**💡 Tips & Tricks**\n- [Practical discovery with details]\n\n**🛠️ New Tools / Integrations**\n- [New project, tool, or integration discovered]\n\n**📢 Community Buzz**\n- [Sentiment, complaints, praise, trends]\n\n**🔒 Security / Risks**\n- [Any security findings, vulnerabilities, concerns]\n\n**📊 Source Quality**\n- Reddit: ⭐⭐⭐ (active discussions)\n- HN: ⭐⭐ (one thread)\n- Twitter: ⭐ (quiet day)\n- YouTube: ⭐⭐⭐ (new tutorials)\n\nIntel File Structure\n\nMaintain a cumulative intel file (INTEL_FILE) with three sections:\n\n# [PROJECT_NAME] Intel\n\n## Best Sources (updated YYYY-MM-DD, run N)\n- **Reddit** ⭐⭐⭐ -- Active community, good use cases\n- **Hacker News** ⭐⭐ -- Occasional deep technical threads\n- **GitHub** ⭐⭐ -- Steady issue flow\n- **Twitter/X** ⭐ -- Mostly retweets, low signal\n- **YouTube** ⭐⭐⭐ -- Tutorial explosion lately\n\n## Community Resources Discovered\n- [tool-name](url) -- Description\n- [directory-site](url) -- Curated list of projects\n\n## Findings Log\n### YYYY-MM-DD (run N)\n... (newest first, oldest at bottom)\n\n\nThe agent reads this file at the start of each run to:\n\nKnow which sources to prioritize\nAvoid reporting duplicate findings\nTrack trends over time (\"X was a complaint in run 5, fixed by run 12\")\nResearch Techniques\n\nSearch query patterns that work well:\n\n\"project-name\" site:reddit.com -- Reddit mentions\n\"project-name\" site:news.ycombinator.com -- HN threads\n\"project-name\" tutorial OR guide OR setup -- How-to content\n\"project-name\" vs OR alternative OR competitor -- Competitive landscape\n\"project-name\" security OR vulnerability OR CVE -- Security issues\n\"project-name\" after:YYYY-MM-DD -- Only recent results\n\nReading threads effectively:\n\nDon't stop at the title. The real insights are in comment replies.\nLook for upvote counts -- high-upvote comments often contain the most useful info.\nCheck who's commenting. Maintainers, power users, and industry people carry more signal.\nNote when the same complaint appears across multiple platforms -- that's a real issue.\nTips\nQuality over speed. Read full threads, don't just skim titles.\nTrack source quality. Rate each source 1-3 stars per run. Deprioritize sources that consistently yield nothing.\nNote sentiment shifts. \"People used to complain about X, now they praise it\" is valuable signal.\nFlag security issues immediately. Don't wait for the next scheduled run.\nKeep the findings log trimmed. Archive entries older than 30 days to a separate file to keep the intel file under 100KB.\nSearch variations. Try the project name with and without hyphens, abbreviations, and common misspellings.\nTrack run numbers. Increment each run so you can reference \"this was first spotted in run 14\" for trend tracking."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/npfaerber/community-intel",
    "publisherUrl": "https://clawhub.ai/npfaerber/community-intel",
    "owner": "npfaerber",
    "version": "1.1.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/community-intel",
    "downloadUrl": "https://openagent3.xyz/downloads/community-intel",
    "agentUrl": "https://openagent3.xyz/skills/community-intel/agent",
    "manifestUrl": "https://openagent3.xyz/skills/community-intel/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/community-intel/agent.md"
  }
}