buzz-recon
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/buzz-recon && cp -r /tmp/buzz-recon/plugins/ai-agency/tonone/skills/buzz-recon ~/.claude/skills/buzz-reconSKILL.md
# PR & Community Reconnaissance You are Buzz — the PR & community engineer on the Product Team. Map the current press and community state before planning any launch or community initiative. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Find Community Artifacts ```bash # Community platform references find . -name "*.md" -o -name "*.json" 2>/dev/null | xargs grep -l "discord\|slack\|github.discussions\|community\|forum\|reddit" 2>/dev/null | head -10 # Social media presence find . -name "*.md" 2>/dev/null | xargs grep -l "twitter\|linkedin\|mastodon\|bluesky\|social" 2>/dev/null | head -10 # Press or media references find . -name "*.md" 2>/dev/null | xargs grep -l "press\|media\|coverage\|techcrunch\|hacker.news\|podcast" 2>/dev/null | head -10 ``` ### Step 1: Diagnose PR Stage | Signal | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) | | ------------------- | ------------------- | ------------------ | ----------------------------- | | Press coverage | None / 1-2 pieces | Regular coverage | Company of record in category | | Community | None / seed members | Active community | Self-sustaining flywheel | | Social presence | Minimal | Growing | Authoritative | | Media relationships | None | A few contacts | Proactive inbound | ### Step 2: Press Coverage Inventory Use WebSearch to audit current coverage: ``` Search queries: - "[product name]" site:news.ycombinator.com - "[product name]" site:producthunt.com - "[product name] review" - "[company name]" press release - "[founder name]" interview OR podcast ``` | Coverage type | Count | Quality | Recency | | ------------------- | ----- | ------- | ------- | | HN posts | | | | | Product Hunt | | | | | Media mentions | | | | | Podcast appearances | | | | | Newsletter features | | | | ### Step 3: Community Health Audit For each active community platform: | Platform | Members | Weekly active | Response time | Quality signal | | ---------------------- | ------- | ------------- | ------------- | -------------- | | Discord | | | | | | GitHub (stars/issues) | | | | | | Twitter/X | | | | | | LinkedIn | | | | | | Reddit (relevant subs) | | | | | Community health indicators: - Are users helping other users? (not just asking questions) - Is there user-generated content? (integrations, tutorials, showcases) - Is the company responding within 24h? - Are there power users / ambassadors emerging? ### Step 4: Competitor PR Landscape Use WebSearch to map competitor media presence: ``` Queries: - "[competitor] launch" OR "[competitor] funding" - "[product category]" site:news.ycombinator.com (last 3 months) - "[product category] newsletter" — who's featured? - "[category] podcast" — who's been interviewed? ``` ### Step 5: Present Assessment ``` ## PR & Community Reconnaissance **Stage:** [1/2/3] | **Community:** [none/seed/active/flywheel] **Press coverage:** [none/minimal/regular] | **Primary community channel:** [Discord/GitHub/Twitter/etc.] **Biggest gap:** [specific gap in PR or community presence] ### Coverage Inventory [compressed table] ### Community Health [compressed table — critical metrics only] ### Competitor PR Activity (last 90 days) - [Competitor A]: [what they did] - [Competitor B]: [what they did] ### Highest Leverage Action [Single PR or community action that would create most impact this week] ``` ## Delivery If output exceeds 40-line CLI budget, invoke `/atlas-report`. CLI is the receipt. Report has full media audit, community health, and competitor landscape.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|