[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQSSSFC4DNF9B5S3SN94T5":3,"skill-same:01M7AQSSSFC4DNF9B5S3SN94T5":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AQSSSFC4DNF9B5S3SN94T5","iso27001-audit-prep",null,"\u002Fcs:iso27001-audit-prep \u003Cscope> — ISO 27001 ISMS audit readiness 6-question forcing interrogation. Use before annual Clause 9.2 internal audit, surveillance audit prep, or stage 1 certification readiness.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fcompliance-os\u002Fskills\u002Fiso27001-audit-prep\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"iso27001-audit-prep\"\ndescription: \"\u002Fcs:iso27001-audit-prep \u003Cscope> — ISO 27001 ISMS audit readiness 6-question forcing interrogation. Use before annual Clause 9.2 internal audit, surveillance audit prep, or stage 1 certification readiness.\"\n---\n\n# \u002Fcs:iso27001-audit-prep — ISO 27001 ISMS Audit Forcing Questions\n\n**Command:** `\u002Fcs:iso27001-audit-prep \u003Cscope>`\n\nThe ISO 27001 ISMS auditor pressure-tests any ISMS work. Six sample-driven questions before any internal audit, stage 1 readiness, or surveillance audit.\n\n## When to Run\n\n- Before annual Clause 9.2 internal audit\n- Before stage 1 \u002F stage 2 ISO 27001 certification audit\n- Before surveillance audit (year 2 \u002F year 3)\n- After material change to ISMS scope (new business unit, new product line, new SaaS adoption)\n- Post-incident (breach triggers ad-hoc ISMS audit)\n- Quarterly during high-growth phase\n\n## The Six ISMS Questions\n\n### 1. What's the audit scope, and is rolling 3-year coverage on track?\n**No 3-year coverage discipline, no defensible programme.**\n- Every Clause 4-10 + every applicable Annex A control must be audited at least once per 3-year cycle\n- Run `isms_audit_scheduler.py` in `ra-qm-team\u002Fskills\u002Fisms-audit-expert\u002F`\n- Confirm auditor independence — no self-audit on any sample\n\n### 2. When was the risk register last refreshed, and are treatments linked to Annex A controls?\n**Stale risk register = certification finding.**\n- Quarterly refresh expected; annual minimum\n- Every high\u002Fcritical risk must link to ≥ 1 Annex A control treating it\n- Residual risk acceptance documented + signed\n- Review against `iso27001_audit_playbook.md` for stage 1 expectations\n\n### 3. Show me the access review records — quarterly cadence, the last 4 quarters.\n**Most-cited finding area.**\n- Annex A.5.15 + A.8.2 + A.8.3 access controls\n- Sample real records pulled from Okta \u002F IAM, not curated audit-prep packs\n- For each terminated employee in last 90 days: deprovisioning evidence within 24-hour SLA\n- Privileged access reviewed at finer granularity\n\n### 4. What's the supplier inventory + last review evidence?\n**Second-most-cited finding area.**\n- Annex A.5.19-A.5.21 supplier management\n- Critical SaaS suppliers reviewed at least annually\n- DPAs signed for personal-data sub-processors (cross-check with cs-dpo-gdpr)\n- AI-specific contract clauses where third-party AI services in use (cross-check with cs-aims-iso42001)\n\n### 5. Where's the incident response evidence + post-incident review?\n**A.5.24-27 + A.6.8 — high-stakes audit area.**\n- Severity definitions documented + consistently applied\n- Last 5 incidents have post-incident review (PIR) within 30-day SLA\n- GDPR Article 33 \u002F 34 notification timing aligned with A.5.24 (cross-check with cs-dpo-gdpr)\n- Blameless retro culture; not punitive\n\n### 6. What's the management review cadence + inputs?\n**Clause 9.3 required inputs are prescriptive — easy to miss.**\n- Required inputs: audit results, risks, performance, nonconformities, opportunities\n- Schedule: annual minimum; quarterly preferred for mature programs\n- Outputs documented + tracked to closure\n- Integrated review across frameworks (per `multi_framework_audit_playbook.md`) preferred to separate reviews\n\n## Workflow\n\n```bash\n# 1. Audit programme planning\npython ra-qm-team\u002Fskills\u002Fisms-audit-expert\u002Fscripts\u002Fisms_audit_scheduler.py audit_scope.json\n\n# 2. Mock audit for readiness check\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Faudit_simulator.py iso27001_scope.json\n\n# 3. Cross-framework reuse (SOC 2 = 75% overlap; ISO 42001 = 60% reuse)\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Fcross_framework_mapper.py program.json\n```\n\n## Output Format\n\n```markdown\n# ISO 27001 Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[programme-plan | finding-severity | cert-readiness | incident-followup]\n\n## Audit Programme Status\n- Clauses scheduled this year: \u003Clist>\n- Annex A controls scheduled: \u003Ccount>\n- Rolling 3-year coverage: clean | gaps in \u003Clist>\n- Auditor independence: clean | issues in \u003Clist>\n\n## Risk Register Health\n- Last refresh: YYYY-MM-DD\n- High\u002Fcritical risks without Annex A control link: N\n- Residual risk acceptance documentation: complete | gaps\n\n## High-Stakes Controls Status\n- A.5.15 + A.8.2 + A.8.3 access control: pass\u002Ffail with sample\n- A.5.19-A.5.21 supplier mgmt: pass\u002Ffail with sample\n- A.5.24-27 + A.6.8 incident response: pass\u002Ffail with sample\n- A.8.15-16 logging: pass\u002Ffail with sample\n\n## Management Review Status\n- Last review date: YYYY-MM-DD\n- Required Article 9.3 inputs present: yes\u002Fno\n- Open action items past due: N\n\n## Cross-Framework Impact\n- SOC 2 controls affected: \u003Clist>\n- ISO 42001 controls affected (if applicable): \u003Clist>\n- GDPR Article 32 controls affected: \u003Clist>\n\n## Verdict\n🟢 READY | 🟡 CLOSE-CRITICALS-FIRST | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + corrective-action timeline]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:soc2-audit-prep` — for SOC 2 cross-walk pair (75% overlap)\n- `\u002Fcs:aims-audit` — for ISO 42001 AIMS cross-walk\n- `\u002Fcs:gdpr-audit-prep` — for Article 32 organizational measures overlap\n- `\u002Fcs:ciso-review` — for executive cybersecurity strategy\n- `\u002Fcs:decide` — to log the verdict\n\n## Related\n\n- Agent: [`cs-ciso-iso27001`](..\u002F..\u002Fagents\u002Fcs-ciso-iso27001.md)\n- Skill: [`isms-audit-expert`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fisms-audit-expert\u002FSKILL.md)\n- Playbook: [iso27001_audit_playbook.md](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fisms-audit-expert\u002Freferences\u002Fiso27001_audit_playbook.md)\n- Adjacent: `..\u002Fsoc2-audit-prep\u002F`, `..\u002Faims-audit\u002F`, `..\u002Fgdpr-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:iso27001-audit-prep — ISO 27001 ISMS Audit Forcing Questions\n\n**Command:** `\u002Fcs:iso27001-audit-prep \u003Cscope>`\n\nThe ISO 27001 ISMS auditor pressure-tests any ISMS work. Six sample-driven questions before any internal audit, stage 1 readiness, or surveillance audit.\n\n## When to Run\n\n- Before annual Clause 9.2 internal audit\n- Before stage 1 \u002F stage 2 ISO 27001 certification audit\n- Before surveillance audit (year 2 \u002F year 3)\n- After material change to ISMS scope (new business unit, new product line, new SaaS adoption)\n- Post-incident (breach triggers ad-hoc ISMS audit)\n- Quarterly during high-growth phase\n\n## The Six ISMS Questions\n\n### 1. What's the audit scope, and is rolling 3-year coverage on track?\n**No 3-year coverage discipline, no defensible programme.**\n- Every Clause 4-10 + every applicable Annex A control must be audited at least once per 3-year cycle\n- Run `isms_audit_scheduler.py` in `ra-qm-team\u002Fskills\u002Fisms-audit-expert\u002F`\n- Confirm auditor independence — no self-audit on any sample\n\n### 2. When was the risk register last refreshed, and are treatments linked to Annex A controls?\n**Stale risk register = certification finding.**\n- Quarterly refresh expected; annual minimum\n- Every high\u002Fcritical risk must link to ≥ 1 Annex A control treating it\n- Residual risk acceptance documented + signed\n- Review against `iso27001_audit_playbook.md` for stage 1 expectations\n\n### 3. Show me the access review records — quarterly cadence, the last 4 quarters.\n**Most-cited finding area.**\n- Annex A.5.15 + A.8.2 + A.8.3 access controls\n- Sample real records pulled from Okta \u002F IAM, not curated audit-prep packs\n- For each terminated employee in last 90 days: deprovisioning evidence within 24-hour SLA\n- Privileged access reviewed at finer granularity\n\n### 4. What's the supplier inventory + last review evidence?\n**Second-most-cited finding area.**\n- Annex A.5.19-A.5.21 supplier management\n- Critical SaaS suppliers reviewed at least annually\n- DPAs signed for personal-data sub-processors (cross-check with cs-dpo-gdpr)\n- AI-specific contract clauses where third-party AI services in use (cross-check with cs-aims-iso42001)\n\n### 5. Where's the incident response evidence + post-incident review?\n**A.5.24-27 + A.6.8 — high-stakes audit area.**\n- Severity definitions documented + consistently applied\n- Last 5 incidents have post-incident review (PIR) within 30-day SLA\n- GDPR Article 33 \u002F 34 notification timing aligned with A.5.24 (cross-check with cs-dpo-gdpr)\n- Blameless retro culture; not punitive\n\n### 6. What's the management review cadence + inputs?\n**Clause 9.3 required inputs are prescriptive — easy to miss.**\n- Required inputs: audit results, risks, performance, nonconformities, opportunities\n- Schedule: annual minimum; quarterly preferred for mature programs\n- Outputs documented + tracked to closure\n- Integrated review across frameworks (per `multi_framework_audit_playbook.md`) preferred to separate reviews\n\n## Workflow\n\n```bash\n# 1. Audit programme planning\npython ra-qm-team\u002Fskills\u002Fisms-audit-expert\u002Fscripts\u002Fisms_audit_scheduler.py audit_scope.json\n\n# 2. Mock audit for readiness check\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Faudit_simulator.py iso27001_scope.json\n\n# 3. Cross-framework reuse (SOC 2 = 75% overlap; ISO 42001 = 60% reuse)\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Fcross_framework_mapper.py program.json\n```\n\n## Output Format\n\n```markdown\n# ISO 27001 Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[programme-plan | finding-severity | cert-readiness | incident-followup]\n\n## Audit Programme Status\n- Clauses scheduled this year: \u003Clist>\n- Annex A controls scheduled: \u003Ccount>\n- Rolling 3-year coverage: clean | gaps in \u003Clist>\n- Auditor independence: clean | issues in \u003Clist>\n\n## Risk Register Health\n- Last refresh: YYYY-MM-DD\n- High\u002Fcritical risks without Annex A control link: N\n- Residual risk acceptance documentation: complete | gaps\n\n## High-Stakes Controls Status\n- A.5.15 + A.8.2 + A.8.3 access control: pass\u002Ffail with sample\n- A.5.19-A.5.21 supplier mgmt: pass\u002Ffail with sample\n- A.5.24-27 + A.6.8 incident response: pass\u002Ffail with sample\n- A.8.15-16 logging: pass\u002Ffail with sample\n\n## Management Review Status\n- Last review date: YYYY-MM-DD\n- Required Article 9.3 inputs present: yes\u002Fno\n- Open action items past due: N\n\n## Cross-Framework Impact\n- SOC 2 controls affected: \u003Clist>\n- ISO 42001 controls affected (if applicable): \u003Clist>\n- GDPR Article 32 controls affected: \u003Clist>\n\n## Verdict\n🟢 READY | 🟡 CLOSE-CRITICALS-FIRST | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + corrective-action timeline]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:soc2-audit-prep` — for SOC 2 cross-walk pair (75% overlap)\n- `\u002Fcs:aims-audit` — for ISO 42001 AIMS cross-walk\n- `\u002Fcs:gdpr-audit-prep` — for Article 32 organizational measures overlap\n- `\u002Fcs:ciso-review` — for executive cybersecurity strategy\n- `\u002Fcs:decide` — to log the verdict\n\n## Related\n\n- Agent: [`cs-ciso-iso27001`](..\u002F..\u002Fagents\u002Fcs-ciso-iso27001.md)\n- Skill: [`isms-audit-expert`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fisms-audit-expert\u002FSKILL.md)\n- Playbook: [iso27001_audit_playbook.md](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fisms-audit-expert\u002Freferences\u002Fiso27001_audit_playbook.md)\n- Adjacent: `..\u002Fsoc2-audit-prep\u002F`, `..\u002Faims-audit\u002F`, `..\u002Fgdpr-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","992d25a425dee442a1f6a628d00a4fed33efe839","compliance-os\u002Fskills\u002Fiso27001-audit-prep","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill iso27001-audit-prep",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill iso27001-audit-prep",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill iso27001-audit-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fcompliance-os\u002Fskills\u002Fiso27001-audit-prep\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]