[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D6PCSEV0F9AV35SNXWGY3K":3,"skill-same:01M7D6PCSEV0F9AV35SNXWGY3K":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7D6PCSEV0F9AV35SNXWGY3K","pm-manipulation",null,"Detect suspected manipulation on prediction markets over the past 3 days by cross-referencing price\u002Fvolume\u002Fcomment anomalies with multilingual local-press coverage","LiamVisionary\u002Faeon-template","LiamVisionary","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102138294?v=4","01M73379NZZ99TT4ZS17XR3Q9D","01M7D6D62V1SGGMKGT08Q1D2R8",0,"MIT","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fpm-manipulation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pm-manipulation\ndescription: Detect suspected manipulation on prediction markets over the past 3 days by cross-referencing price\u002Fvolume\u002Fcomment anomalies with multilingual local-press coverage\nmetadata:\n  title: PM Manipulation\n  category: crypto\n  tags:\n    - crypto\n    - research\n    - security\n---\n\nRead `memory\u002FMEMORY.md` for context.\nRead the last 3 days of `memory\u002Flogs\u002F` to avoid re-flagging markets you already covered, and to compare current readings against prior ones.\n\n## Voice\n\nIf `soul\u002FSOUL.md` and `soul\u002FSTYLE.md` are populated, match the operator's voice in the notification and write-up. If empty or absent, use a clear, direct, neutral tone. The methodology itself is the same either way.\n\n## Why this skill exists\n\nEnglish-language coverage of any prediction market is dense for US politics, sparse for everything else. Election-, geopolitics-, and conflict-related markets are most often pushed by actors closer to the home country than to the English-speaking financial press. By the time a coordinated narrative lands in mainstream financial outlets, the trade is over. Local-language press, regional outlets, and country-specific Telegram \u002F X channels move first — sometimes by 24–72h.\n\nThis skill looks at the **past 3 days** of activity on a configurable prediction-market platform and asks: where does the price action diverge from organic English-press coverage, and does a multilingual sweep reveal a narrative push that explains it?\n\n## Configuration\n\nRead `memory\u002Ftopics\u002Fprediction-markets.md` if it exists for an optional `## Platform` line naming the target API root. Defaults to Polymarket's public Gamma + CLOB APIs (`gamma-api.polymarket.com`, `clob.polymarket.com`, `data-api.polymarket.com`). The candidate selection, scoring rubric, and multilingual sweep are platform-agnostic; only the endpoints differ.\n\nThe keyword filter and locale table below are starting points — the operator can edit `memory\u002Ftopics\u002Fprediction-markets.md` to add `## Keywords` and `## Locales` sections that override the defaults.\n\n## Network note\n\n`curl` works — there is no network sandbox. For every curl call, if it fails or returns empty, use **WebFetch** as a fallback for a flaky public GET. The Polymarket APIs above are public (no auth). For news searches, prefer **WebSearch** with locale-specific queries — a built-in Claude tool that needs no curl.\n\n## Steps\n\n### 1. Build the candidate set (markets active in past 3 days)\n\nPull the most-active markets across the categories most prone to manipulation: politics, geopolitics, conflict, elections (national and regional), regulatory rulings, and resolution-disputed markets.\n\n```bash\n# Top markets by 24h volume — repeat for last 3 days using volume24hr \u002F volume1wk fields\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fmarkets?closed=false&order=volume24hr&ascending=false&limit=30\"\n\n# Also fetch by 7d volume to catch slower-burn manipulation\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fmarkets?closed=false&order=volume1wk&ascending=false&limit=30\"\n```\n\nFrom the union of those two lists, pick **6–10 candidates** that meet at least one of:\n- Question references a non-US country, region, or conflict\n- Question references a regulatory body, election, or coup\u002Fconflict event\n- 7d volume > $500k AND 24h volume > $50k (real money, not just liquidity-mining)\n- Slug contains keywords (default set; operator can override in `memory\u002Ftopics\u002Fprediction-markets.md`): `russia`, `iran`, `israel`, `china`, `taiwan`, `ukraine`, `venezuela`, `argentina`, `mexico`, `brazil`, `india`, `pakistan`, `nigeria`, `france`, `germany`, `italy`, `spain`, `eu-`, `nato`, `cartel`, `coup`, `nuclear`, `assassination`, `ceasefire`, `election`, `vote`, `referendum`, `oracle`, `dispute`, `umip`\n\nSkip anything sports, weather, or pure crypto-price (BTC > $X by Y) — those have different manipulation signatures and aren't this skill's job.\n\n### 2. Pull 3-day price + trade data per candidate\n\nFor each candidate market, get the YES-token (`clobTokenIds[0]`) and pull 3-day price history at hourly fidelity:\n\n```bash\ncurl -s \"https:\u002F\u002Fclob.polymarket.com\u002Fprices-history?market=$TOKEN_ID&interval=1w&fidelity=60\"\n```\n\nCompute, from the past 72h window only:\n- **3d open \u002F close \u002F high \u002F low** (price 0.0–1.0)\n- **Largest single-hour move** (absolute pp change)\n- **Move concentration** — what % of the 3d net move happened in the single largest 6h block? If > 70%, flag `concentrated-move`.\n- **Volume spike ratio** — (peak hour volume) \u002F (median hour volume). If > 8x, flag `volume-spike`.\n- **Direction inversion** — did price reverse > 5pp within the 72h window? Flag `reversal` — common when a manipulator unwinds.\n\nAlso pull the trades feed if available (some markets only) for whale concentration:\n```bash\ncurl -s \"https:\u002F\u002Fdata-api.polymarket.com\u002Ftrades?market=$TOKEN_ID&limit=500\"\n```\nCompute **whale share** — % of 3d volume from the top-3 wallet addresses. If > 40%, flag `whale-concentrated`.\n\nIf the trades endpoint doesn't return per-market data, skip whale-share for that candidate — note it in the report rather than failing.\n\n### 3. Pull comments and detect coordination patterns\n\nFor each candidate, fetch comments from the past 3 days:\n\n```bash\n# Get the event id first (comments live on Event, not Market)\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fevents?slug=$EVENT_SLUG&limit=1\"\n\n# Top comments by reactions\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fcomments?parent_entity_type=Event&parent_entity_id=$EVENT_ID&limit=50&order=reactionCount&ascending=false\"\n\n# Most recent\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fcomments?parent_entity_type=Event&parent_entity_id=$EVENT_ID&limit=50&order=createdAt&ascending=false\"\n```\n\nFilter to comments from the last 72h (`createdAt` within window). Then look for:\n- **Burst posting** — > 10 comments from accounts with usernames matching the same regex pattern (e.g. `user\\d{4,}`, common spam-bot signature) within a 6h window. Flag `bot-burst`.\n- **Narrative concentration** — > 40% of top-reacted comments push the same one-sided talking point with near-identical phrasing. Flag `narrative-push`.\n- **Cross-market spam** — same usernames repeating identical text across multiple unrelated markets (compare against any logged comments from prior `pm-manipulation` runs). Flag `cross-market-spam`.\n\nApply a `reactionCount > 1` pre-filter before counting \"real\" reactions, but **do** count low-reaction comments toward bot-burst and narrative-concentration signals — that's exactly where the spam shows up.\n\n### 4. Multilingual press sweep — the actual differentiator\n\nFor each candidate that hit any anomaly flag in steps 2 or 3, run a localized press sweep targeting the country\u002Fregion most relevant to the question. The goal is to find coverage that explains (or **doesn't** explain) the price action, in the language of the place where the news would actually break first.\n\nPick 2–3 languages per market based on the topic. Suggested locale targets:\n\n| Topic \u002F region | Languages | Press domains (use as `site:` filters) |\n|---|---|---|\n| Russia \u002F Ukraine | ru, uk | `site:rbc.ru`, `site:tass.com`, `site:meduza.io`, `site:pravda.com.ua`, `site:kyivindependent.com` |\n| Iran \u002F Middle East | ar, fa, he | `site:aljazeera.net`, `site:alarabiya.net`, `site:irna.ir`, `site:ynet.co.il`, `site:haaretz.co.il` |\n| China \u002F Taiwan \u002F HK | zh-cn, zh-tw | `site:scmp.com`, `site:caixin.com`, `site:ltn.com.tw`, `site:cna.com.tw`, `site:rfa.org` |\n| Latin America | es, pt | `site:elpais.com`, `site:eltiempo.com`, `site:clarin.com`, `site:folha.uol.com.br`, `site:estadao.com.br`, `site:eluniversal.com.mx` |\n| Europe | fr, de, it, es | `site:lemonde.fr`, `site:lefigaro.fr`, `site:spiegel.de`, `site:zeit.de`, `site:repubblica.it`, `site:elmundo.es` |\n| India \u002F Pakistan | hi, ur, en-IN | `site:thehindu.com`, `site:timesofindia.indiatimes.com`, `site:dawn.com`, `site:tribune.com.pk` |\n| Africa | en-ZA, fr, ar | `site:dailymaverick.co.za`, `site:premiumtimesng.com`, `site:nation.africa`, `site:jeuneafrique.com` |\n\nFor each market × language pair:\n```\nWebSearch: \u003Cmarket keywords in target language> \u003Csite filters from table> [past 7 days]\n```\n\nTranslate keywords into the target language before searching. If you're not confident in a translation, ask via WebFetch a translation tool URL or skip that language with a note.\n\nAlso check **non-press** signals where coverage tends to break first:\n- Telegram channels (use WebSearch `t.me\u002F\u003Cchannel>`-style queries, plus general queries like `\"\u003Ctopic in language>\" telegram`)\n- Local-language X\u002FTwitter via WebSearch `\"\u003Ctopic in language>\" twitter.com`\n- Country-specific Reddit (`site:reddit.com\u002Fr\u002F\u003Ccountry>`)\n\nFor each candidate market record:\n- **Local-press timeline** — when did the first regional-language story drop? Was it before, during, or after the price move?\n- **Narrative direction** — does local press support the price move's direction, contradict it, or stay silent?\n- **Coverage asymmetry** — is the story dominant in one language and absent in English? That's the strongest manipulation tell — local actors trading their information advantage.\n\n### 5. Score each candidate (0–5 manipulation suspicion)\n\nSum the flags. Each is worth 1 point:\n- `concentrated-move` (>70% of 3d move in 6h)\n- `volume-spike` (peak\u002Fmedian > 8x)\n- `whale-concentrated` (top-3 wallets > 40% volume)\n- `bot-burst` OR `narrative-push` OR `cross-market-spam` (any one of these — comments only count once)\n- `reversal` (>5pp price reversal within 72h)\n- **Coverage asymmetry** — local press strongly supports OR contradicts the move while English press is silent (worth 1 point; if asymmetry is *strong* AND timing matches the price move within ±12h, worth 2 points and cap the total at 5)\n\nClassify:\n- **0–1 — clean.** No write-up, just log the slug and stop.\n- **2 — watch.** Brief note in the report, no notification.\n- **3 — suspicious.** Full write-up + notification.\n- **4–5 — high-confidence manipulation pattern.** Full write-up + urgent notification, file an issue under `memory\u002Fissues\u002F` with severity `medium`, category `unknown`, detected_by `pm-manipulation`.\n\nBe honest about uncertainty. \"Suspicious\" is not \"proof\". The skill's value is putting a watchlist in front of a human, not adjudicating fraud.\n\n### 6. Format the briefing\n\nBuild the body in a temp file (multi-line content; never argv-pipe long strings):\n\n```bash\nTEMP=$(mktemp -t pm-manipulation.XXXXXX.md)\ncat > \"$TEMP\" \u003C\u003C'MSG'\nPM Manipulation Watch — ${today} (past 3d)\n\nscanned: N markets · flagged: M · suspicious: K · high-conf: J\n\n--- SUSPICIOUS \u002F HIGH-CONFIDENCE ---\n\n1. \"[market question]\"  — score X\u002F5\n   slug: \u003Cevent-slug>\n   3d: $opens → $closes ($change pp), peak vol $X\n   flags: \u003Ccomma-separated flag names>\n   local press: \u003Cone-line summary of what foreign-language coverage said and when>\n   asymmetry: \u003Cenglish-silent | english-contradicts | english-confirms | n\u002Fa>\n   take: \u003Cone-sentence opinion — coordinated push? insider? unclear?>\n\n2. ...\n\n--- WATCH (score 2) ---\n- \"[question]\" — \u003Cone-line note>\n\n--- CLEAN (scanned but no flags) ---\nN markets, no anomalies above threshold.\n\nread it: output\u002Farticles\u002Fpm-manipulation-${today}.md\nMSG\n```\n\nKeep the notification under 3500 chars. If it exceeds, drop the CLEAN section and the WATCH bullets first; never truncate the SUSPICIOUS section mid-entry.\n\n### 7. Save the full report\n\nWrite the unabridged report to `output\u002Farticles\u002Fpm-manipulation-${today}.md`:\n\n```markdown\n# PM Manipulation Watch — ${today}\n\n**Window:** past 3 days · **Scanned:** N markets · **Suspicious (≥3):** K · **High-confidence (≥4):** J\n\n## Methodology\n3-day price\u002Fvolume\u002Fcomment scan + multilingual press sweep. Each candidate scored 0–5 across 6 anomaly classes. See `skills\u002Fpm-manipulation\u002FSKILL.md` for the full scoring rubric.\n\n## Suspicious Markets\n\n### 1. [Market question] — score X\u002F5\n- **Slug:** \u003Cevent-slug>\n- **3d action:** $open → $close (change pp), peak hour vol $X, whale share Y%\n- **Flags triggered:** \u003Clist>\n- **Comments:** \u003Ccoordinated patterns observed>\n- **Local press:**\n  - \u003Clanguage>: \u003Coutlet> — \u003Cone-line summary, date, link>\n  - \u003Clanguage>: \u003Coutlet> — ...\n- **English press:** \u003Coutlet — date — link, or \"silent\">\n- **Asymmetry:** \u003Cenglish-silent | english-contradicts | english-confirms | n\u002Fa>\n- **Take:** \u003C2–3 sentences>\n\n[repeat per suspicious market]\n\n## Watchlist (score 2)\n- ...\n\n## Clean\n[brief table: market, 3d change, why scanned]\n```\n\nCite every source with a URL. No untranslated quotes longer than ~10 words — render the original AND a short English gloss.\n\n### 8. Notify\n\n```bash\n.\u002Fnotify -f \"$TEMP\"\n```\n\nIf status is **high-confidence (≥4)**, prepend `[URGENT] ` to the notification subject so it surfaces in chat.\n\n### 9. Log\n\nAppend to `memory\u002Flogs\u002F${today}.md`:\n```\n### pm-manipulation\n- **Scanned:** N markets (past 3d)\n- **Suspicious (≥3):** K\n- **High-confidence (≥4):** J\n- **Top flag:** \"[market]\" — score X\u002F5\n- **Languages searched:** \u003Clist>\n- **Issues filed:** [ISS-NNN list or \"none\"]\n- **Notification sent:** yes \u002F no\n- PM_MANIPULATION_OK\n```\n\n## Guidelines\n\n- **Past 3 days only.** Older windows belong to one-off audits. Recency matters — manipulation is a near-term phenomenon, and stale signal turns this skill into noise.\n- **Multilingual is the differentiator.** A pure English scan is just a worse `monitor-polymarket`. The signal lives in coverage gaps between languages.\n- **No accusations.** Use words like \"suspected\", \"consistent with\", \"anomalous\", \"asymmetric coverage\". Never name actors as manipulators without direct evidence.\n- **Translate inline.** When quoting non-English press, give the original phrase + English gloss. Never paraphrase a foreign source as if it were English.\n- **No double-counting.** If a market was flagged in the last 3 days of `pm-manipulation` logs and the situation hasn't escalated, mention it as \"ongoing\" rather than re-running the full write-up.\n- **Quiet weeks are useful.** \"Scanned 8 markets, all clean\" is a valid output — flagging this skill as silent has signal of its own.\n\n## Environment Variables Required\n\n- None — uses public Polymarket APIs + WebSearch\u002FWebFetch\n- Notification channels configured via repo secrets (see CLAUDE.md)\n","Read `memory\u002FMEMORY.md` for context.\nRead the last 3 days of `memory\u002Flogs\u002F` to avoid re-flagging markets you already covered, and to compare current readings against prior ones.\n\n## Voice\n\nIf `soul\u002FSOUL.md` and `soul\u002FSTYLE.md` are populated, match the operator's voice in the notification and write-up. If empty or absent, use a clear, direct, neutral tone. The methodology itself is the same either way.\n\n## Why this skill exists\n\nEnglish-language coverage of any prediction market is dense for US politics, sparse for everything else. Election-, geopolitics-, and conflict-related markets are most often pushed by actors closer to the home country than to the English-speaking financial press. By the time a coordinated narrative lands in mainstream financial outlets, the trade is over. Local-language press, regional outlets, and country-specific Telegram \u002F X channels move first — sometimes by 24–72h.\n\nThis skill looks at the **past 3 days** of activity on a configurable prediction-market platform and asks: where does the price action diverge from organic English-press coverage, and does a multilingual sweep reveal a narrative push that explains it?\n\n## Configuration\n\nRead `memory\u002Ftopics\u002Fprediction-markets.md` if it exists for an optional `## Platform` line naming the target API root. Defaults to Polymarket's public Gamma + CLOB APIs (`gamma-api.polymarket.com`, `clob.polymarket.com`, `data-api.polymarket.com`). The candidate selection, scoring rubric, and multilingual sweep are platform-agnostic; only the endpoints differ.\n\nThe keyword filter and locale table below are starting points — the operator can edit `memory\u002Ftopics\u002Fprediction-markets.md` to add `## Keywords` and `## Locales` sections that override the defaults.\n\n## Network note\n\n`curl` works — there is no network sandbox. For every curl call, if it fails or returns empty, use **WebFetch** as a fallback for a flaky public GET. The Polymarket APIs above are public (no auth). For news searches, prefer **WebSearch** with locale-specific queries — a built-in Claude tool that needs no curl.\n\n## Steps\n\n### 1. Build the candidate set (markets active in past 3 days)\n\nPull the most-active markets across the categories most prone to manipulation: politics, geopolitics, conflict, elections (national and regional), regulatory rulings, and resolution-disputed markets.\n\n```bash\n# Top markets by 24h volume — repeat for last 3 days using volume24hr \u002F volume1wk fields\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fmarkets?closed=false&order=volume24hr&ascending=false&limit=30\"\n\n# Also fetch by 7d volume to catch slower-burn manipulation\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fmarkets?closed=false&order=volume1wk&ascending=false&limit=30\"\n```\n\nFrom the union of those two lists, pick **6–10 candidates** that meet at least one of:\n- Question references a non-US country, region, or conflict\n- Question references a regulatory body, election, or coup\u002Fconflict event\n- 7d volume > $500k AND 24h volume > $50k (real money, not just liquidity-mining)\n- Slug contains keywords (default set; operator can override in `memory\u002Ftopics\u002Fprediction-markets.md`): `russia`, `iran`, `israel`, `china`, `taiwan`, `ukraine`, `venezuela`, `argentina`, `mexico`, `brazil`, `india`, `pakistan`, `nigeria`, `france`, `germany`, `italy`, `spain`, `eu-`, `nato`, `cartel`, `coup`, `nuclear`, `assassination`, `ceasefire`, `election`, `vote`, `referendum`, `oracle`, `dispute`, `umip`\n\nSkip anything sports, weather, or pure crypto-price (BTC > $X by Y) — those have different manipulation signatures and aren't this skill's job.\n\n### 2. Pull 3-day price + trade data per candidate\n\nFor each candidate market, get the YES-token (`clobTokenIds[0]`) and pull 3-day price history at hourly fidelity:\n\n```bash\ncurl -s \"https:\u002F\u002Fclob.polymarket.com\u002Fprices-history?market=$TOKEN_ID&interval=1w&fidelity=60\"\n```\n\nCompute, from the past 72h window only:\n- **3d open \u002F close \u002F high \u002F low** (price 0.0–1.0)\n- **Largest single-hour move** (absolute pp change)\n- **Move concentration** — what % of the 3d net move happened in the single largest 6h block? If > 70%, flag `concentrated-move`.\n- **Volume spike ratio** — (peak hour volume) \u002F (median hour volume). If > 8x, flag `volume-spike`.\n- **Direction inversion** — did price reverse > 5pp within the 72h window? Flag `reversal` — common when a manipulator unwinds.\n\nAlso pull the trades feed if available (some markets only) for whale concentration:\n```bash\ncurl -s \"https:\u002F\u002Fdata-api.polymarket.com\u002Ftrades?market=$TOKEN_ID&limit=500\"\n```\nCompute **whale share** — % of 3d volume from the top-3 wallet addresses. If > 40%, flag `whale-concentrated`.\n\nIf the trades endpoint doesn't return per-market data, skip whale-share for that candidate — note it in the report rather than failing.\n\n### 3. Pull comments and detect coordination patterns\n\nFor each candidate, fetch comments from the past 3 days:\n\n```bash\n# Get the event id first (comments live on Event, not Market)\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fevents?slug=$EVENT_SLUG&limit=1\"\n\n# Top comments by reactions\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fcomments?parent_entity_type=Event&parent_entity_id=$EVENT_ID&limit=50&order=reactionCount&ascending=false\"\n\n# Most recent\ncurl -s \"https:\u002F\u002Fgamma-api.polymarket.com\u002Fcomments?parent_entity_type=Event&parent_entity_id=$EVENT_ID&limit=50&order=createdAt&ascending=false\"\n```\n\nFilter to comments from the last 72h (`createdAt` within window). Then look for:\n- **Burst posting** — > 10 comments from accounts with usernames matching the same regex pattern (e.g. `user\\d{4,}`, common spam-bot signature) within a 6h window. Flag `bot-burst`.\n- **Narrative concentration** — > 40% of top-reacted comments push the same one-sided talking point with near-identical phrasing. Flag `narrative-push`.\n- **Cross-market spam** — same usernames repeating identical text across multiple unrelated markets (compare against any logged comments from prior `pm-manipulation` runs). Flag `cross-market-spam`.\n\nApply a `reactionCount > 1` pre-filter before counting \"real\" reactions, but **do** count low-reaction comments toward bot-burst and narrative-concentration signals — that's exactly where the spam shows up.\n\n### 4. Multilingual press sweep — the actual differentiator\n\nFor each candidate that hit any anomaly flag in steps 2 or 3, run a localized press sweep targeting the country\u002Fregion most relevant to the question. The goal is to find coverage that explains (or **doesn't** explain) the price action, in the language of the place where the news would actually break first.\n\nPick 2–3 languages per market based on the topic. Suggested locale targets:\n\n| Topic \u002F region | Languages | Press domains (use as `site:` filters) |\n|---|---|---|\n| Russia \u002F Ukraine | ru, uk | `site:rbc.ru`, `site:tass.com`, `site:meduza.io`, `site:pravda.com.ua`, `site:kyivindependent.com` |\n| Iran \u002F Middle East | ar, fa, he | `site:aljazeera.net`, `site:alarabiya.net`, `site:irna.ir`, `site:ynet.co.il`, `site:haaretz.co.il` |\n| China \u002F Taiwan \u002F HK | zh-cn, zh-tw | `site:scmp.com`, `site:caixin.com`, `site:ltn.com.tw`, `site:cna.com.tw`, `site:rfa.org` |\n| Latin America | es, pt | `site:elpais.com`, `site:eltiempo.com`, `site:clarin.com`, `site:folha.uol.com.br`, `site:estadao.com.br`, `site:eluniversal.com.mx` |\n| Europe | fr, de, it, es | `site:lemonde.fr`, `site:lefigaro.fr`, `site:spiegel.de`, `site:zeit.de`, `site:repubblica.it`, `site:elmundo.es` |\n| India \u002F Pakistan | hi, ur, en-IN | `site:thehindu.com`, `site:timesofindia.indiatimes.com`, `site:dawn.com`, `site:tribune.com.pk` |\n| Africa | en-ZA, fr, ar | `site:dailymaverick.co.za`, `site:premiumtimesng.com`, `site:nation.africa`, `site:jeuneafrique.com` |\n\nFor each market × language pair:\n```\nWebSearch: \u003Cmarket keywords in target language> \u003Csite filters from table> [past 7 days]\n```\n\nTranslate keywords into the target language before searching. If you're not confident in a translation, ask via WebFetch a translation tool URL or skip that language with a note.\n\nAlso check **non-press** signals where coverage tends to break first:\n- Telegram channels (use WebSearch `t.me\u002F\u003Cchannel>`-style queries, plus general queries like `\"\u003Ctopic in language>\" telegram`)\n- Local-language X\u002FTwitter via WebSearch `\"\u003Ctopic in language>\" twitter.com`\n- Country-specific Reddit (`site:reddit.com\u002Fr\u002F\u003Ccountry>`)\n\nFor each candidate market record:\n- **Local-press timeline** — when did the first regional-language story drop? Was it before, during, or after the price move?\n- **Narrative direction** — does local press support the price move's direction, contradict it, or stay silent?\n- **Coverage asymmetry** — is the story dominant in one language and absent in English? That's the strongest manipulation tell — local actors trading their information advantage.\n\n### 5. Score each candidate (0–5 manipulation suspicion)\n\nSum the flags. Each is worth 1 point:\n- `concentrated-move` (>70% of 3d move in 6h)\n- `volume-spike` (peak\u002Fmedian > 8x)\n- `whale-concentrated` (top-3 wallets > 40% volume)\n- `bot-burst` OR `narrative-push` OR `cross-market-spam` (any one of these — comments only count once)\n- `reversal` (>5pp price reversal within 72h)\n- **Coverage asymmetry** — local press strongly supports OR contradicts the move while English press is silent (worth 1 point; if asymmetry is *strong* AND timing matches the price move within ±12h, worth 2 points and cap the total at 5)\n\nClassify:\n- **0–1 — clean.** No write-up, just log the slug and stop.\n- **2 — watch.** Brief note in the report, no notification.\n- **3 — suspicious.** Full write-up + notification.\n- **4–5 — high-confidence manipulation pattern.** Full write-up + urgent notification, file an issue under `memory\u002Fissues\u002F` with severity `medium`, category `unknown`, detected_by `pm-manipulation`.\n\nBe honest about uncertainty. \"Suspicious\" is not \"proof\". The skill's value is putting a watchlist in front of a human, not adjudicating fraud.\n\n### 6. Format the briefing\n\nBuild the body in a temp file (multi-line content; never argv-pipe long strings):\n\n```bash\nTEMP=$(mktemp -t pm-manipulation.XXXXXX.md)\ncat > \"$TEMP\" \u003C\u003C'MSG'\nPM Manipulation Watch — ${today} (past 3d)\n\nscanned: N markets · flagged: M · suspicious: K · high-conf: J\n\n--- SUSPICIOUS \u002F HIGH-CONFIDENCE ---\n\n1. \"[market question]\"  — score X\u002F5\n   slug: \u003Cevent-slug>\n   3d: $opens → $closes ($change pp), peak vol $X\n   flags: \u003Ccomma-separated flag names>\n   local press: \u003Cone-line summary of what foreign-language coverage said and when>\n   asymmetry: \u003Cenglish-silent | english-contradicts | english-confirms | n\u002Fa>\n   take: \u003Cone-sentence opinion — coordinated push? insider? unclear?>\n\n2. ...\n\n--- WATCH (score 2) ---\n- \"[question]\" — \u003Cone-line note>\n\n--- CLEAN (scanned but no flags) ---\nN markets, no anomalies above threshold.\n\nread it: output\u002Farticles\u002Fpm-manipulation-${today}.md\nMSG\n```\n\nKeep the notification under 3500 chars. If it exceeds, drop the CLEAN section and the WATCH bullets first; never truncate the SUSPICIOUS section mid-entry.\n\n### 7. Save the full report\n\nWrite the unabridged report to `output\u002Farticles\u002Fpm-manipulation-${today}.md`:\n\n```markdown\n# PM Manipulation Watch — ${today}\n\n**Window:** past 3 days · **Scanned:** N markets · **Suspicious (≥3):** K · **High-confidence (≥4):** J\n\n## Methodology\n3-day price\u002Fvolume\u002Fcomment scan + multilingual press sweep. Each candidate scored 0–5 across 6 anomaly classes. See `skills\u002Fpm-manipulation\u002FSKILL.md` for the full scoring rubric.\n\n## Suspicious Markets\n\n### 1. [Market question] — score X\u002F5\n- **Slug:** \u003Cevent-slug>\n- **3d action:** $open → $close (change pp), peak hour vol $X, whale share Y%\n- **Flags triggered:** \u003Clist>\n- **Comments:** \u003Ccoordinated patterns observed>\n- **Local press:**\n  - \u003Clanguage>: \u003Coutlet> — \u003Cone-line summary, date, link>\n  - \u003Clanguage>: \u003Coutlet> — ...\n- **English press:** \u003Coutlet — date — link, or \"silent\">\n- **Asymmetry:** \u003Cenglish-silent | english-contradicts | english-confirms | n\u002Fa>\n- **Take:** \u003C2–3 sentences>\n\n[repeat per suspicious market]\n\n## Watchlist (score 2)\n- ...\n\n## Clean\n[brief table: market, 3d change, why scanned]\n```\n\nCite every source with a URL. No untranslated quotes longer than ~10 words — render the original AND a short English gloss.\n\n### 8. Notify\n\n```bash\n.\u002Fnotify -f \"$TEMP\"\n```\n\nIf status is **high-confidence (≥4)**, prepend `[URGENT] ` to the notification subject so it surfaces in chat.\n\n### 9. Log\n\nAppend to `memory\u002Flogs\u002F${today}.md`:\n```\n### pm-manipulation\n- **Scanned:** N markets (past 3d)\n- **Suspicious (≥3):** K\n- **High-confidence (≥4):** J\n- **Top flag:** \"[market]\" — score X\u002F5\n- **Languages searched:** \u003Clist>\n- **Issues filed:** [ISS-NNN list or \"none\"]\n- **Notification sent:** yes \u002F no\n- PM_MANIPULATION_OK\n```\n\n## Guidelines\n\n- **Past 3 days only.** Older windows belong to one-off audits. Recency matters — manipulation is a near-term phenomenon, and stale signal turns this skill into noise.\n- **Multilingual is the differentiator.** A pure English scan is just a worse `monitor-polymarket`. The signal lives in coverage gaps between languages.\n- **No accusations.** Use words like \"suspected\", \"consistent with\", \"anomalous\", \"asymmetric coverage\". Never name actors as manipulators without direct evidence.\n- **Translate inline.** When quoting non-English press, give the original phrase + English gloss. Never paraphrase a foreign source as if it were English.\n- **No double-counting.** If a market was flagged in the last 3 days of `pm-manipulation` logs and the situation hasn't escalated, mention it as \"ongoing\" rather than re-running the full write-up.\n- **Quiet weeks are useful.** \"Scanned 8 markets, all clean\" is a valid output — flagging this skill as silent has signal of its own.\n\n## Environment Variables Required\n\n- None — uses public Polymarket APIs + WebSearch\u002FWebFetch\n- Notification channels configured via repo secrets (see CLAUDE.md)\n",{"name":5,"metadata":23,"description":7},{"tags":24,"title":28,"category":25},[25,26,27],"crypto","research","security","PM Manipulation","main","fa8f75cd49adcad9214508fdb5d1ead8fab420be","skills\u002Fpm-manipulation","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template","https:\u002F\u002Fgithub.com\u002FLiamVisionary","2026-11-15 04:34:04",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add LiamVisionary\u002Faeon-template --skill pm-manipulation",{"tool":41,"command":42},"bunx","bunx skills add LiamVisionary\u002Faeon-template --skill pm-manipulation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add LiamVisionary\u002Faeon-template --skill pm-manipulation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fpm-manipulation\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7D6W8WRJH3JVJ2JQ674AD77","you-web-search","Web search using You.com Search API with high-quality, cited results and optional real-time web crawling","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fyou-web-search\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7D6W2XPBZZPPXPX76WMPSDA","write-tweet","Multi-format tweet studio - standalone drafts (10 across 5 size tiers), a 5-10 tweet thread, or 10 remixes of past tweets, selected via ${var}","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-tweet\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7D6VZVWK4RATPHM90N71QZD","weekly-aeoncard","Build a weekly token-consumption recap image from memory\u002Ftoken-usage.csv - this week + all-time totals, top skills, rendered as a shareable SVG card.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-aeoncard\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7D6VQ7H3DHAAP0BEWTC3HK4","vuln-tracker","One lifecycle poll over everything vuln-scanner produces - PR and advisory status, PVR triage transitions, and pending-disclosure aging, with a stars-secured impact headline and one action queue.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-tracker\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7D6VDRA94RJKDPKJ65S47KT","vuln-scanner","Audit trending repos for real security vulnerabilities and disclose responsibly - scan and route findings (PVR \u002F dependency PR), re-submit queued advisories, and send armed email disclosures","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-scanner\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7D6V8BNPHCTPJBJD89H8DZF","video-script","Turn a repo, product page, or update into a recording-ready video script in a receipts-first format - verifies every claim against live sources, then writes timestamped VO + on-screen direction with a plain-language glossary, assets checklist, anti-tells, and a verify-before-recording list","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-script\u002FSKILL.md",[],[]]