[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DC8MMF2NDRC8EXSY59S9YS":3,"skill-same:01M7DC8MMF2NDRC8EXSY59S9YS":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M7DC8MMF2NDRC8EXSY59S9YS","mention-radar",null,"Monitor external web and social mentions of the operator's active projects - surface what people are discovering, where they're confused, and where to engage","Ditto190\u002FAeon-automaton-codeyourself-mm","Ditto190","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110319982?v=4","01M7DBZRW755H8JSCQH6WFBM2P","01M7DBZRXAPWXAR6K6M6C53MCQ",0,"MIT","https:\u002F\u002Fgithub.com\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fmention-radar\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mention-radar\ndescription: Monitor external web and social mentions of the operator's active projects - surface what people are discovering, where they're confused, and where to engage\nmetadata:\n  title: Mention Radar\n  category: productivity\n  schedule: \"25 7 2\u002F2 * *\"\n  commits: false\n  var: \"\"\n  tags:\n    - social\n    - dev\n  requires:\n    - XAI_API_KEY?\n---\n> **${var}** — Comma-separated project names to track (e.g. \"MyApp, my-lib\"). If empty, derives targets from MEMORY.md and memory\u002Ftopics\u002Fprojects.md.\n\nRead memory\u002FMEMORY.md for current project status.\nRead the last 3 days of memory\u002Flogs\u002F to avoid re-surfacing already-noted mentions.\n\n## Steps\n\n1. **Define the targets.**\n   - If `${var}` is set: parse it as a comma-separated list of project names.\n   - Otherwise: scan `memory\u002FMEMORY.md` (goals, active topics) and `memory\u002Ftopics\u002Fprojects.md` (if it exists) for the operator's active projects. A target needs at least a name; collect a site\u002Fdomain and a GitHub `owner\u002Frepo` too when known.\n   - Cap at 6 targets — prefer the most active ones.\n   - If zero targets can be derived: log `MENTION_RADAR_SKIP: no projects configured — set var or add projects to memory\u002Ftopics\u002Fprojects.md` and stop. No notification.\n\n   For each target, build search terms:\n   - The exact project name in quotes (e.g. `\"MyApp\" site:x.com OR site:reddit.com OR site:news.ycombinator.com`)\n   - The domain if known (e.g. `\"myapp.xyz\"`)\n   - The repo if known (e.g. `site:github.com owner\u002Fmyapp`)\n\n2. **Search for external mentions.** X\u002FTwitter is fetched via the X.AI Responses API (**primary**); the rest of the public web (Reddit, Farcaster, blogs, newsletters, GitHub Discussions, HN, Product Hunt) goes through WebSearch, which is also the **last-resort fallback** for X itself. Derive the operator's handle from `soul\u002FSOUL.md` if present (call it `$OPERATOR`) so you can exclude their own posts.\n\n   **Path A — X.AI API (primary, X\u002FTwitter mentions).** For each target, ask Grok's `x_search` who is talking about the project on X. See the **Fetching** contract below — attempt this whenever the key is present, set the Bash tool `timeout` to ≥180000, and capture the HTTP status. Use a unique tmp filename per target if you loop (e.g. `\u002Ftmp\u002Fxai-mr-$SLUG.json`). `$NAME`\u002F`$DOMAIN`\u002F`$REPO` come from the target built in step 1 (`$DOMAIN`\u002F`$REPO` may be empty — leave them out if so):\n   ```bash\n   FROM_DATE=$(date -u -d \"7 days ago\" +%Y-%m-%d 2>\u002Fdev\u002Fnull || date -u -v-7d +%Y-%m-%d)\n   TO_DATE=$(date -u +%Y-%m-%d)\n   PROMPT=\"Search X for posts by OTHER people mentioning the project \\\"${NAME}\\\" (also its site ${DOMAIN} and repo ${REPO} when given), posted between ${FROM_DATE} and ${TO_DATE}. Exclude posts by the operator @${OPERATOR} and by the project's own accounts. For each mention return: @handle, the full post text, date, exact engagement counts (likes, retweets, replies; 0 if unknown), the poster's approximate follower count if visible, and the direct link https:\u002F\u002Fx.com\u002Fhandle\u002Fstatus\u002FID. Prioritize people discovering it for the first time, asking confused questions, hitting friction (setup\u002Fdocs\u002Fmissing feature), comparing it to a competitor, or requesting a feature. Return a numbered list; if nobody is talking about it, say so explicitly.\"\n   jq -n --arg p \"$PROMPT\" --arg fd \"$FROM_DATE\" --arg td \"$TO_DATE\" \\\n     '{model:\"grok-4.6\", input:[{role:\"user\",content:$p}], tools:[{type:\"x_search\",from_date:$fd,to_date:$td}]}' \\\n     > \u002Ftmp\u002Fxai-mr-payload.json\n   HTTP=$(.\u002Fsecretcurl -s -o \u002Ftmp\u002Fxai-mr.json -w '%{http_code}' --max-time 150 -X POST \"https:\u002F\u002Fapi.x.ai\u002Fv1\u002Fresponses\" \\\n     -H \"Content-Type: application\u002Fjson\" \\\n     -H \"Authorization: Bearer {XAI_API_KEY}\" \\\n     -d @\u002Ftmp\u002Fxai-mr-payload.json)\n   echo \"xai http=$HTTP bytes=$(wc -c \u003C\u002Ftmp\u002Fxai-mr.json)\"\n   ```\n   On `HTTP=200` with a non-empty body, parse `\u002Ftmp\u002Fxai-mr.json` with `jq -r '.output[] | select(.type == \"message\") | .content[] | select(.type == \"output_text\") | .text'` and feed the X mentions into categorization (step 4). Record `X_SOURCE=api`.\n\n   **Path B — WebSearch (broader web + X fallback).** Always use WebSearch for the non-X surfaces — Reddit, Farcaster, personal blogs, newsletters, GitHub Discussions, HN, Product Hunt:\n   - Try both brand name and URL variants\n   - Time-box to last 7 days where the search engine supports it\n   - Skip results from the operator's own accounts and the project's own repos\n\n   WebSearch is **also** the fallback for X\u002FTwitter, but only when Path A truly failed (`key-unset`, `http-\u003Ccode>`, `empty`, or `timeout` — record the real reason per the **Fetching** contract, never \"XAI_API_KEY unavailable\" when the key was set). On the X fallback query `site:x.com \"\u003Cproject name>\" after:${FROM_DATE}`; note in the log that X results came from WebSearch (lower quality) and set `X_SOURCE=websearch`.\n\n3. **Also check GitHub network signals** for each target with a known repo:\n   ```bash\n   gh api repos\u002FOWNER\u002FREPO --jq '{stars: .stargazers_count, forks: .forks_count, watchers: .watchers_count}'\n   ```\n   Skip any repo that 404s (private or not yet public). Compare to the last log entry to compute deltas. If no prior data, record as baseline.\n\n4. **Categorize each mention** found:\n   - **Discovery** — person found the project for the first time, sharing it, impressed (\"this is cool\", star notification, share)\n   - **Confusion** — person unclear on what it does, asking questions, mischaracterizing it\n   - **Friction** — person ran into a problem (setup, docs, missing feature)\n   - **Competitor comparison** — mentioned alongside or against a competing project\n   - **Feature request \u002F wish** — explicit ask for something missing\n   - **Press \u002F newsletter** — cited in a publication or digest\n\n5. **Identify engagement opportunities.** Flag any mention where:\n   - The person is confused and a 1-tweet clarification would help\n   - A feature request aligns with what's being built\n   - A competitor comparison is wrong or incomplete\n   - A high-follower account discovered the project (high-leverage reply opportunity)\n\n6. **Format the output** (under 4000 chars):\n   ```\n   *Mention Radar — ${today}*\n\n   {PROJECT NAME, uppercased}\n   - [source] — [what they said] — [category]\n   ...\n   (one section per target)\n\n   ENGAGEMENT OPPORTUNITIES\n   - [handle\u002Fsource]: [why worth replying]\n\n   QUIET: [project] — no external mentions found\n   ```\n   Use `QUIET: [project]` for any project with zero external mentions this cycle.\n   Skip GitHub-only star delta if it's less than 5 — only mention notable jumps.\n\n7. **Only notify if there's signal.** Skip notification if ALL projects are quiet and no GitHub deltas > 5 stars. Log `MENTION_RADAR_QUIET` instead.\n\n8. **Send via `.\u002Fnotify`** if there's anything worth surfacing.\n\n9. **Log to memory\u002Flogs\u002F${today}.md**:\n   ```\n   ### mention-radar\n   - **{project}:** [N mentions \u002F QUIET]\n   (one line per target)\n   - **Top find:** [best mention in one line, or \"none\"]\n   - **Engagement opps:** [N flagged, or 0]\n   - **Notification sent:** yes\u002Fno\n   ```\n\n## Guidelines\n\n- This is signal filtering, not a metrics report. One real conversation > ten impressions.\n- Prioritize quality of mention over quantity. A thoughtful Reddit post or HN comment matters more than a retweet.\n- Don't manufacture urgency. If there's nothing worth acting on, say so.\n- Be specific — link the source, quote the key line, name the person if identifiable.\n- The point is engagement opportunity and awareness, not vanity numbers.\n\n## Fetching\n\n`XAI_API_KEY` is **injected into your environment** for this skill (declared in `requires:`). It is present and valid. **The primary fetch path for X\u002FTwitter mentions is a direct `curl` to `https:\u002F\u002Fapi.x.ai\u002Fv1\u002Fresponses` with `Authorization: Bearer {XAI_API_KEY}`** (step 2, Path A). There is no network sandbox blocking this; earlier versions of this skill claimed there was — that is stale and wrong. Just make the call.\n\n**You MUST attempt the direct curl before any X fallback.** The rules:\n\n1. **Check, don't assume.** Run `[ -n \"$XAI_API_KEY\" ] && echo KEY_PRESENT || echo KEY_UNSET`. If `KEY_PRESENT` (it will be), you are required to try Path A.\n2. **Allow enough time.** The `x_search` call typically takes 30–120s (it searches X live). When you invoke the Bash tool for the curl, **set the tool's `timeout` to at least 180000 (180s)**, and keep **`--max-time 150`** on the curl itself so it fails cleanly rather than hanging. A curl that is slow is **not** a missing key — do not treat a timeout as \"key unavailable\".\n3. **Capture the HTTP status** so the fallback decision is based on fact, not assumption. Build the payload to the fixed file `\u002Ftmp\u002Fxai-mr-payload.json` first (the `jq -n --arg` in Path A), then send it with `-d @file` — the `.\u002Fsecretcurl` command must stay 100% literal (no `$VAR`):\n   ```bash\n   HTTP=$(.\u002Fsecretcurl -s -o \u002Ftmp\u002Fxai-mr.json -w '%{http_code}' --max-time 150 -X POST \"https:\u002F\u002Fapi.x.ai\u002Fv1\u002Fresponses\" \\\n     -H \"Content-Type: application\u002Fjson\" -H \"Authorization: Bearer {XAI_API_KEY}\" -d @\u002Ftmp\u002Fxai-mr-payload.json)\n   echo \"xai http=$HTTP bytes=$(wc -c \u003C\u002Ftmp\u002Fxai-mr.json)\"\n   ```\n   Then parse `\u002Ftmp\u002Fxai-mr.json` with the standard `jq` extractor. `HTTP=200` with a non-empty body → use it (`X_SOURCE=api`).\n4. **Fall back only on a real failure**, and **record the true reason** — never write \"XAI_API_KEY unavailable\" when the key was set. Use one of: `key-unset` (only if step 1 said `KEY_UNSET`), `http-\u003Ccode>` (non-2xx), `empty` (200 but no mentions parsed), `timeout` (curl exceeded `--max-time`).\n\n**WebSearch \u002F WebFetch are last-resort fallbacks only** for X — lower quality (WebSearch favours old high-engagement tweets). They remain the primary tool for the non-X web surfaces (Reddit, HN, blogs, etc.). Never reach for the X WebSearch fallback while the key works.\n\n## Environment Variables\n\n- `XAI_API_KEY` — X.AI API key for Grok's `x_search` tool. Declared in `requires:` (optional `?`), so it is **injected into this skill's environment** and is the primary path for X\u002FTwitter mentions. If it is ever unset, X mentions degrade to the WebSearch fallback at lower quality; the broader-web search is unaffected.\n- `gh` CLI — pre-authenticated in GitHub Actions; used for the GitHub network-signal check (step 3). Not an env var you set here.\n","> **${var}** — Comma-separated project names to track (e.g. \"MyApp, my-lib\"). If empty, derives targets from MEMORY.md and memory\u002Ftopics\u002Fprojects.md.\n\nRead memory\u002FMEMORY.md for current project status.\nRead the last 3 days of memory\u002Flogs\u002F to avoid re-surfacing already-noted mentions.\n\n## Steps\n\n1. **Define the targets.**\n   - If `${var}` is set: parse it as a comma-separated list of project names.\n   - Otherwise: scan `memory\u002FMEMORY.md` (goals, active topics) and `memory\u002Ftopics\u002Fprojects.md` (if it exists) for the operator's active projects. A target needs at least a name; collect a site\u002Fdomain and a GitHub `owner\u002Frepo` too when known.\n   - Cap at 6 targets — prefer the most active ones.\n   - If zero targets can be derived: log `MENTION_RADAR_SKIP: no projects configured — set var or add projects to memory\u002Ftopics\u002Fprojects.md` and stop. No notification.\n\n   For each target, build search terms:\n   - The exact project name in quotes (e.g. `\"MyApp\" site:x.com OR site:reddit.com OR site:news.ycombinator.com`)\n   - The domain if known (e.g. `\"myapp.xyz\"`)\n   - The repo if known (e.g. `site:github.com owner\u002Fmyapp`)\n\n2. **Search for external mentions.** X\u002FTwitter is fetched via the X.AI Responses API (**primary**); the rest of the public web (Reddit, Farcaster, blogs, newsletters, GitHub Discussions, HN, Product Hunt) goes through WebSearch, which is also the **last-resort fallback** for X itself. Derive the operator's handle from `soul\u002FSOUL.md` if present (call it `$OPERATOR`) so you can exclude their own posts.\n\n   **Path A — X.AI API (primary, X\u002FTwitter mentions).** For each target, ask Grok's `x_search` who is talking about the project on X. See the **Fetching** contract below — attempt this whenever the key is present, set the Bash tool `timeout` to ≥180000, and capture the HTTP status. Use a unique tmp filename per target if you loop (e.g. `\u002Ftmp\u002Fxai-mr-$SLUG.json`). `$NAME`\u002F`$DOMAIN`\u002F`$REPO` come from the target built in step 1 (`$DOMAIN`\u002F`$REPO` may be empty — leave them out if so):\n   ```bash\n   FROM_DATE=$(date -u -d \"7 days ago\" +%Y-%m-%d 2>\u002Fdev\u002Fnull || date -u -v-7d +%Y-%m-%d)\n   TO_DATE=$(date -u +%Y-%m-%d)\n   PROMPT=\"Search X for posts by OTHER people mentioning the project \\\"${NAME}\\\" (also its site ${DOMAIN} and repo ${REPO} when given), posted between ${FROM_DATE} and ${TO_DATE}. Exclude posts by the operator @${OPERATOR} and by the project's own accounts. For each mention return: @handle, the full post text, date, exact engagement counts (likes, retweets, replies; 0 if unknown), the poster's approximate follower count if visible, and the direct link https:\u002F\u002Fx.com\u002Fhandle\u002Fstatus\u002FID. Prioritize people discovering it for the first time, asking confused questions, hitting friction (setup\u002Fdocs\u002Fmissing feature), comparing it to a competitor, or requesting a feature. Return a numbered list; if nobody is talking about it, say so explicitly.\"\n   jq -n --arg p \"$PROMPT\" --arg fd \"$FROM_DATE\" --arg td \"$TO_DATE\" \\\n     '{model:\"grok-4.6\", input:[{role:\"user\",content:$p}], tools:[{type:\"x_search\",from_date:$fd,to_date:$td}]}' \\\n     > \u002Ftmp\u002Fxai-mr-payload.json\n   HTTP=$(.\u002Fsecretcurl -s -o \u002Ftmp\u002Fxai-mr.json -w '%{http_code}' --max-time 150 -X POST \"https:\u002F\u002Fapi.x.ai\u002Fv1\u002Fresponses\" \\\n     -H \"Content-Type: application\u002Fjson\" \\\n     -H \"Authorization: Bearer {XAI_API_KEY}\" \\\n     -d @\u002Ftmp\u002Fxai-mr-payload.json)\n   echo \"xai http=$HTTP bytes=$(wc -c \u003C\u002Ftmp\u002Fxai-mr.json)\"\n   ```\n   On `HTTP=200` with a non-empty body, parse `\u002Ftmp\u002Fxai-mr.json` with `jq -r '.output[] | select(.type == \"message\") | .content[] | select(.type == \"output_text\") | .text'` and feed the X mentions into categorization (step 4). Record `X_SOURCE=api`.\n\n   **Path B — WebSearch (broader web + X fallback).** Always use WebSearch for the non-X surfaces — Reddit, Farcaster, personal blogs, newsletters, GitHub Discussions, HN, Product Hunt:\n   - Try both brand name and URL variants\n   - Time-box to last 7 days where the search engine supports it\n   - Skip results from the operator's own accounts and the project's own repos\n\n   WebSearch is **also** the fallback for X\u002FTwitter, but only when Path A truly failed (`key-unset`, `http-\u003Ccode>`, `empty`, or `timeout` — record the real reason per the **Fetching** contract, never \"XAI_API_KEY unavailable\" when the key was set). On the X fallback query `site:x.com \"\u003Cproject name>\" after:${FROM_DATE}`; note in the log that X results came from WebSearch (lower quality) and set `X_SOURCE=websearch`.\n\n3. **Also check GitHub network signals** for each target with a known repo:\n   ```bash\n   gh api repos\u002FOWNER\u002FREPO --jq '{stars: .stargazers_count, forks: .forks_count, watchers: .watchers_count}'\n   ```\n   Skip any repo that 404s (private or not yet public). Compare to the last log entry to compute deltas. If no prior data, record as baseline.\n\n4. **Categorize each mention** found:\n   - **Discovery** — person found the project for the first time, sharing it, impressed (\"this is cool\", star notification, share)\n   - **Confusion** — person unclear on what it does, asking questions, mischaracterizing it\n   - **Friction** — person ran into a problem (setup, docs, missing feature)\n   - **Competitor comparison** — mentioned alongside or against a competing project\n   - **Feature request \u002F wish** — explicit ask for something missing\n   - **Press \u002F newsletter** — cited in a publication or digest\n\n5. **Identify engagement opportunities.** Flag any mention where:\n   - The person is confused and a 1-tweet clarification would help\n   - A feature request aligns with what's being built\n   - A competitor comparison is wrong or incomplete\n   - A high-follower account discovered the project (high-leverage reply opportunity)\n\n6. **Format the output** (under 4000 chars):\n   ```\n   *Mention Radar — ${today}*\n\n   {PROJECT NAME, uppercased}\n   - [source] — [what they said] — [category]\n   ...\n   (one section per target)\n\n   ENGAGEMENT OPPORTUNITIES\n   - [handle\u002Fsource]: [why worth replying]\n\n   QUIET: [project] — no external mentions found\n   ```\n   Use `QUIET: [project]` for any project with zero external mentions this cycle.\n   Skip GitHub-only star delta if it's less than 5 — only mention notable jumps.\n\n7. **Only notify if there's signal.** Skip notification if ALL projects are quiet and no GitHub deltas > 5 stars. Log `MENTION_RADAR_QUIET` instead.\n\n8. **Send via `.\u002Fnotify`** if there's anything worth surfacing.\n\n9. **Log to memory\u002Flogs\u002F${today}.md**:\n   ```\n   ### mention-radar\n   - **{project}:** [N mentions \u002F QUIET]\n   (one line per target)\n   - **Top find:** [best mention in one line, or \"none\"]\n   - **Engagement opps:** [N flagged, or 0]\n   - **Notification sent:** yes\u002Fno\n   ```\n\n## Guidelines\n\n- This is signal filtering, not a metrics report. One real conversation > ten impressions.\n- Prioritize quality of mention over quantity. A thoughtful Reddit post or HN comment matters more than a retweet.\n- Don't manufacture urgency. If there's nothing worth acting on, say so.\n- Be specific — link the source, quote the key line, name the person if identifiable.\n- The point is engagement opportunity and awareness, not vanity numbers.\n\n## Fetching\n\n`XAI_API_KEY` is **injected into your environment** for this skill (declared in `requires:`). It is present and valid. **The primary fetch path for X\u002FTwitter mentions is a direct `curl` to `https:\u002F\u002Fapi.x.ai\u002Fv1\u002Fresponses` with `Authorization: Bearer {XAI_API_KEY}`** (step 2, Path A). There is no network sandbox blocking this; earlier versions of this skill claimed there was — that is stale and wrong. Just make the call.\n\n**You MUST attempt the direct curl before any X fallback.** The rules:\n\n1. **Check, don't assume.** Run `[ -n \"$XAI_API_KEY\" ] && echo KEY_PRESENT || echo KEY_UNSET`. If `KEY_PRESENT` (it will be), you are required to try Path A.\n2. **Allow enough time.** The `x_search` call typically takes 30–120s (it searches X live). When you invoke the Bash tool for the curl, **set the tool's `timeout` to at least 180000 (180s)**, and keep **`--max-time 150`** on the curl itself so it fails cleanly rather than hanging. A curl that is slow is **not** a missing key — do not treat a timeout as \"key unavailable\".\n3. **Capture the HTTP status** so the fallback decision is based on fact, not assumption. Build the payload to the fixed file `\u002Ftmp\u002Fxai-mr-payload.json` first (the `jq -n --arg` in Path A), then send it with `-d @file` — the `.\u002Fsecretcurl` command must stay 100% literal (no `$VAR`):\n   ```bash\n   HTTP=$(.\u002Fsecretcurl -s -o \u002Ftmp\u002Fxai-mr.json -w '%{http_code}' --max-time 150 -X POST \"https:\u002F\u002Fapi.x.ai\u002Fv1\u002Fresponses\" \\\n     -H \"Content-Type: application\u002Fjson\" -H \"Authorization: Bearer {XAI_API_KEY}\" -d @\u002Ftmp\u002Fxai-mr-payload.json)\n   echo \"xai http=$HTTP bytes=$(wc -c \u003C\u002Ftmp\u002Fxai-mr.json)\"\n   ```\n   Then parse `\u002Ftmp\u002Fxai-mr.json` with the standard `jq` extractor. `HTTP=200` with a non-empty body → use it (`X_SOURCE=api`).\n4. **Fall back only on a real failure**, and **record the true reason** — never write \"XAI_API_KEY unavailable\" when the key was set. Use one of: `key-unset` (only if step 1 said `KEY_UNSET`), `http-\u003Ccode>` (non-2xx), `empty` (200 but no mentions parsed), `timeout` (curl exceeded `--max-time`).\n\n**WebSearch \u002F WebFetch are last-resort fallbacks only** for X — lower quality (WebSearch favours old high-engagement tweets). They remain the primary tool for the non-X web surfaces (Reddit, HN, blogs, etc.). Never reach for the X WebSearch fallback while the key works.\n\n## Environment Variables\n\n- `XAI_API_KEY` — X.AI API key for Grok's `x_search` tool. Declared in `requires:` (optional `?`), so it is **injected into this skill's environment** and is the primary path for X\u002FTwitter mentions. If it is ever unset, X mentions degrade to the WebSearch fallback at lower quality; the broader-web search is unaffected.\n- `gh` CLI — pre-authenticated in GitHub Actions; used for the GitHub network-signal check (step 3). Not an env var you set here.\n",{"name":5,"metadata":23,"description":7},{"var":24,"tags":25,"title":28,"commits":19,"category":29,"requires":30,"schedule":32},"",[26,27],"social","dev","Mention Radar","productivity",[31],"XAI_API_KEY?","25 7 2\u002F2 * *","main","d272e2d5dc4795e777d85c731669e1978c0d7595","skills\u002Fmention-radar","https:\u002F\u002Fgithub.com\u002FDitto190\u002FAeon-automaton-codeyourself-mm","https:\u002F\u002Fgithub.com\u002FDitto190","2026-11-13 06:13:51",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Ditto190\u002FAeon-automaton-codeyourself-mm --skill mention-radar",{"tool":45,"command":46},"bunx","bunx skills add Ditto190\u002FAeon-automaton-codeyourself-mm --skill mention-radar",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Ditto190\u002FAeon-automaton-codeyourself-mm --skill mention-radar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fmention-radar\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7DCG5X4KFH7AB8485P75B8F","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\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fyou-web-search\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7DCFZSBXYJ5YD2RW2EYYBTR","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\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-tweet\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7DCFWHQ8A71VR7QR9HGWXFP","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\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-aeoncard\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7DCFHZQJMV0VBJY9HPPG74R","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\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-tracker\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7DCF5RBH2H7S5H6Y7PSJRRD","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\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-scanner\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7DCF140AXQARZJ5WNSB8BCA","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\u002FDitto190\u002FAeon-automaton-codeyourself-mm\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-script\u002FSKILL.md",[],[]]