القائمة
Use for generic X public-data research, trend discovery, recent-post checks, and social attention signals. Provides app-only bearer auth, endpoint patterns, field selection, error handling, and compact JSON evidence guidance.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for Drip Meta Ads CLI work: Meta account/Page preflight, env mapping, paused Facebook campaign creation, Graph fallback commands, redaction, safety rules, and Performance Marketer evidence.
Use for Drip Builder work. Builder turns the user's selected Fashion Designer product images into a reviewed, deployed, one-page limited-drop site and writes builder-output.json.
Use for generic Exa Search API research. Provides auth, request-shape, date-filter, batching, highlights, error-handling, and compact JSON evidence guidance for arbitrary caller-supplied queries. Query-agnostic; does not decide what to search for.
Use for Drip Fashion Designer work. Fashion Designer turns approved Scout ideas into polished product mockups through three thin product-lane agents, lightweight curation, and fashion-designer-output.json.
Use when a sandbox task needs to operate Meta Ads through the `meta` CLI: account/page preflight, campaign/ad set/ad/creative creation or updates, optional read-only status checks, insights reads, catalog/dataset/pixel checks, env mapping, command safety, redaction, and paused-by-default ad operations.
Use for Drip Performance Marketer work. Performance Marketer turns a generated Builder drop-site URL plus selected product images into one paused Facebook-only drop-of-week ad artifact, writes performance-marketer-output.json, and stops before activation, spend, insights readback, or optimization loops.
| name | x-trends |
| description | Use for generic X public-data research, trend discovery, recent-post checks, and social attention signals. Provides app-only bearer auth, endpoint patterns, field selection, error handling, and compact JSON evidence guidance. |
Use X as an attention and recency signal. This skill explains how to query public X endpoints and return compact evidence. The caller owns interpretation.
Use app-only bearer auth for public reads:
TOKEN="${X_BEARER_TOKEN:-$TWITTER_BEARER_TOKEN}"
Never print token values.
Use WOEID trend lookup first when a suitable WOEID is known:
curl -fsS "https://api.x.com/2/trends/by/woeid/1?max_trends=20&trend.fields=trend_name,tweet_count" \
-H "Authorization: Bearer $TOKEN"
Useful WOEIDs:
| Place | WOEID |
|---|---|
| Worldwide | 1 |
| India | 23424848 |
| Mumbai | 2295411 |
| Delhi | 20070458 |
| Bengaluru | 2295420 |
| United States | 23424977 |
| New York | 2459115 |
| London | 44418 |
For an unknown city/country, use worldwide plus the closest known country/city and note uncertainty.
If WOEID trends are unavailable, too broad, or opaque, use recent search for caller-supplied terms. Always request explicit fields because defaults are minimal.
curl -fsS "https://api.x.com/2/tweets/search/recent?max_results=25&query=<url-encoded-query>&tweet.fields=created_at,public_metrics,lang" \
-H "Authorization: Bearer $TOKEN"
Useful fields:
tweet.fields=created_at,public_metrics,langexpansions=author_id when author context mattersuser.fields=verified,public_metrics when author context is requestedWhen the caller supplies multiple markets, WOEIDs, topics, or query angles, run independent API calls in parallel when practical. Keep the merged return compact.
Parallelism is API-level. Do not spawn additional Codex subagents from this skill.
Return compact JSON-like evidence:
{
"source": "x",
"markets": ["worldwide", "india", "mumbai"],
"trendSignals": [
{
"name": "trend name",
"markets": ["india", "mumbai"],
"tweetCountMax": 12345,
"recentSearchQuery": null,
"notes": "short factual signal summary"
}
],
"errors": []
}