[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDY5WA2PAYX5AMFJTYBR6P":3,"skill-same:01M7FDY5WA2PAYX5AMFJTYBR6P":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FDY5WA2PAYX5AMFJTYBR6P","patent-review",null,"Get an external patent examiner review of a patent application. Use when user says \"专利审查\", \"patent review\", \"审查意见\", \"examiner review\", or wants critical feedback on patent claims and specification.","CZX-LBJ\u002Fdeepseek-science","CZX-LBJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F204594689?v=4","01M7FC59WQ9PFXT04MKGJDCFFT","czx","01M7FC59XB2GW0BKWN9JTDBQS7",1,"MIT","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fpatent-review\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: patent-review\ndescription: \"Get an external patent examiner review of a patent application. Use when user says \\\"专利审查\\\", \\\"patent review\\\", \\\"审查意见\\\", \\\"examiner review\\\", or wants critical feedback on patent claims and specification.\"\nargument-hint: \"[patent-directory-or-scope]\"\nallowed-tools: Bash(*), Read, Grep, Glob, Write, Edit\n---\n\n# Patent Examiner Review via Codex MCP (xhigh reasoning)\n\nGet a multi-round patent examiner review of the patent application based on: **$ARGUMENTS**\n\nAdapted from `\u002Fresearch-review`. The reviewer persona is a patent examiner, not a paper reviewer.\n\n## Constants\n\n- `REVIEWER_MODEL = gpt-6-astra` — Model used via Codex MCP\n- `REVIEW_ROUNDS = 2` — Number of review rounds\n- `EXAMINER_PERSONA = \"patent-examiner\"` — GPT-6-Astra persona\n\n## Prerequisites\n\n- Codex MCP Server configured:\n  ```bash\n  claude mcp add codex -s user -- python3 \"$HOME\u002Faris_repo\u002Fmcp-servers\u002Fcodex-exec\u002Fserver.py\"   # your ARIS clone's path\n  ```\n\n## Inputs\n\n1. `patent\u002FCLAIMS.md` — all drafted claims\n2. `patent\u002Fspecification\u002F` — all specification sections\n3. `patent\u002Ffigures\u002Fnumeral_index.md` — reference numeral mapping\n4. `patent\u002FPRIOR_ART_REPORT.md` — known prior art\n5. `patent\u002FINVENTION_DISCLOSURE.md` — invention structure\n\n## Workflow\n\n### Step 1: Gather Patent Context\n\nBefore calling the external reviewer, compile a comprehensive briefing:\n1. Read all claims (independent + dependent)\n2. Read specification sections (at least summary and detailed description)\n3. Read prior art report for context\n4. Identify: core inventive concept, claim scope, known prior art, target jurisdiction\n\n### Step 2: Round 1 — Full Examiner Review\n\nSend to `REVIEWER_MODEL` via `spawn_agent` with xhigh reasoning:\n\n```text\nspawn_agent:\n  model: gpt-6-astra\n  reasoning_effort: xhigh\n  message: |\n    You are a senior patent examiner at the [USPTO\u002FCNIPA\u002FEPO].\n    Examine this patent application and issue a detailed office action.\n\n    CLAIMS:\n    [all claims]\n\n    SPECIFICATION SUMMARY:\n    [key sections: title, technical field, background, summary, abstract]\n\n    PRIOR ART KNOWN:\n    [prior art references]\n\n    PATENTABILITY STANDARDS TO APPLY:\n    [US: 35 USC 101\u002F102\u002F103\u002F112 | CN: Articles 22, 26 | EP: Articles 54, 56, 83, 84]\n\n    Please issue an office action covering:\n\n    1. CLAIM CLARITY (112(b)\u002FArt 84):\n       - Are all terms definite?\n       - Any indefinite functional language?\n       - Antecedent basis issues?\n\n    2. WRITTEN DESCRIPTION (112(a)\u002FArt 83 first para):\n       - Does the spec support ALL claim scope?\n       - Any claim elements without spec support?\n\n    3. ENABLEMENT (112(a)\u002FArt 83):\n       - Can a POSITA practice the invention?\n       - Any missing algorithm\u002Fstructure for functional claims?\n\n    4. NOVELTY (102\u002FArt 54):\n       - Would any known reference anticipate any claim?\n       - Identify the closest single reference.\n\n    5. NON-OBVIOUSNESS (103\u002FArt 56):\n       - Would any combination render claims obvious?\n       - What is the motivation to combine?\n\n    6. CLAIM SCOPE:\n       - Are independent claims broad enough to be commercially valuable?\n       - Do dependent claims provide meaningful fallback positions?\n       - Any claims that are too broad (likely rejected) or too narrow (not valuable)?\n\n    7. SPECIFICATION QUALITY:\n       - Language issues (subjective terms, relative terms, result-to-be-achieved)\n       - Reference numeral consistency\n       - Missing embodiments\n\n    Format your response as a formal office action with:\n    - GROUNDS OF REJECTION for each issue (cite statute)\n    - SUGGESTED AMENDMENTS for each issue\n    - OVERALL PATENTABILITY SCORE: 1-10\n\n    Be rigorous and specific. This is a real examination.\n```\n\n### Step 3: Implement Fixes (Round 1)\n\nBased on the examiner's office action:\n\n1. **CRITICAL issues** (102 rejection, 112 indefiniteness, missing enablement):\n   - Must be fixed before proceeding\n   - Amend claims or add specification support\n\n2. **MAJOR issues** (103 obviousness, weak claim scope, missing support):\n   - Should be fixed or argued\n   - Consider claim amendments or specification additions\n\n3. **MINOR issues** (language quality, numeral consistency, formatting):\n   - Fix if time permits\n   - Document in output for later cleanup\n\nFor each fix:\n- Show the specific change (old claim -> new claim)\n- Explain how the fix addresses the examiner's concern\n\n### Step 4: Round 2 — Follow-Up Review\n\nUse `send_input` with the saved reviewer id from Round 1:\n\n```text\nsend_input:\n  target: [saved reviewer id from Round 1]\n  message: |\n    Here is the revised patent application after addressing your office action.\n\n    CHANGES MADE:\n    [list of all changes with rationale]\n\n    REVISED CLAIMS:\n    [updated claims]\n\n    REVISED SPECIFICATION EXCERPTS:\n    [changed sections]\n\n    Please re-examine:\n    1. Are the previous rejections overcome?\n    2. Are there new issues introduced by the amendments?\n    3. What is the updated patentability score?\n    4. Any remaining grounds for rejection?\n```\n\n### Step 5: Generate Improvement Report\n\nWrite `patent\u002FPATENT_REVIEW.md`:\n\n```markdown\n## Patent Review Report\n\n### Application Summary\n[Title, claims count, jurisdiction]\n\n### Review Round 1\n#### Office Action Summary\n[Key findings from examiner]\n\n#### Issues Found\n| # | Type | Severity | Claim\u002FSection | Issue | Citation | Fix Applied |\n|---|------|----------|--------------|-------|----------|-------------|\n| 1 | Clarity | CRITICAL | Claim 3 | Indefinite term \"rapid\" | 112(b) | Defined in spec |\n| 2 | Novelty | MAJOR | Claim 1 | Ref X anticipates element C | 102 | Amended claim |\n\n#### Score After Round 1: [X]\u002F10\n\n### Review Round 2\n#### Follow-Up Assessment\n[Are previous rejections overcome?]\n\n#### Remaining Issues\n[Any issues still outstanding]\n\n#### Score After Round 2: [X]\u002F10\n\n### Recommendations\n[Final recommendations before proceeding to jurisdiction formatting]\n- [ ] All CRITICAL issues resolved\n- [ ] All MAJOR issues resolved or argued\n- [ ] Specification supports all claim amendments\n- [ ] Ready for jurisdiction formatting\n```\n\n## Key Rules\n\n- The reviewer persona must be a patent examiner, not a paper reviewer or academic.\n- Always use `model_reasoning_effort: \"xhigh\"` for maximum analysis depth.\n- Address CRITICAL and MAJOR issues before proceeding to the next phase.\n- Document all changes in the review report for traceability.\n- If the patentability score is below 5\u002F10 after Round 2, recommend significant rework before filing.\n- The review is advisory -- actual prosecution may proceed differently.\n","# Patent Examiner Review via Codex MCP (xhigh reasoning)\n\nGet a multi-round patent examiner review of the patent application based on: **$ARGUMENTS**\n\nAdapted from `\u002Fresearch-review`. The reviewer persona is a patent examiner, not a paper reviewer.\n\n## Constants\n\n- `REVIEWER_MODEL = gpt-6-astra` — Model used via Codex MCP\n- `REVIEW_ROUNDS = 2` — Number of review rounds\n- `EXAMINER_PERSONA = \"patent-examiner\"` — GPT-6-Astra persona\n\n## Prerequisites\n\n- Codex MCP Server configured:\n  ```bash\n  claude mcp add codex -s user -- python3 \"$HOME\u002Faris_repo\u002Fmcp-servers\u002Fcodex-exec\u002Fserver.py\"   # your ARIS clone's path\n  ```\n\n## Inputs\n\n1. `patent\u002FCLAIMS.md` — all drafted claims\n2. `patent\u002Fspecification\u002F` — all specification sections\n3. `patent\u002Ffigures\u002Fnumeral_index.md` — reference numeral mapping\n4. `patent\u002FPRIOR_ART_REPORT.md` — known prior art\n5. `patent\u002FINVENTION_DISCLOSURE.md` — invention structure\n\n## Workflow\n\n### Step 1: Gather Patent Context\n\nBefore calling the external reviewer, compile a comprehensive briefing:\n1. Read all claims (independent + dependent)\n2. Read specification sections (at least summary and detailed description)\n3. Read prior art report for context\n4. Identify: core inventive concept, claim scope, known prior art, target jurisdiction\n\n### Step 2: Round 1 — Full Examiner Review\n\nSend to `REVIEWER_MODEL` via `spawn_agent` with xhigh reasoning:\n\n```text\nspawn_agent:\n  model: gpt-6-astra\n  reasoning_effort: xhigh\n  message: |\n    You are a senior patent examiner at the [USPTO\u002FCNIPA\u002FEPO].\n    Examine this patent application and issue a detailed office action.\n\n    CLAIMS:\n    [all claims]\n\n    SPECIFICATION SUMMARY:\n    [key sections: title, technical field, background, summary, abstract]\n\n    PRIOR ART KNOWN:\n    [prior art references]\n\n    PATENTABILITY STANDARDS TO APPLY:\n    [US: 35 USC 101\u002F102\u002F103\u002F112 | CN: Articles 22, 26 | EP: Articles 54, 56, 83, 84]\n\n    Please issue an office action covering:\n\n    1. CLAIM CLARITY (112(b)\u002FArt 84):\n       - Are all terms definite?\n       - Any indefinite functional language?\n       - Antecedent basis issues?\n\n    2. WRITTEN DESCRIPTION (112(a)\u002FArt 83 first para):\n       - Does the spec support ALL claim scope?\n       - Any claim elements without spec support?\n\n    3. ENABLEMENT (112(a)\u002FArt 83):\n       - Can a POSITA practice the invention?\n       - Any missing algorithm\u002Fstructure for functional claims?\n\n    4. NOVELTY (102\u002FArt 54):\n       - Would any known reference anticipate any claim?\n       - Identify the closest single reference.\n\n    5. NON-OBVIOUSNESS (103\u002FArt 56):\n       - Would any combination render claims obvious?\n       - What is the motivation to combine?\n\n    6. CLAIM SCOPE:\n       - Are independent claims broad enough to be commercially valuable?\n       - Do dependent claims provide meaningful fallback positions?\n       - Any claims that are too broad (likely rejected) or too narrow (not valuable)?\n\n    7. SPECIFICATION QUALITY:\n       - Language issues (subjective terms, relative terms, result-to-be-achieved)\n       - Reference numeral consistency\n       - Missing embodiments\n\n    Format your response as a formal office action with:\n    - GROUNDS OF REJECTION for each issue (cite statute)\n    - SUGGESTED AMENDMENTS for each issue\n    - OVERALL PATENTABILITY SCORE: 1-10\n\n    Be rigorous and specific. This is a real examination.\n```\n\n### Step 3: Implement Fixes (Round 1)\n\nBased on the examiner's office action:\n\n1. **CRITICAL issues** (102 rejection, 112 indefiniteness, missing enablement):\n   - Must be fixed before proceeding\n   - Amend claims or add specification support\n\n2. **MAJOR issues** (103 obviousness, weak claim scope, missing support):\n   - Should be fixed or argued\n   - Consider claim amendments or specification additions\n\n3. **MINOR issues** (language quality, numeral consistency, formatting):\n   - Fix if time permits\n   - Document in output for later cleanup\n\nFor each fix:\n- Show the specific change (old claim -> new claim)\n- Explain how the fix addresses the examiner's concern\n\n### Step 4: Round 2 — Follow-Up Review\n\nUse `send_input` with the saved reviewer id from Round 1:\n\n```text\nsend_input:\n  target: [saved reviewer id from Round 1]\n  message: |\n    Here is the revised patent application after addressing your office action.\n\n    CHANGES MADE:\n    [list of all changes with rationale]\n\n    REVISED CLAIMS:\n    [updated claims]\n\n    REVISED SPECIFICATION EXCERPTS:\n    [changed sections]\n\n    Please re-examine:\n    1. Are the previous rejections overcome?\n    2. Are there new issues introduced by the amendments?\n    3. What is the updated patentability score?\n    4. Any remaining grounds for rejection?\n```\n\n### Step 5: Generate Improvement Report\n\nWrite `patent\u002FPATENT_REVIEW.md`:\n\n```markdown\n## Patent Review Report\n\n### Application Summary\n[Title, claims count, jurisdiction]\n\n### Review Round 1\n#### Office Action Summary\n[Key findings from examiner]\n\n#### Issues Found\n| # | Type | Severity | Claim\u002FSection | Issue | Citation | Fix Applied |\n|---|------|----------|--------------|-------|----------|-------------|\n| 1 | Clarity | CRITICAL | Claim 3 | Indefinite term \"rapid\" | 112(b) | Defined in spec |\n| 2 | Novelty | MAJOR | Claim 1 | Ref X anticipates element C | 102 | Amended claim |\n\n#### Score After Round 1: [X]\u002F10\n\n### Review Round 2\n#### Follow-Up Assessment\n[Are previous rejections overcome?]\n\n#### Remaining Issues\n[Any issues still outstanding]\n\n#### Score After Round 2: [X]\u002F10\n\n### Recommendations\n[Final recommendations before proceeding to jurisdiction formatting]\n- [ ] All CRITICAL issues resolved\n- [ ] All MAJOR issues resolved or argued\n- [ ] Specification supports all claim amendments\n- [ ] Ready for jurisdiction formatting\n```\n\n## Key Rules\n\n- The reviewer persona must be a patent examiner, not a paper reviewer or academic.\n- Always use `model_reasoning_effort: \"xhigh\"` for maximum analysis depth.\n- Address CRITICAL and MAJOR issues before proceeding to the next phase.\n- Document all changes in the review report for traceability.\n- If the patentability score is below 5\u002F10 after Round 2, recommend significant rework before filing.\n- The review is advisory -- actual prosecution may proceed differently.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(*), Read, Grep, Glob, Write, Edit","[patent-directory-or-scope]","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fpatent-review",0,"https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science","https:\u002F\u002Fgithub.com\u002FCZX-LBJ","一个没事喜欢随便写点代码的小菜鸡\r\n","2026-10-22 09:48:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CZX-LBJ\u002Fdeepseek-science --skill patent-review",{"tool":40,"command":41},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill patent-review",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill patent-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Fpatent-review\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7FEEKSNMRMKW6JEK93PFDFY","bio-free-energy-calculations","Performs alchemical free-energy calculations including relative binding free energy (RBFE \u002F FEP+) and absolute binding free energy (ABFE) via OpenFE, FEP+, GROMACS, AMBER pmemd, and OpenMM with explicit lambda scheduling, soft-core potentials, MBAR\u002FBAR analysis, cycle-closure validation, and protocol-appropriate enhanced sampling. Compares ML alternatives (Boltz-2 affinity, DeepDock). Use when ranking analogs by binding affinity beyond docking accuracy, performing prospective lead optimization, or validating SAR predictions.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Ffree-energy-calculations\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7FEE5CTE5QK55CEMXNNVWY9","bio-conformer-generation","Generates 3D conformer ensembles using RDKit ETKDGv3 with knowledge-enhanced distance geometry, MMFF94\u002FUFF force-field optimization, CREST + GFN2-xTB semi-empirical refinement, and macrocycle-aware torsion preferences. Provides explicit decision rules for single vs ensemble conformer use, RMSD pruning, energy windows, conformer count, and force-field choice. Use when preparing 3D ligands for docking, generating descriptor input for 3D QSAR, or sampling macrocycle\u002Fpeptide conformational ensembles.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fconformer-generation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FEDNGFEMFWD1MSEDR5H7CY","bio-admet-prediction","Predicts ADMET properties using ADMETlab 3.0 (119 platform features, including 77 prediction models with modeled-endpoint uncertainty), ADMET-AI, DeepChem MolNet, and chemprop D-MPNN with explicit handling of OECD QSAR principles, applicability domain assessment, calibration, hERG\u002FCYP\u002FAMES endpoints, and PAINS \u002F Lipinski \u002F Ro5 \u002F Veber \u002F BBB druglikeness filters. Use when filtering compounds for drug-likeness, prioritizing leads by predicted safety, or building an in-house ADMET QSAR model.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fadmet-prediction\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FED69GFB54FRF7AV5066DN","writing-systems-papers","Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says \"写系统论文\", \"systems paper structure\", \"OSDI paper\", \"SOSP paper\", or wants fine-grained structural guidance for a systems conference submission.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwriting-systems-papers\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FECVVDWZ0X0VEDTCE4B4DZ","wiki-enrich","Fill in the per-paper TODO sections of research-wiki\u002Fpapers\u002F\u003Cslug>.md pages that literature-ingest skills leave as bare scaffolds. Use when user says 'enrich wiki', 'fill paper TODOs', 'wiki body 補完', '把 paper 摘要寫進 wiki', 'research-wiki 自動填', or after a batch ingest that left papers\u002F as TODO scaffolds.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwiki-enrich\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FECD4BCJ2MTSBDDSE3ZAJ5","web-debug-search","Search GitHub, Stack Exchange, Chinese technical communities, official documentation, and general developer web sources for software errors, compatibility problems, API usage questions, and real-world workarounds. Use for debugging and discovery only; results are not paper-citation evidence.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fweb-debug-search\u002FSKILL.md",[],[]]