[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E7DHNMS3RYVG9DMZ8QWX6Y":3,"skill-same:01M7E7DHNMS3RYVG9DMZ8QWX6Y":77},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7E7DHNMS3RYVG9DMZ8QWX6Y","draft-brief",null,"Drafts court filings — motions, memoranda of law, appellate briefs — as court-ready .docx, with Midpage research behind every citation. Use to \"draft a motion to dismiss,\" \"write the brief.\"","wxdwu\u002Fnew-api","wxdwu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80968397?v=4","01M7E6AEMB59N90BKXD77EC83D","Xudong Wu","01M7E6AEMY2BXCDVZ9MJJHFQ4C",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: draft-brief\ndescription: \"Drafts court filings — motions, memoranda of law, appellate briefs — as court-ready .docx, with Midpage research behind every citation. Use to \\\"draft a motion to dismiss,\\\" \\\"write the brief.\\\"\"\nmetadata:\n  version: 0.2.0\n  author: midpage\n---\n\n# Draft Brief\n\nDraft and format a court-ready filing and hand back the `.docx`. Briefs, motions, memoranda of\nlaw, oppositions, replies, appellate briefs. **Complaints and other pleadings are out of\nscope** — if asked to draft one, say so and stop. Read the shared guides first — they carry\nthe method this skill assumes: `references\u002Flitigation-writing.md` (how to write it),\n`references\u002Fcourt-rules.md` (how to find the governing rules), `references\u002Fcitations.md` (how\nevery cite links), and `references\u002Flegal-docx.md` (rendering). The research method is below —\nit is the heart of this skill.\n\n## Workflow\n\n1. **Get up to speed.** Read any relevant uploads and consult the relevant record documents\n   (`analyzeDocketReport` for posture and the operative filings, `analyzeDocketFiling` to read\n   what they actually say). Every record fact you later assert carries a linked filing cite.\n2. **Preliminary research.** Don't jump to conclusions about what to argue; research with\n   Midpage to determine what the strongest arguments are and what makes procedural sense.\n3. **Craft the research-based narrative structure.** Consult\n   `references\u002Flitigation-writing.md`. Before doing even more research, settle on structure\n   and arguments based on your preliminary research.\n4. **MOST IMPORTANT: Exhaustive, iterative research per issue.** Make a research plan and\n   follow it, using the method below. The goal is not to surface and analyze the obvious\n   opinions only; you want to find the strongest, most favorable cases that will carry each\n   argument the extra mile. Don't settle for any case supporting your proposition — find the\n   favorable ones with devastating language, framings, facts, and the right outcomes. Each\n   argument needs to be dense with case-law citations and compelling analysis. Find the cases\n   and arguments that HURT and confront them head on — distinguish them or argue they are not\n   determinative.\n5. **Get the governing rules** per `references\u002Fcourt-rules.md`: case orders → judge's\n   individual practices → local\u002FECF rules → federal baseline. Capture length limits,\n   font\u002Fmargins\u002Fspacing, required sections, caption form, certificates, TOC\u002FTOA triggers —\n   each linked to its source. Surface conflicts (the more specific layer controls; show both).\n6. **Write it** per `references\u002Flitigation-writing.md`: theme stated up front, point headings\n   that argue, rule synthesis not book reports, quotes woven into prose, adverse authority\n   confronted head-on.\n7. **Render** with the `brief` profile (`references\u002Flegal-docx.md`). Thread any rule-set\n   spacing\u002Ffont\u002Fmargin through `D.builders(\"brief\", { lineSpacing })`; defaults stand when\n   rules are silent. Validate the rendered file against the verifiable requirements (length,\n   font, margins, spacing, required sections, certificates).\n\n## Research with Midpage (the method)\n\nAll law comes from the Midpage tools this session. `search` finds candidates; `findInOpinion`\npreviews; **`analyzeOpinion` is what permits a citation** — no case is cited without it.\n\n- **Frame before you search.** Pin the forum (court, circuit, state) — it controls what binds\n  and how to filter. Reduce each question to the operative element actually in dispute (\"does\n  an eight-month delay defeat likely irreparable harm in the Ninth Circuit?\" — not \"can we get\n  an injunction?\"). Each distinct issue gets its own searches and its own section. For every\n  issue, write down what the other side will argue — that defines half your research targets.\n- **Search semantic, parallel, filtered.** Concept- and proposition-style queries, never\n  boolean. One issue per query, up to four in parallel. Filter to the forum\n  (`jurisdictionType`, `circuits`\u002F`courts`\u002F`states`, dates when recency matters); binding\n  authority first, persuasive labeled as such. If you filter `publishStatus`, run a parallel\n  `unknown` query too (for California, default to `published` plus `unknown`). Need exact\n  wording? Stop guessing in `search` — run `findInOpinion` on a promising case.\n- **Triage before you spend analysis.** `highlights` show why a case matched — previews only,\n  never quote them. `treatment` gauges whether it's good law and how heavily relied on.\n  `findInOpinion` is the free double-click before an `analyzeOpinion` call.\n- **Branch from the best case.** When a strong case surfaces, mine it: `analyzeOpinion` it and\n  pull the authorities the opinion itself leans on (the rule it states usually quotes the case\n  you actually want); then search its key holding language as its own query to find later\n  cases applying it. A case the court's own opinions repeatedly cite is worth more than three\n  you found cold.\n- **Iterate until it's scorched earth.** Re-query each issue with new framings — the best\n  case's holding language, the opposing side's framing, narrower fact patterns, the remedy\n  angle — until new queries keep returning the same leading cases. That saturation is the\n  signal you've mapped the field; anything less is settling.\n- **The `analyzeOpinion` gate, on every case you cite.** Pass a `question` naming the exact\n  element. Check **`doesNotAddress` first** — if your point is listed, the case does not stand\n  for it, however close the language looks. Build sentences from `supportedPropositions`\n  (each carries a cite-ready proposition, a verified quote, and a `deeplinkURL`). Lead with\n  `core_holding` over `supporting_analysis`; never sell `background` as the holding. Carry\n  `scope` qualifiers into your sentence. A concurrence or dissent (`opinionSection`) is never\n  presented as the court's holding. Surface negative `treatment` honestly — if you must use a\n  caution\u002Fnegative case, say so.\n- **Research the other side as hard as your own.** For every issue, run searches framed from\n  the opposing position; identify the case they will lead with and `analyzeOpinion` it too —\n  that's what step 4's confrontation is built from.\n- **Silence and splits are findings.** No controlling authority on point, or a genuine split,\n  gets reported as such — never papered over with an off-point or out-of-jurisdiction cite.\n\n## Scope discipline\n\n- **Format, required sections, and limits are always in scope.** When a rule forces a change,\n  name the rule and link the source.\n- **Drafting substance** (argument, facts) is in scope when drafting from scratch or when\n  asked.\n- **Working from the user's existing draft: do not rewrite their arguments, reorder their\n  theories, or change their voice** unless they ask or a rule requires it (get sign-off before\n  cutting argument to meet a limit). Note substantive problems you spot as a brief, separate\n  observation — never silently implement them.\n\n## Hard rules\n\n- Never recall a rule, holding, quote, or record fact from memory. Rules come from sources\n  retrieved this session; case law from `analyzeOpinion`; record facts from\n  `analyzeDocketFiling`. No invented case, quote, pin cite, statute, or rule, ever.\n- Honor `doesNotAddress`, distinguish holdings from dicta and majority from\n  concurrence\u002Fdissent, surface negative treatment.\n- The attorney owns the filing. Flag open items and judgment calls plainly; never imply the\n  document is filing-ready without their review.\n- Brief-writing is research-led. Do thorough, iterative research with Midpage.\n","# Draft Brief\n\nDraft and format a court-ready filing and hand back the `.docx`. Briefs, motions, memoranda of\nlaw, oppositions, replies, appellate briefs. **Complaints and other pleadings are out of\nscope** — if asked to draft one, say so and stop. Read the shared guides first — they carry\nthe method this skill assumes: `references\u002Flitigation-writing.md` (how to write it),\n`references\u002Fcourt-rules.md` (how to find the governing rules), `references\u002Fcitations.md` (how\nevery cite links), and `references\u002Flegal-docx.md` (rendering). The research method is below —\nit is the heart of this skill.\n\n## Workflow\n\n1. **Get up to speed.** Read any relevant uploads and consult the relevant record documents\n   (`analyzeDocketReport` for posture and the operative filings, `analyzeDocketFiling` to read\n   what they actually say). Every record fact you later assert carries a linked filing cite.\n2. **Preliminary research.** Don't jump to conclusions about what to argue; research with\n   Midpage to determine what the strongest arguments are and what makes procedural sense.\n3. **Craft the research-based narrative structure.** Consult\n   `references\u002Flitigation-writing.md`. Before doing even more research, settle on structure\n   and arguments based on your preliminary research.\n4. **MOST IMPORTANT: Exhaustive, iterative research per issue.** Make a research plan and\n   follow it, using the method below. The goal is not to surface and analyze the obvious\n   opinions only; you want to find the strongest, most favorable cases that will carry each\n   argument the extra mile. Don't settle for any case supporting your proposition — find the\n   favorable ones with devastating language, framings, facts, and the right outcomes. Each\n   argument needs to be dense with case-law citations and compelling analysis. Find the cases\n   and arguments that HURT and confront them head on — distinguish them or argue they are not\n   determinative.\n5. **Get the governing rules** per `references\u002Fcourt-rules.md`: case orders → judge's\n   individual practices → local\u002FECF rules → federal baseline. Capture length limits,\n   font\u002Fmargins\u002Fspacing, required sections, caption form, certificates, TOC\u002FTOA triggers —\n   each linked to its source. Surface conflicts (the more specific layer controls; show both).\n6. **Write it** per `references\u002Flitigation-writing.md`: theme stated up front, point headings\n   that argue, rule synthesis not book reports, quotes woven into prose, adverse authority\n   confronted head-on.\n7. **Render** with the `brief` profile (`references\u002Flegal-docx.md`). Thread any rule-set\n   spacing\u002Ffont\u002Fmargin through `D.builders(\"brief\", { lineSpacing })`; defaults stand when\n   rules are silent. Validate the rendered file against the verifiable requirements (length,\n   font, margins, spacing, required sections, certificates).\n\n## Research with Midpage (the method)\n\nAll law comes from the Midpage tools this session. `search` finds candidates; `findInOpinion`\npreviews; **`analyzeOpinion` is what permits a citation** — no case is cited without it.\n\n- **Frame before you search.** Pin the forum (court, circuit, state) — it controls what binds\n  and how to filter. Reduce each question to the operative element actually in dispute (\"does\n  an eight-month delay defeat likely irreparable harm in the Ninth Circuit?\" — not \"can we get\n  an injunction?\"). Each distinct issue gets its own searches and its own section. For every\n  issue, write down what the other side will argue — that defines half your research targets.\n- **Search semantic, parallel, filtered.** Concept- and proposition-style queries, never\n  boolean. One issue per query, up to four in parallel. Filter to the forum\n  (`jurisdictionType`, `circuits`\u002F`courts`\u002F`states`, dates when recency matters); binding\n  authority first, persuasive labeled as such. If you filter `publishStatus`, run a parallel\n  `unknown` query too (for California, default to `published` plus `unknown`). Need exact\n  wording? Stop guessing in `search` — run `findInOpinion` on a promising case.\n- **Triage before you spend analysis.** `highlights` show why a case matched — previews only,\n  never quote them. `treatment` gauges whether it's good law and how heavily relied on.\n  `findInOpinion` is the free double-click before an `analyzeOpinion` call.\n- **Branch from the best case.** When a strong case surfaces, mine it: `analyzeOpinion` it and\n  pull the authorities the opinion itself leans on (the rule it states usually quotes the case\n  you actually want); then search its key holding language as its own query to find later\n  cases applying it. A case the court's own opinions repeatedly cite is worth more than three\n  you found cold.\n- **Iterate until it's scorched earth.** Re-query each issue with new framings — the best\n  case's holding language, the opposing side's framing, narrower fact patterns, the remedy\n  angle — until new queries keep returning the same leading cases. That saturation is the\n  signal you've mapped the field; anything less is settling.\n- **The `analyzeOpinion` gate, on every case you cite.** Pass a `question` naming the exact\n  element. Check **`doesNotAddress` first** — if your point is listed, the case does not stand\n  for it, however close the language looks. Build sentences from `supportedPropositions`\n  (each carries a cite-ready proposition, a verified quote, and a `deeplinkURL`). Lead with\n  `core_holding` over `supporting_analysis`; never sell `background` as the holding. Carry\n  `scope` qualifiers into your sentence. A concurrence or dissent (`opinionSection`) is never\n  presented as the court's holding. Surface negative `treatment` honestly — if you must use a\n  caution\u002Fnegative case, say so.\n- **Research the other side as hard as your own.** For every issue, run searches framed from\n  the opposing position; identify the case they will lead with and `analyzeOpinion` it too —\n  that's what step 4's confrontation is built from.\n- **Silence and splits are findings.** No controlling authority on point, or a genuine split,\n  gets reported as such — never papered over with an off-point or out-of-jurisdiction cite.\n\n## Scope discipline\n\n- **Format, required sections, and limits are always in scope.** When a rule forces a change,\n  name the rule and link the source.\n- **Drafting substance** (argument, facts) is in scope when drafting from scratch or when\n  asked.\n- **Working from the user's existing draft: do not rewrite their arguments, reorder their\n  theories, or change their voice** unless they ask or a rule requires it (get sign-off before\n  cutting argument to meet a limit). Note substantive problems you spot as a brief, separate\n  observation — never silently implement them.\n\n## Hard rules\n\n- Never recall a rule, holding, quote, or record fact from memory. Rules come from sources\n  retrieved this session; case law from `analyzeOpinion`; record facts from\n  `analyzeDocketFiling`. No invented case, quote, pin cite, statute, or rule, ever.\n- Honor `doesNotAddress`, distinguish holdings from dicta and majority from\n  concurrence\u002Fdissent, surface negative treatment.\n- The attorney owns the filing. Flag open items and judgment calls plainly; never imply the\n  document is filing-ready without their review.\n- Brief-writing is research-led. Do thorough, iterative research with Midpage.\n",{"name":5,"metadata":24,"description":7},{"author":25,"version":26},"midpage","0.2.0","main","dde9a06ab10bce3fe52058c783826590231f7df3","plugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api","https:\u002F\u002Fgithub.com\u002Fwxdwu","24120128@bjtu.edu.cn","I am Xudong Wu，a student in beijing jiaotong University, \"I am eager to learn on GitHub and contribute my part to this community.","2026-10-05 17:26:50",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add wxdwu\u002Fnew-api --skill draft-brief",{"tool":41,"command":42},"bunx","bunx skills add wxdwu\u002Fnew-api --skill draft-brief",{"tool":44,"command":45},"pnpm","pnpm dlx skills add wxdwu\u002Fnew-api --skill draft-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002FSKILL.md",true,[49,55,59,63,67,71],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",215,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcitations.md",2461,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002Freferences\u002Fcitations.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcourt-rules.md",5306,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002Freferences\u002Fcourt-rules.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Flegal-docx.md",6652,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002Freferences\u002Flegal-docx.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Flitigation-writing.md",9870,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002Freferences\u002Flitigation-writing.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Flegal_docx.js","SCRIPT","脚本",29188,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fmidpage\u002Fskills\u002Fdraft-brief\u002Fscripts\u002Flegal_docx.js",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7E8SVA2N0JA09RW1XJYXCWX","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzotero\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7E8ST1FJAD5PWTW2FN1NSK0","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"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":19},"01M7E8SRW074NNNCZRCZA5T3Z1","setup-zoom-websockets","Use when building Zoom WebSockets.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7E8SPCFMD3YVPRX2MW8X3RA","setup-zoom-webhooks","Use when building Zoom webhooks.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7E8SMCH4RPCX8YSBNGWQCMP","zoom-virtual-agent-web","Zoom Virtual Agent SDK for web embeds. Use for campaign or entry ID chat launch, event-driven controls, user context updates, and CSP-safe deployment.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fweb\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7E8SJCAY323E36Z8SAP8H4M","zoom-virtual-agent-ios","Zoom Virtual Agent iOS integration via WKWebView. Use for Swift\u002FObjective-C script injection, message handlers, support_handoff relay, and URL routing policies.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fios\u002FSKILL.md",[],[]]