From c8cba69d85c370048c298e1226664b893f0b8882 Mon Sep 17 00:00:00 2001 From: kriptoburak Date: Mon, 8 Jun 2026 20:05:37 +0200 Subject: [PATCH] docs: add TweetClaw source context --- README.md | 22 ++++++++++++++++++++++ SKILL.md | 25 +++++++++++++++++++++++++ openclaw/SKILL.md | 25 +++++++++++++++++++++++++ skills/citedy-seo-agent/README.md | 20 ++++++++++++++++++++ skills/citedy-seo-agent/SKILL.md | 25 +++++++++++++++++++++++++ 5 files changed, 117 insertions(+) diff --git a/README.md b/README.md index b166ff5..826cf4e 100644 --- a/README.md +++ b/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 diff --git a/SKILL.md b/SKILL.md index 0bcb02b..79a9477 100644 --- a/SKILL.md +++ b/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 | diff --git a/openclaw/SKILL.md b/openclaw/SKILL.md index 0bcb02b..79a9477 100644 --- a/openclaw/SKILL.md +++ b/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 | diff --git a/skills/citedy-seo-agent/README.md b/skills/citedy-seo-agent/README.md index 91fca41..4f012cc 100644 --- a/skills/citedy-seo-agent/README.md +++ b/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 | diff --git a/skills/citedy-seo-agent/SKILL.md b/skills/citedy-seo-agent/SKILL.md index 0bcb02b..79a9477 100644 --- a/skills/citedy-seo-agent/SKILL.md +++ b/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 |