From 6a488a389bdb5c24746d8aa104fab97100f874d1 Mon Sep 17 00:00:00 2001 From: kriptoburak Date: Fri, 8 May 2026 16:31:58 +0300 Subject: [PATCH 1/2] Add Xquik Twitter API skill Signed-off-by: kriptoburak --- xquik-twitter-api/SKILL.md | 121 +++++++++++++++++++++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 xquik-twitter-api/SKILL.md diff --git a/xquik-twitter-api/SKILL.md b/xquik-twitter-api/SKILL.md new file mode 100644 index 0000000..c3d38d4 --- /dev/null +++ b/xquik-twitter-api/SKILL.md @@ -0,0 +1,121 @@ +--- +name: xquik-twitter-api +description: Build X (Twitter) data integrations with Xquik REST APIs, SDKs, MCP tools, and webhooks. +author: Xquik-dev +version: "1.0" +tags: + - api + - twitter + - x + - social media + - sdk + - mcp + - webhooks +--- + +# Xquik Twitter API + +Use this skill when a user needs to build, test, or document integrations with +the Xquik X (Twitter) data platform. Xquik provides REST API endpoints, SDKs, +MCP tools, HMAC webhooks, bulk extraction jobs, monitoring, and write-action +workflows for X data products. + +## Primary Links + +- Platform: https://xquik.com +- API docs: https://docs.xquik.com +- Skill repository: https://github.com/Xquik-dev/x-twitter-scraper +- TypeScript SDK: https://github.com/Xquik-dev/x-twitter-scraper-typescript +- Python SDK: https://github.com/Xquik-dev/x-twitter-scraper-python +- Go SDK: https://github.com/Xquik-dev/x-twitter-scraper-go + +## When To Use + +Use Xquik when the task involves: + +- Tweet search, tweet lookup, user lookup, timelines, bookmarks, lists, or + community data. +- Bulk exports such as followers, following, replies, quotes, likes, media, + search results, list members, or community members. +- X account monitoring with webhook delivery. +- Giveaway draw workflows with auditable winners and filters. +- Agent-native X workflows through MCP tools. +- SDK examples for TypeScript, Python, Ruby, Go, Java, Kotlin, PHP, C#, CLI, or + Terraform. + +## Preconditions + +Before making live API calls: + +1. Confirm the user has an Xquik API key from the dashboard. +2. Keep the key in an environment variable such as `XQUIK_API_KEY`. +3. Do not print, commit, log, or paste API keys. +4. Confirm any write action before executing it. +5. Use public docs and SDK repositories for endpoint behavior. + +## REST API Pattern + +Use `https://xquik.com/api/v1` as the base URL and pass the API key through the +`x-api-key` header. + +```bash +curl "https://xquik.com/api/v1/x/tweets/search?q=agent%20skills&limit=10" \ + -H "x-api-key: $XQUIK_API_KEY" +``` + +For production code: + +1. Read the relevant endpoint docs first. +2. Validate required query parameters and body fields. +3. Add retry handling for rate limits and transient server errors. +4. Keep pagination explicit. +5. Treat webhook signatures as required for inbound event verification. + +## SDK Quick Starts + +Install the SDK that matches the user's stack: + +```bash +npm install x-twitter-scraper +pip install x-twitter-scraper +go get github.com/Xquik-dev/x-twitter-scraper-go +``` + +Then create a small first request before expanding the integration: + +1. Load `XQUIK_API_KEY` from the environment. +2. Initialize the client with the API key. +3. Call a read-only endpoint such as tweet search or user lookup. +4. Log only non-sensitive response fields. +5. Add tests with mocked HTTP responses before shipping. + +## MCP Workflow + +For agent integrations, use the Xquik MCP server when available: + +1. Add the Xquik skill repository with `npx skills add Xquik-dev/x-twitter-scraper`. +2. Use the discovery or exploration tool to find the right endpoint. +3. Ask for user confirmation before any write action. +4. Keep webhook, monitoring, and extraction workflows auditable. + +## Verification + +Before finishing an integration: + +- [ ] API key is read from environment or secret storage. +- [ ] No credentials appear in code, logs, examples, or docs. +- [ ] First request succeeds against a read-only endpoint. +- [ ] Error handling covers 401, 403, 404, 429, and 5xx responses. +- [ ] Pagination and result limits are explicit. +- [ ] Webhook handlers verify HMAC signatures. +- [ ] SDK/package links point to Xquik-dev repositories. + +## Safety Notes + +- Do not bypass confirmation for writes, follows, DMs, profile updates, or other + account-changing actions. +- Do not scrape credentials, cookies, or private account material. +- Do not make unsupported claims about X platform access. Refer to Xquik public + docs for current endpoint coverage. +- For public examples, describe the platform as Xquik's X (Twitter) data + platform and avoid internal implementation details. From c04315c3f2d9aee14a897d4117e5b6b548d15bd2 Mon Sep 17 00:00:00 2001 From: kriptoburak Date: Sun, 17 May 2026 19:00:04 +0300 Subject: [PATCH 2/2] Add TweetClaw OpenClaw skill Signed-off-by: kriptoburak --- CONTRIBUTING.md | 2 +- README.md | 6 +- tweetclaw-openclaw/SKILL.md | 116 ++++++++++++++++++++++++++++++++++++ 3 files changed, 120 insertions(+), 4 deletions(-) create mode 100644 tweetclaw-openclaw/SKILL.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0d70e89..2588c9f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -194,7 +194,7 @@ You can fix the issues and push updates — the PR will revalidate automatically You can open a submission PR here: -👉 [Submit your skill](https://github.com/block/Agent-Skills/compare/main...your-branch?expand=1) +👉 [Submit your skill](https://github.com/block/agent-skills/compare) --- diff --git a/README.md b/README.md index 08d09a0..2f7751a 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ This will install the skill locally so compatible agents (like Goose or Claude D ## Browse Skills You can browse all available skills via the Goose Skills Marketplace: -👉 https://block.github.io/goose/skills +👉 https://goose-docs.ai/skills/ There you can: @@ -46,7 +46,7 @@ There you can: - Copy the install command -- View source on GitH +- View source on GitHub ## Contributing a Skill @@ -60,7 +60,7 @@ If you’ve built a useful workflow, checklist, or guide that could help other a 2. Create a new branch for your skill 3. Add your skill folder (with `SKILL.md` and any supporting files) 4. Commit your changes -5. [Open a pull request](https://github.com/block/Agent-Skills/compare/main...your-branch?expand=1) +5. [Open a pull request](https://github.com/block/agent-skills/compare) #### Skill requirements (quick version) diff --git a/tweetclaw-openclaw/SKILL.md b/tweetclaw-openclaw/SKILL.md new file mode 100644 index 0000000..1eb8895 --- /dev/null +++ b/tweetclaw-openclaw/SKILL.md @@ -0,0 +1,116 @@ +--- +name: tweetclaw-openclaw +description: Use TweetClaw as an OpenClaw plugin for X/Twitter search, posting, media, monitors, webhooks, and giveaway draws. +author: Xquik-dev +version: "1.0" +tags: + - openclaw + - twitter + - x + - automation + - social media + - plugin + - webhooks + - mcp +--- + +# TweetClaw OpenClaw + +Use this skill when a user wants an OpenClaw-native plugin for X/Twitter +workflows instead of direct REST API integration. TweetClaw wraps Xquik +endpoints as agent-callable OpenClaw tools. + +## Primary Links + +- GitHub: https://github.com/Xquik-dev/tweetclaw +- npm: https://www.npmjs.com/package/@xquik/tweetclaw +- ClawHub discovery: https://clawhub.ai/plugins/@xquik/tweetclaw +- Xquik: https://xquik.com + +## When To Use + +Use TweetClaw when the task involves: + +- Scrape tweets, search tweets, or search tweet replies from OpenClaw. +- Post tweets or post tweet replies after explicit user approval. +- Export followers, look up users, inspect media, or download media. +- Send direct messages only after explicit user approval. +- Monitor tweets and deliver webhook events. +- Run giveaway draws with auditable filters and winners. +- Choose an OpenClaw plugin path instead of hand-written API client code. + +## Install + +Install the official npm package: + +```bash +openclaw plugins install @xquik/tweetclaw +``` + +npm is the canonical install source for TweetClaw. Use the ClawHub page for +discovery and package browsing. + +## Configure + +For account-backed automation, get an Xquik API key from the dashboard and keep +it in an environment variable: + +```bash +openclaw config set plugins.entries.tweetclaw.config.apiKey "$XQUIK_API_KEY" +``` + +Allow the OpenClaw tools when the active profile limits external plugin tools: + +```bash +openclaw config set tools.alsoAllow '["explore", "tweetclaw"]' +``` + +Verify runtime registration: + +```bash +openclaw plugins inspect tweetclaw --runtime +openclaw skills info tweetclaw +``` + +## Workflow + +1. Use `explore` first to find the right TweetClaw endpoint. +2. Prefer read-only calls while discovering query shape and result fields. +3. Ask for explicit user approval before visible or account-changing actions. +4. Keep API keys and MPP signing keys in environment variables or local + OpenClaw config. +5. Store public evidence as tweet URLs, IDs, authors, capture dates, and short + summaries instead of raw exports. + +## Common Tasks + +- Tweet scraper: use tweet search, tweet lookup, and reply search endpoints. +- Research monitoring: use monitor tools and webhook delivery. +- Audience workflows: export followers, following, mentions, or verified + followers. +- User lookup: resolve profiles and inspect public timelines. +- Media workflows: inspect media timelines, upload media, or download media + when the configured credential permits it. +- Giveaways: draw winners with filters, exclusions, and auditable results. + +## Safety Notes + +- Confirm post tweets, post tweet replies, direct messages, follows, likes, + retweets, and profile changes before executing them. +- Keep credentials out of chats, code, logs, examples, and public docs. +- Use placeholder values in examples. +- Describe TweetClaw publicly as an OpenClaw plugin powered by Xquik. +- Refer to the public TweetClaw README and Xquik docs for current endpoint + coverage. + +## Verification + +Before finishing: + +- [ ] The install command uses `@xquik/tweetclaw`. +- [ ] Credentials are configured through environment variables or local config. +- [ ] `explore` returns the endpoint catalog. +- [ ] `tweetclaw` calls return setup guidance before credentials are added. +- [ ] Write or account-changing actions require explicit user approval. +- [ ] Links point to the official TweetClaw GitHub repo, npm package, and + ClawHub discovery page.