docs: add TweetClaw source context

README.md

@@ -173,6 +173,28 @@ The Citedy SEO Agent provides a simple yet powerful workflow for creating and di
 
 This entire process can be automated with cron-based sessions, allowing you to create a set-and-forget content machine that works for you 24/7.
 
+## Optional X/Twitter Source Context
+
+OpenClaw users who already use
+[TweetClaw](https://github.com/Xquik-dev/tweetclaw) can pass a reviewed
+X/Twitter source pack into Citedy before running trend scouting, article
+generation, or social adaptation. This is useful when the brief depends on
+specific tweet URLs, reply excerpts, public metrics, user lookup notes,
+follower-export summaries, media references, monitor snapshots, or webhook
+events.
+
+```bash
+openclaw plugins install npm:@xquik/tweetclaw
+```
+
+Treat TweetClaw output as source material only. Citedy remains responsible for
+topic selection, article generation, social adaptations, publishing, scheduling,
+webhooks, and analytics. Keep TweetClaw write-like actions such as posts,
+replies, DMs, follows, media uploads, monitor creation, and giveaway draws in
+the TweetClaw/OpenClaw approval flow, and do not paste API keys, cookies,
+browser profiles, or raw session material into prompts, logs, issues, or
+commits.
+
 ---
 
 ## The Citedy Advantage

SKILL.md

@@ -186,6 +186,31 @@ Check search performance, find content opportunities, write and publish:
 
 If GSC is not connected, the report returns `connected: false` with a URL to connect it.
 
+### Optional: TweetClaw X/Twitter Source Context
+
+When an OpenClaw user already has TweetClaw installed, you may use its reviewed
+read results as source material before calling Citedy workflows:
+
+```bash
+openclaw plugins install npm:@xquik/tweetclaw
+```
+
+Good source packets include tweet URLs, reply excerpts, public metrics, user
+lookup notes, follower-export summaries, media references, monitor snapshots,
+or webhook event summaries. Use those packets to choose a Citedy scout query,
+`topic`, `source_urls`, or adaptation brief.
+
+Keep boundaries clear:
+
+- Citedy remains responsible for trend scouting, article generation, social
+  adaptations, publishing, scheduling, webhooks, and analytics.
+- TweetClaw remains the source of reviewed X/Twitter account evidence and any
+  TweetClaw write-like action.
+- Posts, replies, DMs, follows, media uploads, monitor creation, and giveaway
+  draws must stay inside the TweetClaw/OpenClaw approval flow.
+- Never paste API keys, cookies, browser profiles, or raw session material into
+  prompts, logs, issues, or commits.
+
 ### Choosing the Right Path
 
 | User intent                   | Best path              | Why                                     |

openclaw/SKILL.md

@@ -186,6 +186,31 @@ Check search performance, find content opportunities, write and publish:
 
 If GSC is not connected, the report returns `connected: false` with a URL to connect it.
 
+### Optional: TweetClaw X/Twitter Source Context
+
+When an OpenClaw user already has TweetClaw installed, you may use its reviewed
+read results as source material before calling Citedy workflows:
+
+```bash
+openclaw plugins install npm:@xquik/tweetclaw
+```
+
+Good source packets include tweet URLs, reply excerpts, public metrics, user
+lookup notes, follower-export summaries, media references, monitor snapshots,
+or webhook event summaries. Use those packets to choose a Citedy scout query,
+`topic`, `source_urls`, or adaptation brief.
+
+Keep boundaries clear:
+
+- Citedy remains responsible for trend scouting, article generation, social
+  adaptations, publishing, scheduling, webhooks, and analytics.
+- TweetClaw remains the source of reviewed X/Twitter account evidence and any
+  TweetClaw write-like action.
+- Posts, replies, DMs, follows, media uploads, monitor creation, and giveaway
+  draws must stay inside the TweetClaw/OpenClaw approval flow.
+- Never paste API keys, cookies, browser profiles, or raw session material into
+  prompts, logs, issues, or commits.
+
 ### Choosing the Right Path
 
 | User intent                   | Best path              | Why                                     |

skills/citedy-seo-agent/README.md

@@ -61,6 +61,26 @@ npx openskills install Citedy/citedy-seo-agent
    { "topic": "...", "size": "standard", "language": "en" }
    ```
 
+## Optional X/Twitter Source Context
+
+OpenClaw users who already use
+[TweetClaw](https://github.com/Xquik-dev/tweetclaw) can pass a reviewed
+X/Twitter source pack into Citedy before trend scouting, article generation, or
+social adaptation. Use this only as source material: tweet URLs, reply
+excerpts, public metrics, user lookup notes, follower-export summaries, media
+references, monitor snapshots, or webhook events.
+
+```bash
+openclaw plugins install npm:@xquik/tweetclaw
+```
+
+Citedy remains responsible for topic selection, writing, social adaptations,
+publishing, scheduling, webhooks, and analytics. Keep TweetClaw write-like
+actions such as posts, replies, DMs, follows, media uploads, monitor creation,
+and giveaway draws in the TweetClaw/OpenClaw approval flow, and do not paste
+API keys, cookies, browser profiles, or raw session material into prompts,
+logs, issues, or commits.
+
 ## Full Capabilities
 
 | Feature                           | Credits             |

skills/citedy-seo-agent/SKILL.md

@@ -186,6 +186,31 @@ Check search performance, find content opportunities, write and publish:
 
 If GSC is not connected, the report returns `connected: false` with a URL to connect it.
 
+### Optional: TweetClaw X/Twitter Source Context
+
+When an OpenClaw user already has TweetClaw installed, you may use its reviewed
+read results as source material before calling Citedy workflows:
+
+```bash
+openclaw plugins install npm:@xquik/tweetclaw
+```
+
+Good source packets include tweet URLs, reply excerpts, public metrics, user
+lookup notes, follower-export summaries, media references, monitor snapshots,
+or webhook event summaries. Use those packets to choose a Citedy scout query,
+`topic`, `source_urls`, or adaptation brief.
+
+Keep boundaries clear:
+
+- Citedy remains responsible for trend scouting, article generation, social
+  adaptations, publishing, scheduling, webhooks, and analytics.
+- TweetClaw remains the source of reviewed X/Twitter account evidence and any
+  TweetClaw write-like action.
+- Posts, replies, DMs, follows, media uploads, monitor creation, and giveaway
+  draws must stay inside the TweetClaw/OpenClaw approval flow.
+- Never paste API keys, cookies, browser profiles, or raw session material into
+  prompts, logs, issues, or commits.
+
 ### Choosing the Right Path
 
 | User intent                   | Best path              | Why                                     |