[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CZ8YC25PQXJ0WFD0WBBDM5":3,"skill-same:01M6CZ8YC25PQXJ0WFD0WBBDM5":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":55,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6CZ8YC25PQXJ0WFD0WBBDM5","inbox-triage",null,"Daily GitHub notification inbox triage - surfaces aging vuln PR replies, security advisories, review requests, and mentions that need action","aeonfun\u002Faeon","aeonfun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F287715280?v=4","01M6CZ23C6MXGMF4N0V1DZ1247","aeon","01M6CZ23GMZP1BR424J8Y8K3DG",793,"MIT","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fskills\u002Finbox-triage\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"triage","inbox triage","inbox","review","github","security","pr","dev","Meta","daily","surfaces","aging","replies","requests","action","notification","2026-11-10 10:12:30",false,"---\nname: inbox-triage\ndescription: Daily GitHub notification inbox triage - surfaces aging vuln PR replies, security advisories, review requests, and mentions that need action\nmetadata:\n  title: Inbox Triage\n  category: dev\n  var: \"\"\n  tags:\n    - github\n    - security\n    - meta\n---\n\nToday is ${today}. Read `memory\u002FMEMORY.md` before starting.\n\n## Why this skill exists\n\nHand-tracked follow-ups live in MEMORY.md. `vuln-tracker` tracks the operator's vuln PRs by scanning branch names and ages the `memory\u002Fpending-disclosures\u002F` queue. Neither reads from the actual GitHub notification inbox. When a maintainer replies to a vuln PR — or a security advisory opens on a watched repo — it sits unread until someone manually checks GitHub. This skill reads the inbox and routes what needs action.\n\n`vuln-tracker` covers PR and disclosure lifecycle by branch and draft state. This skill covers the **notification layer** — inbound responses, review requests, security alerts, mentions.\n\n## Steps\n\n### 1. Fetch GitHub notifications\n\nRun:\n```bash\ngh api \u002Fnotifications --paginate 2>&1\n```\n\nParse the JSON array. If the command errors or returns an empty array `[]`, log `INBOX_TRIAGE_SKIP: no notifications` and stop.\n\nLimit to the first 100 notifications if `--paginate` returns more (GitHub caps at 50 per page; two pages is enough).\n\nFor each notification record:\n- `id`\n- `reason` — why you're being notified (mention, review_requested, author, state_change, security_alert, assign, etc.)\n- `subject.title`\n- `subject.type` — PullRequest, Issue, Release, etc.\n- `subject.url` — API URL for the subject\n- `repository.full_name`\n- `updated_at` — ISO timestamp\n\n### 2. Filter\n\nKeep notifications where `unread: true` AND `updated_at` is within the last 14 days. Discard older or read ones.\n\nIf zero remain after filtering: log `INBOX_TRIAGE_SKIP: no actionable notifications within 14 days` and stop.\n\n### 3. Categorize\n\nAssign each notification to exactly one category (first match wins):\n\n| Category | Match criteria |\n|----------|---------------|\n| `SECURITY` | `reason == \"security_alert\"` OR title contains any of: vulnerability, vuln, CVE, advisory, security |\n| `VULN_REPLY` | `subject.type == \"PullRequest\"` AND `reason` is one of: author, state_change, comment AND `repository.full_name` is NOT under the operator's own account\u002Forg (derive the operator's GitHub handle from `soul\u002FSOUL.md` or the workflow's `GITHUB_ACTOR` — these are PRs filed on third-party repos by the vuln-scanner) |\n| `REVIEW_NEEDED` | `reason == \"review_requested\"` |\n| `MENTION` | `reason == \"mention\"` OR `reason == \"team_mention\"` |\n| `GENERAL` | everything else |\n\n### 4. Age vuln PR replies\n\nFor each `VULN_REPLY` notification, compute `age_days` = today minus `updated_at` date (integer days).\n\nFlag urgency:\n- `CRITICAL` — age_days > 7 (maintainer likely hasn't responded)\n- `AGING` — age_days 3–7\n- `FRESH` — age_days \u003C 3\n\nCross-reference with `memory\u002Ftopics\u002Fvuln-followup.md` if it exists: look for the PR title in that file and pull any tracked notes (e.g. \"approved\", \"NEEDS-ANSWER\", merge status).\n\n### 5. Resolve HTML URLs for action items\n\nFor each notification in SECURITY, VULN_REPLY (CRITICAL or AGING), REVIEW_NEEDED, and MENTION categories:\n\nTry to get the HTML URL via:\n```bash\ngh api {subject.url} --jq '.html_url' 2>\u002Fdev\u002Fnull\n```\n\nIf that fails, construct the URL manually:\n`https:\u002F\u002Fgithub.com\u002F{repository.full_name}\u002Fpulls\u002F{number}` for PRs\n`https:\u002F\u002Fgithub.com\u002F{repository.full_name}\u002Fissues\u002F{number}` for issues\n\n(Extract the number from the tail of `subject.url`.)\n\n### 6. Write triage summary\n\nOverwrite `memory\u002Ftopics\u002Finbox-triage.md`:\n\n```markdown\n# GitHub Inbox Triage\n\nLast run: {today}\nScanned: {N} unread notifications ({N} within 14 days)\n\n## Action Required\n\n### Security ({count})\n{for each SECURITY item, sorted by age:}\n- **{repo}**: {title} ({age_days}d) - {html_url}\n\n{if none:}\nNone.\n\n### Vuln PR Replies ({count_critical} critical, {count_aging} aging)\n{for each VULN_REPLY sorted by age desc:}\n- **[{CRITICAL|AGING|FRESH}]** `{repo}` ({age_days}d): {title} - {html_url}\n  {if vuln-followup note found:} _{tracked note}_\n\n{if none:}\nNone.\n\n### Review Requested ({count})\n{for each REVIEW_NEEDED item:}\n- **{repo}**: {title} - {html_url}\n\n{if none:}\nNone.\n\n### Mentions ({count})\n{for each MENTION item:}\n- **{repo}**: {title} - {html_url}\n\n{if none:}\nNone.\n\n## No Action Needed\n{count_general} general notifications (subscriptions, automated state changes).\n```\n\n### 7. Update MEMORY.md known follow-ups\n\nRead `memory\u002FMEMORY.md`. Find the `## Known Follow-ups` section.\n\n**Add** any VULN_REPLY CRITICAL item not already tracked there — append:\n```\n- **{repo} #{number} NEEDS-ANSWER** - {age_days}d since maintainer activity ({url})\n```\n\n**Update** any existing NEEDS-ANSWER item for a PR that now appears as FRESH in VULN_REPLY (maintainer responded recently) — change its note to `RESPONDED — verify resolution`.\n\nDo NOT add GENERAL, REVIEW_NEEDED, MENTION, or SECURITY items to MEMORY.md Known Follow-ups (too noisy; security items warrant a separate issue if severe).\n\n### 8. Send notification\n\nOnly send if at least one of:\n- Any SECURITY item\n- Any VULN_REPLY where urgency == CRITICAL\n- Any REVIEW_NEEDED item\n- Three or more MENTION items\n\nWrite to `.pending-notify-temp\u002Finbox-triage-${today}.md`:\n\n```\ninbox - {today}\n\n{if SECURITY:}\nsecurity alert: {repo} - {title}\n\n{if VULN_REPLY CRITICAL:}\nvuln PRs aging: {comma-separated list of \"repo (Nd)\"}\n\n{if REVIEW_NEEDED:}\nreview needed: {comma-separated repo list}\n\n{if 3+ MENTION:}\n{N} mentions\n\nread it: memory\u002Ftopics\u002Finbox-triage.md\n```\n\nThen:\n```bash\n.\u002Fnotify -f .pending-notify-temp\u002Finbox-triage-${today}.md\n```\n\nIf nothing meets the threshold: skip notification. Log that no notification was sent.\n\n### 9. Log\n\nAppend to `memory\u002Flogs\u002F${today}.md`:\n\n```markdown\n### inbox-triage\n- **Scanned:** {N} notifications\n- **Security:** {N}\n- **Vuln replies:** {N total} ({N_critical} critical, {N_aging} aging, {N_fresh} fresh)\n- **Review needed:** {N}\n- **Mentions:** {N}\n- **MEMORY.md follow-ups updated:** {yes\u002Fno - what changed}\n- **Notification sent:** {yes\u002Fno}\n- INBOX_TRIAGE_OK\n```\n\nIf skipped:\n```markdown\n### inbox-triage\n- INBOX_TRIAGE_SKIP: {reason}\n```\n\n## Required Env Vars\n\nNone beyond `GITHUB_TOKEN`, which GitHub Actions sets automatically and `gh` uses internally.\n\n## Network Note\n\nUses `gh api` for all GitHub calls — it handles auth internally, so no `$SECRET` ever appears on the command line for the Bash permission layer to refuse. `gh api` works in a GitHub Actions run. If `gh api \u002Fnotifications` fails (rate limit, auth error), log the error and exit with `INBOX_TRIAGE_SKIP: api error`. Use WebFetch as a fallback only if `gh` is unavailable — the endpoint is `https:\u002F\u002Fapi.github.com\u002Fnotifications` with `Authorization: Bearer $GITHUB_TOKEN`, but WebFetch can't carry that auth header; prefer `gh`.\n\n## What this is NOT\n\n- Not a replacement for hand-tracked follow-ups in MEMORY.md. This reads the raw GitHub inbox.\n- Not a duplicate of `vuln-tracker` — vuln-tracker tracks lifecycle by branch name. This catches inbound maintainer replies via notifications.\n- Not a duplicate of `vuln-tracker`'s disclosure-queue aging - that manages `memory\u002Fpending-disclosures\u002F` advisory drafts. This reads GitHub security alerts and PR responses.\n","Today is ${today}. Read `memory\u002FMEMORY.md` before starting.\n\n## Why this skill exists\n\nHand-tracked follow-ups live in MEMORY.md. `vuln-tracker` tracks the operator's vuln PRs by scanning branch names and ages the `memory\u002Fpending-disclosures\u002F` queue. Neither reads from the actual GitHub notification inbox. When a maintainer replies to a vuln PR — or a security advisory opens on a watched repo — it sits unread until someone manually checks GitHub. This skill reads the inbox and routes what needs action.\n\n`vuln-tracker` covers PR and disclosure lifecycle by branch and draft state. This skill covers the **notification layer** — inbound responses, review requests, security alerts, mentions.\n\n## Steps\n\n### 1. Fetch GitHub notifications\n\nRun:\n```bash\ngh api \u002Fnotifications --paginate 2>&1\n```\n\nParse the JSON array. If the command errors or returns an empty array `[]`, log `INBOX_TRIAGE_SKIP: no notifications` and stop.\n\nLimit to the first 100 notifications if `--paginate` returns more (GitHub caps at 50 per page; two pages is enough).\n\nFor each notification record:\n- `id`\n- `reason` — why you're being notified (mention, review_requested, author, state_change, security_alert, assign, etc.)\n- `subject.title`\n- `subject.type` — PullRequest, Issue, Release, etc.\n- `subject.url` — API URL for the subject\n- `repository.full_name`\n- `updated_at` — ISO timestamp\n\n### 2. Filter\n\nKeep notifications where `unread: true` AND `updated_at` is within the last 14 days. Discard older or read ones.\n\nIf zero remain after filtering: log `INBOX_TRIAGE_SKIP: no actionable notifications within 14 days` and stop.\n\n### 3. Categorize\n\nAssign each notification to exactly one category (first match wins):\n\n| Category | Match criteria |\n|----------|---------------|\n| `SECURITY` | `reason == \"security_alert\"` OR title contains any of: vulnerability, vuln, CVE, advisory, security |\n| `VULN_REPLY` | `subject.type == \"PullRequest\"` AND `reason` is one of: author, state_change, comment AND `repository.full_name` is NOT under the operator's own account\u002Forg (derive the operator's GitHub handle from `soul\u002FSOUL.md` or the workflow's `GITHUB_ACTOR` — these are PRs filed on third-party repos by the vuln-scanner) |\n| `REVIEW_NEEDED` | `reason == \"review_requested\"` |\n| `MENTION` | `reason == \"mention\"` OR `reason == \"team_mention\"` |\n| `GENERAL` | everything else |\n\n### 4. Age vuln PR replies\n\nFor each `VULN_REPLY` notification, compute `age_days` = today minus `updated_at` date (integer days).\n\nFlag urgency:\n- `CRITICAL` — age_days > 7 (maintainer likely hasn't responded)\n- `AGING` — age_days 3–7\n- `FRESH` — age_days \u003C 3\n\nCross-reference with `memory\u002Ftopics\u002Fvuln-followup.md` if it exists: look for the PR title in that file and pull any tracked notes (e.g. \"approved\", \"NEEDS-ANSWER\", merge status).\n\n### 5. Resolve HTML URLs for action items\n\nFor each notification in SECURITY, VULN_REPLY (CRITICAL or AGING), REVIEW_NEEDED, and MENTION categories:\n\nTry to get the HTML URL via:\n```bash\ngh api {subject.url} --jq '.html_url' 2>\u002Fdev\u002Fnull\n```\n\nIf that fails, construct the URL manually:\n`https:\u002F\u002Fgithub.com\u002F{repository.full_name}\u002Fpulls\u002F{number}` for PRs\n`https:\u002F\u002Fgithub.com\u002F{repository.full_name}\u002Fissues\u002F{number}` for issues\n\n(Extract the number from the tail of `subject.url`.)\n\n### 6. Write triage summary\n\nOverwrite `memory\u002Ftopics\u002Finbox-triage.md`:\n\n```markdown\n# GitHub Inbox Triage\n\nLast run: {today}\nScanned: {N} unread notifications ({N} within 14 days)\n\n## Action Required\n\n### Security ({count})\n{for each SECURITY item, sorted by age:}\n- **{repo}**: {title} ({age_days}d) - {html_url}\n\n{if none:}\nNone.\n\n### Vuln PR Replies ({count_critical} critical, {count_aging} aging)\n{for each VULN_REPLY sorted by age desc:}\n- **[{CRITICAL|AGING|FRESH}]** `{repo}` ({age_days}d): {title} - {html_url}\n  {if vuln-followup note found:} _{tracked note}_\n\n{if none:}\nNone.\n\n### Review Requested ({count})\n{for each REVIEW_NEEDED item:}\n- **{repo}**: {title} - {html_url}\n\n{if none:}\nNone.\n\n### Mentions ({count})\n{for each MENTION item:}\n- **{repo}**: {title} - {html_url}\n\n{if none:}\nNone.\n\n## No Action Needed\n{count_general} general notifications (subscriptions, automated state changes).\n```\n\n### 7. Update MEMORY.md known follow-ups\n\nRead `memory\u002FMEMORY.md`. Find the `## Known Follow-ups` section.\n\n**Add** any VULN_REPLY CRITICAL item not already tracked there — append:\n```\n- **{repo} #{number} NEEDS-ANSWER** - {age_days}d since maintainer activity ({url})\n```\n\n**Update** any existing NEEDS-ANSWER item for a PR that now appears as FRESH in VULN_REPLY (maintainer responded recently) — change its note to `RESPONDED — verify resolution`.\n\nDo NOT add GENERAL, REVIEW_NEEDED, MENTION, or SECURITY items to MEMORY.md Known Follow-ups (too noisy; security items warrant a separate issue if severe).\n\n### 8. Send notification\n\nOnly send if at least one of:\n- Any SECURITY item\n- Any VULN_REPLY where urgency == CRITICAL\n- Any REVIEW_NEEDED item\n- Three or more MENTION items\n\nWrite to `.pending-notify-temp\u002Finbox-triage-${today}.md`:\n\n```\ninbox - {today}\n\n{if SECURITY:}\nsecurity alert: {repo} - {title}\n\n{if VULN_REPLY CRITICAL:}\nvuln PRs aging: {comma-separated list of \"repo (Nd)\"}\n\n{if REVIEW_NEEDED:}\nreview needed: {comma-separated repo list}\n\n{if 3+ MENTION:}\n{N} mentions\n\nread it: memory\u002Ftopics\u002Finbox-triage.md\n```\n\nThen:\n```bash\n.\u002Fnotify -f .pending-notify-temp\u002Finbox-triage-${today}.md\n```\n\nIf nothing meets the threshold: skip notification. Log that no notification was sent.\n\n### 9. Log\n\nAppend to `memory\u002Flogs\u002F${today}.md`:\n\n```markdown\n### inbox-triage\n- **Scanned:** {N} notifications\n- **Security:** {N}\n- **Vuln replies:** {N total} ({N_critical} critical, {N_aging} aging, {N_fresh} fresh)\n- **Review needed:** {N}\n- **Mentions:** {N}\n- **MEMORY.md follow-ups updated:** {yes\u002Fno - what changed}\n- **Notification sent:** {yes\u002Fno}\n- INBOX_TRIAGE_OK\n```\n\nIf skipped:\n```markdown\n### inbox-triage\n- INBOX_TRIAGE_SKIP: {reason}\n```\n\n## Required Env Vars\n\nNone beyond `GITHUB_TOKEN`, which GitHub Actions sets automatically and `gh` uses internally.\n\n## Network Note\n\nUses `gh api` for all GitHub calls — it handles auth internally, so no `$SECRET` ever appears on the command line for the Bash permission layer to refuse. `gh api` works in a GitHub Actions run. If `gh api \u002Fnotifications` fails (rate limit, auth error), log the error and exit with `INBOX_TRIAGE_SKIP: api error`. Use WebFetch as a fallback only if `gh` is unavailable — the endpoint is `https:\u002F\u002Fapi.github.com\u002Fnotifications` with `Authorization: Bearer $GITHUB_TOKEN`, but WebFetch can't carry that auth header; prefer `gh`.\n\n## What this is NOT\n\n- Not a replacement for hand-tracked follow-ups in MEMORY.md. This reads the raw GitHub inbox.\n- Not a duplicate of `vuln-tracker` — vuln-tracker tracks lifecycle by branch name. This catches inbound maintainer replies via notifications.\n- Not a duplicate of `vuln-tracker`'s disclosure-queue aging - that manages `memory\u002Fpending-disclosures\u002F` advisory drafts. This reads GitHub security alerts and PR responses.\n",{"name":5,"metadata":45,"description":7},{"var":46,"tags":47,"title":49,"category":31},"",[28,29,48],"meta","Inbox Triage","main","504a21d53c0c9b485f6e90c43db83000825e1d3c","skills\u002Finbox-triage",308,"https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon","https:\u002F\u002Fwww.aeon.fun\u002F","https:\u002F\u002Fgithub.com\u002Faeonfun","The most autonomous agent framework.","2026-11-15 03:40:18",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add aeonfun\u002Faeon --skill inbox-triage",{"tool":65,"command":66},"bunx","bunx skills add aeonfun\u002Faeon --skill inbox-triage",{"tool":68,"command":69},"pnpm","pnpm dlx skills add aeonfun\u002Faeon --skill inbox-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fskills\u002Finbox-triage\u002FSKILL.md",true,[],[74,81,87,93,99,105],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M7DSM3QWBJ44FKRMDDRAGNET","Warn Mixed Script","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Fskill-scan-fixtures\u002Fwarn-mixed-script\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":82,"name":83,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":80},"01M7DSM0496DRYYW5A4NAAHZDX","Warn Hidden CSS","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Fskill-scan-fixtures\u002Fwarn-hidden-css\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":80},"01M7DSKWCGDVYZSDJM31YHS2JB","Malicious Injection Uppercase","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Fskill-scan-fixtures\u002Fmalicious-injection-uppercase\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":80},"01M7DSKRV2RRA1V0HK13KYWJXD","Malicious Injection Homoglyph","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Fskill-scan-fixtures\u002Fmalicious-injection-homoglyph\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":80},"01M7DSKMXJKY0167YHVCKF7B49","Malicious Injection Disregard Prior","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Fskill-scan-fixtures\u002Fmalicious-injection-disregard-prior\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":80},"01M7DSKGFQ5V2VNSA4K97CVFMB","Benign Greek Math","https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Fskill-scan-fixtures\u002Fbenign-greek-math\u002FSKILL.md",[],[]]