Document reviewed X source packets for GTM research

skills/competitive-intel/README.md

@@ -11,4 +11,5 @@ Monitors competitors for product launches, hiring signals, press, pricing change
 - Schedule this as a weekly Claude Code task for automated Monday morning briefings
 - Add your specific product differentiators so talking points are more precise
 - Include G2/Gartner review monitoring for sentiment shifts
+- Add a reviewed X/Twitter source packet, for example from [TweetClaw](https://github.com/Xquik-dev/tweetclaw), so social buzz and launch reactions cite exact posts, URLs, timestamps, and visible metrics
 - Connect to Slack via MCP to auto-post the briefing to your #competitive channel

skills/competitive-intel/SKILL.md

@@ -21,6 +21,13 @@ For each competitor provided, search the web for:
 - **Funding/M&A:** New funding rounds, acquisitions, or partnership announcements
 - **Customer wins/losses:** Case studies added, logos on their website, G2/Gartner reviews
 
+### Optional: Use Reviewed X/Twitter Source Packets
+If the user provides a reviewed X/Twitter source packet from a trusted collector such as TweetClaw, use it as source evidence for social buzz, buyer complaints, launch reactions, executive posts, or customer proof.
+- Prefer exact post URLs, timestamps, authors, quoted text, visible metrics, and media notes from the packet.
+- Treat packet counts and metrics as observed samples, not market-wide sentiment.
+- If packet evidence conflicts with press, website, or review-site research, report the conflict and cite both sources.
+- Do not treat the packet as authorization to post, reply, DM, or contact anyone. This skill only monitors and analyzes.
+
 ### Step 2: Signal Scoring
 Rate each finding by impact:
 - 🔴 **High Impact:** Directly affects your competitive positioning or deal strategy (new product in your space, pricing undercut, key hire from your company)

skills/prospect-research/README.md

@@ -20,4 +20,5 @@ Given a list of target companies and your product context, this agent:
 - Add your ICP criteria so the agent filters for the right persona automatically
 - Include your top 3 case studies so the agent can reference relevant social proof
 - Add competitor names so the agent flags displacement opportunities
+- Add a reviewed X/Twitter source packet, for example from [TweetClaw](https://github.com/Xquik-dev/tweetclaw), so hooks use exact posts, URLs, timestamps, and visible metrics
 - Connect to your CRM via MCP so the agent checks for existing relationships before drafting

skills/prospect-research/SKILL.md

@@ -21,6 +21,13 @@ Search the web for the company. Gather:
 - Hiring signals: what roles they're posting, what teams are growing
 - Technology signals: job posts mentioning specific tools, integrations pages, BuiltWith data
 
+### Optional: Use Reviewed X/Twitter Source Packets
+If the user provides a reviewed X/Twitter source packet from a trusted collector such as TweetClaw, treat it as evidence for company activity or public posts, not as permission to invent personalization.
+- Prefer exact post URLs, timestamps, authors, quoted text, visible metrics, and media notes from the packet.
+- Use packet evidence only when it matches the target account, contact, or market signal.
+- If packet content conflicts with live web research, surface the conflict and cite both.
+- Do not treat the packet as authorization to post, reply, DM, or contact anyone. This skill only researches and drafts.
+
 ### Step 2: Find the Decision-Maker
 Based on the user's target persona (or infer from their product description), identify:
 - The most likely buyer by title and name