[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75F6T1KAX4SHN9MF8W0HASE":3,"skill-same:01M75F6T1KAX4SHN9MF8W0HASE":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75F6T1KAX4SHN9MF8W0HASE","matter-update",null,"Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fmatter-update\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matter-update\ndescription: Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.\nargument-hint: \"[slug] [brief event description]\"\n---\n\n# \u002Fmatter-update\n\n1. Follow the workflow and reference below.\n2. Confirm slug exists in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F` and `_log.yaml`.\n3. Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).\n4. Append dated entry to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`.\n5. Update `_log.yaml` — set `last_updated` to today, apply any field updates.\n6. Confirm.\n\n---\n\n# Matter Update\n\n## Purpose\n\nThe portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — find the row\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md` — append target\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fmatter.md` — reference (don't rewrite)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` — risk calibration (if re-assessing risk)\n\n**Conflicts gate — unbypassable.** Before logging an update, check `_log.yaml` for the matter slug. If the matter is not in `_log.yaml`, refuse and route:\n\n> \"I don't see [matter slug] in the matter log. Run `\u002Flitigation-legal:matter-intake` first so the conflicts check runs and the matter workspace exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's no `history.md` to append to until the matter is intaken.\"\n\n## Input\n\nSlug (required). If not provided, ask — with a short list of recently updated matters to pick from.\n\n## The update\n\n### 1. Event type\n\nOffer categories:\n\n- **Procedural** — motion filed\u002Freceived, order issued, hearing held, deadline set\n- **Discovery** — production made\u002Freceived, depositions taken, subpoena served\n- **Substantive** — new facts, key document surfaced, ruling on merits\n- **Strategy** — posture shift, settlement offer made\u002Freceived, authority update\n- **Risk re-assessment** — severity or likelihood changed\n- **Stakeholder** — new person looped in, outside counsel change\n- **Administrative** — engagement letter executed, budget adjusted, hold refreshed\n\nOr freeform if none fits.\n\n### 2. Date\n\nDefault today. Accept an override (e.g., capturing an event from last week).\n\n### 3. Summary\n\nOne-paragraph narrative. What happened, what it means, any immediate implication.\n\n### 4. Log field changes\n\nWalk through potentially affected fields:\n\n- `status:` — has the stage shifted (e.g., pleadings → fact discovery)?\n- `stage:` — substage update\n- `risk:` — reassessment required?\n- `materiality:` — any change (new facts might trigger reserve or disclosure)?\n- `exposure_range:` — revise if new information\n- `next_deadline:` — new upcoming date, if any\n- `outside_counsel:` — change?\n- `internal_owners:` — anyone new or removed?\n- `legal_hold:` — refreshed, expanded, released?\n\nOnly prompt for fields likely affected by the event type. Procedural updates usually touch `stage` and `next_deadline` only; a settlement offer might touch `materiality`, `exposure_range`, `status`.\n\n### 4pre. Settlement-acceptance gate\n\nIf the Strategy update is a **settlement acceptance** (the company is accepting a settlement offer, executing a settlement agreement, or authorizing acceptance in principle — not merely logging an offer made or received): Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`. If the Role is Non-lawyer:\n\n> Accepting a settlement has legal consequences — it resolves claims, typically requires a release, and can affect insurance, tax, and related matters. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:\n>\n> [Generate a 1-page summary: the matter, proposed settlement terms (dollar, structural, release scope, confidentiality, non-disparagement), exposure at stake, authority ladder status (see `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` settlement authority), what could go wrong, what to ask the attorney before accepting.]\n>\n> If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA\u002FBar Standards Board in England & Wales, Law Society in Scotland\u002FNI\u002FIreland\u002FCanada\u002FAustralia, or your jurisdiction's equivalent).\n\nDo not log the acceptance or flip materiality on acceptance basis without an explicit yes. Logging offers or counters does not require the gate — acceptance does.\n\n### 4a. Materiality trigger — explicit prompt\n\nCertain event types force a materiality re-check. When the event type is in this list, **always prompt** — don't let the user move on without an explicit answer:\n\n| Event type | Materiality trigger prompt |\n|---|---|\n| Substantive (new facts, key document, merits ruling) | \"This event is substantive. Does it push `materiality`? Current: `[current]`. Options: `reserved \u002F disclosed \u002F monitored \u002F none`. Change?\" |\n| Strategy (posture shift, settlement offer made or received) | \"Settlement activity often triggers materiality reclassification. Current: `[current]`. If the offer, counter, or acceptance moves exposure or shifts from contested to probable-and-estimable, reclassify.\" |\n| Risk re-assessment (severity or likelihood changed) | \"Risk moved. Materiality should track. Current: `[current]`. Reclassify?\" |\n| Regulatory \u002F enforcement development | \"Regulator action (subpoena, CID, enforcement notice) usually triggers disclosure analysis. Current: `[current]`. Change?\" |\n\nAcceptable answers include `no change` — but `no change` must be explicit, not implied by silence. Capture in the history entry:\n\n```markdown\n**Materiality check:** [no change \u002F changed from X to Y]\n**Reasoning:** [one sentence]\n```\n\nIf materiality moves to `reserved` or `disclosed`, and the matter did not previously carry a reserve or disclosure, flag the event as requiring finance \u002F audit-committee notification per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` materiality thresholds.\n\n### 5. Seed doc prompt (optional)\n\nIf the update references a document (order, filing, correspondence), ask if there's a path to link. Not pushy.\n\n## Writing\n\n### Append to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`\n\nMost recent at top, directly under the `---` that follows the header.\n\n```markdown\n## [YYYY-MM-DD] — [Event type]: [short title]\n\n[Paragraph summary.]\n\n**Fields changed:**\n- [field]: [old → new]\n- [field]: [old → new]\n\n**Related doc:** [path, if provided]\n```\n\nIf no fields changed, omit the \"Fields changed\" block.\n\n### Update `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml`\n\n- Apply any field changes.\n- Set `last_updated: [today]` (or the event date if the user overrode — the log tracks when the record was last touched).\n\n## Confirm\n\nShow the user the history entry and the yaml diff before writing:\n\n> Here's what I'll append and update. Good to commit?\n\n## What this skill does not do\n\n- Edit past history entries. Corrections are new entries that reference and correct prior ones.\n- Silently change the log. Every field change is shown to the user before write.\n- Decide whether a new development warrants reserve\u002Fdisclosure. It surfaces the question (\"this might push materiality — want to reclassify?\"), the user answers.\n","# \u002Fmatter-update\n\n1. Follow the workflow and reference below.\n2. Confirm slug exists in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F` and `_log.yaml`.\n3. Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).\n4. Append dated entry to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`.\n5. Update `_log.yaml` — set `last_updated` to today, apply any field updates.\n6. Confirm.\n\n---\n\n# Matter Update\n\n## Purpose\n\nThe portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — find the row\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md` — append target\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fmatter.md` — reference (don't rewrite)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` — risk calibration (if re-assessing risk)\n\n**Conflicts gate — unbypassable.** Before logging an update, check `_log.yaml` for the matter slug. If the matter is not in `_log.yaml`, refuse and route:\n\n> \"I don't see [matter slug] in the matter log. Run `\u002Flitigation-legal:matter-intake` first so the conflicts check runs and the matter workspace exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's no `history.md` to append to until the matter is intaken.\"\n\n## Input\n\nSlug (required). If not provided, ask — with a short list of recently updated matters to pick from.\n\n## The update\n\n### 1. Event type\n\nOffer categories:\n\n- **Procedural** — motion filed\u002Freceived, order issued, hearing held, deadline set\n- **Discovery** — production made\u002Freceived, depositions taken, subpoena served\n- **Substantive** — new facts, key document surfaced, ruling on merits\n- **Strategy** — posture shift, settlement offer made\u002Freceived, authority update\n- **Risk re-assessment** — severity or likelihood changed\n- **Stakeholder** — new person looped in, outside counsel change\n- **Administrative** — engagement letter executed, budget adjusted, hold refreshed\n\nOr freeform if none fits.\n\n### 2. Date\n\nDefault today. Accept an override (e.g., capturing an event from last week).\n\n### 3. Summary\n\nOne-paragraph narrative. What happened, what it means, any immediate implication.\n\n### 4. Log field changes\n\nWalk through potentially affected fields:\n\n- `status:` — has the stage shifted (e.g., pleadings → fact discovery)?\n- `stage:` — substage update\n- `risk:` — reassessment required?\n- `materiality:` — any change (new facts might trigger reserve or disclosure)?\n- `exposure_range:` — revise if new information\n- `next_deadline:` — new upcoming date, if any\n- `outside_counsel:` — change?\n- `internal_owners:` — anyone new or removed?\n- `legal_hold:` — refreshed, expanded, released?\n\nOnly prompt for fields likely affected by the event type. Procedural updates usually touch `stage` and `next_deadline` only; a settlement offer might touch `materiality`, `exposure_range`, `status`.\n\n### 4pre. Settlement-acceptance gate\n\nIf the Strategy update is a **settlement acceptance** (the company is accepting a settlement offer, executing a settlement agreement, or authorizing acceptance in principle — not merely logging an offer made or received): Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`. If the Role is Non-lawyer:\n\n> Accepting a settlement has legal consequences — it resolves claims, typically requires a release, and can affect insurance, tax, and related matters. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:\n>\n> [Generate a 1-page summary: the matter, proposed settlement terms (dollar, structural, release scope, confidentiality, non-disparagement), exposure at stake, authority ladder status (see `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` settlement authority), what could go wrong, what to ask the attorney before accepting.]\n>\n> If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA\u002FBar Standards Board in England & Wales, Law Society in Scotland\u002FNI\u002FIreland\u002FCanada\u002FAustralia, or your jurisdiction's equivalent).\n\nDo not log the acceptance or flip materiality on acceptance basis without an explicit yes. Logging offers or counters does not require the gate — acceptance does.\n\n### 4a. Materiality trigger — explicit prompt\n\nCertain event types force a materiality re-check. When the event type is in this list, **always prompt** — don't let the user move on without an explicit answer:\n\n| Event type | Materiality trigger prompt |\n|---|---|\n| Substantive (new facts, key document, merits ruling) | \"This event is substantive. Does it push `materiality`? Current: `[current]`. Options: `reserved \u002F disclosed \u002F monitored \u002F none`. Change?\" |\n| Strategy (posture shift, settlement offer made or received) | \"Settlement activity often triggers materiality reclassification. Current: `[current]`. If the offer, counter, or acceptance moves exposure or shifts from contested to probable-and-estimable, reclassify.\" |\n| Risk re-assessment (severity or likelihood changed) | \"Risk moved. Materiality should track. Current: `[current]`. Reclassify?\" |\n| Regulatory \u002F enforcement development | \"Regulator action (subpoena, CID, enforcement notice) usually triggers disclosure analysis. Current: `[current]`. Change?\" |\n\nAcceptable answers include `no change` — but `no change` must be explicit, not implied by silence. Capture in the history entry:\n\n```markdown\n**Materiality check:** [no change \u002F changed from X to Y]\n**Reasoning:** [one sentence]\n```\n\nIf materiality moves to `reserved` or `disclosed`, and the matter did not previously carry a reserve or disclosure, flag the event as requiring finance \u002F audit-committee notification per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` materiality thresholds.\n\n### 5. Seed doc prompt (optional)\n\nIf the update references a document (order, filing, correspondence), ask if there's a path to link. Not pushy.\n\n## Writing\n\n### Append to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`\n\nMost recent at top, directly under the `---` that follows the header.\n\n```markdown\n## [YYYY-MM-DD] — [Event type]: [short title]\n\n[Paragraph summary.]\n\n**Fields changed:**\n- [field]: [old → new]\n- [field]: [old → new]\n\n**Related doc:** [path, if provided]\n```\n\nIf no fields changed, omit the \"Fields changed\" block.\n\n### Update `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml`\n\n- Apply any field changes.\n- Set `last_updated: [today]` (or the event date if the user overrode — the log tracks when the record was last touched).\n\n## Confirm\n\nShow the user the history entry and the yaml diff before writing:\n\n> Here's what I'll append and update. Good to commit?\n\n## What this skill does not do\n\n- Edit past history entries. Corrections are new entries that reference and correct prior ones.\n- Silently change the log. Every field change is shown to the user before write.\n- Decide whether a new development warrants reserve\u002Fdisclosure. It surfaces the question (\"this might push materiality — want to reclassify?\"), the user answers.\n",{"name":5,"description":7,"argument-hint":23},"[slug] [brief event description]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fmatter-update",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill matter-update",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill matter-update",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill matter-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fmatter-update\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]