[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVMGYCDPA1NNJ4GFFVZJZC":3,"skill-same:01M7CVMGYCDPA1NNJ4GFFVZJZC":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":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CVMGYCDPA1NNJ4GFFVZJZC","literature-review",null,"Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdocuments-productivity\u002Fscientific-thinking-literature-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: literature-review\ndescription: Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.\nmetadata:\n  origin: community\n---\n\n# Literature Review\n\nUse this skill when the task is to find, screen, synthesize, and cite a body of\nacademic or technical literature.\n\n## When to Use\n\n- Building a systematic, scoping, or narrative literature review.\n- Synthesizing the state of the art for a research question.\n- Finding gaps, contradictions, or future-work directions.\n- Preparing citation-backed background sections for papers or reports.\n- Comparing evidence across peer-reviewed papers, preprints, patents, and\n  technical reports.\n\n## Review Types\n\n- **Narrative review**: broad synthesis; useful for orientation.\n- **Scoping review**: maps concepts, methods, and evidence gaps.\n- **Systematic review**: predefined protocol, reproducible search, explicit\n  screening and exclusion.\n- **Meta-analysis**: systematic review plus quantitative effect aggregation.\n\nAsk the user which level of rigor is needed. If unspecified, default to a\nscoping review for exploratory work and a systematic review for publication or\nclinical claims.\n\n## Workflow\n\n### 1. Define the Question\n\nConvert the prompt into a searchable research question.\n\nFor clinical or biomedical work, use PICO:\n\n- Population\n- Intervention or exposure\n- Comparator\n- Outcome\n\nFor technical work, use:\n\n- system or domain\n- method or intervention\n- comparison baseline\n- evaluation metric\n\n### 2. Plan the Search\n\nCreate a search protocol before collecting sources:\n\n- databases to search\n- date range\n- languages\n- publication types\n- inclusion criteria\n- exclusion criteria\n- exact search strings\n\nMinimum useful database set:\n\n- PubMed for biomedical and life-sciences literature.\n- arXiv for CS, math, physics, quantitative biology, and preprints.\n- Semantic Scholar or Crossref for broad academic discovery.\n- Domain-specific sources when relevant, such as clinical-trial registries,\n  patent databases, standards bodies, or official technical docs.\n\n### 3. Search and Log Evidence\n\nKeep a search log that makes the review reproducible:\n\n```markdown\n| Database | Date searched | Query | Filters | Results | Export |\n| --- | --- | --- | --- | ---: | --- |\n| PubMed | 2026-05-11 | `(\"CRISPR\"[tiab] OR \"Cas9\"[tiab]) AND \"sickle cell\"[tiab]` | 2020:2026, English | 86 | PMID list |\n| arXiv | 2026-05-11 | `CRISPR sickle cell gene editing` | q-bio, 2020:2026 | 9 | BibTeX |\n```\n\nSave raw IDs, URLs, DOIs, abstracts, and notes separately from the final prose.\n\n### 4. Deduplicate\n\nDeduplicate in this order:\n\n1. DOI\n2. PMID or arXiv ID\n3. exact title\n4. normalized title plus first author and year\n\nRecord how many duplicates were removed.\n\n### 5. Screen Sources\n\nScreen in stages:\n\n1. title\n2. abstract\n3. full text\n\nFor systematic work, record exclusion reasons:\n\n- wrong population\n- wrong intervention\n- wrong outcome\n- not primary research\n- duplicate\n- unavailable full text\n- outside date range\n\n### 6. Extract Data\n\nUse a structured extraction table:\n\n```markdown\n| Study | Design | Population\u002FData | Method | Comparator | Outcome | Key finding | Limitations |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| Author Year | RCT\u002Fcohort\u002Freview\u002Fetc. | sample or corpus | method | baseline | measured outcome | result | caveat |\n```\n\nFor technical papers, include dataset, benchmark, metric, baseline, and\nreproducibility notes.\n\n### 7. Synthesize\n\nGroup evidence by theme rather than summarizing papers one by one.\n\nUseful synthesis lenses:\n\n- strongest evidence\n- conflicting evidence\n- methodological weaknesses\n- population or dataset limits\n- recency and replication\n- practical implications\n- unanswered questions\n\nSeparate claims by confidence:\n\n- **High confidence**: replicated, high-quality evidence across sources.\n- **Medium confidence**: plausible but limited by sample, method, or recency.\n- **Low confidence**: early, speculative, single-source, or weakly measured.\n\n### 8. Verify Citations\n\nBefore finalizing:\n\n- verify DOI, PMID, arXiv ID, or official URL\n- check author names and publication year\n- do not cite a paper for a claim it does not make\n- mark preprints as preprints\n- distinguish reviews from primary evidence\n\n## Output Template\n\n```markdown\n# Literature Review: \u003CTopic>\n\nGenerated: \u003Cdate>\nReview type: \u003Cnarrative | scoping | systematic | meta-analysis>\nSearch window: \u003Cdates>\nDatabases: \u003Clist>\n\n## Research Question\n\n## Search Strategy\n\n## Inclusion and Exclusion Criteria\n\n## Evidence Summary\n\n## Thematic Synthesis\n\n## Gaps and Limitations\n\n## References\n\n## Search Log\n```\n\n## Pitfalls\n\n- Do not treat search snippets as evidence.\n- Do not mix preprints, reviews, and primary studies without labeling them.\n- Do not omit negative or conflicting findings.\n- Do not claim systematic-review rigor without a reproducible protocol.\n- Do not use a single database for a broad claim unless the scope is explicitly\n  limited to that database.\n","# Literature Review\n\nUse this skill when the task is to find, screen, synthesize, and cite a body of\nacademic or technical literature.\n\n## When to Use\n\n- Building a systematic, scoping, or narrative literature review.\n- Synthesizing the state of the art for a research question.\n- Finding gaps, contradictions, or future-work directions.\n- Preparing citation-backed background sections for papers or reports.\n- Comparing evidence across peer-reviewed papers, preprints, patents, and\n  technical reports.\n\n## Review Types\n\n- **Narrative review**: broad synthesis; useful for orientation.\n- **Scoping review**: maps concepts, methods, and evidence gaps.\n- **Systematic review**: predefined protocol, reproducible search, explicit\n  screening and exclusion.\n- **Meta-analysis**: systematic review plus quantitative effect aggregation.\n\nAsk the user which level of rigor is needed. If unspecified, default to a\nscoping review for exploratory work and a systematic review for publication or\nclinical claims.\n\n## Workflow\n\n### 1. Define the Question\n\nConvert the prompt into a searchable research question.\n\nFor clinical or biomedical work, use PICO:\n\n- Population\n- Intervention or exposure\n- Comparator\n- Outcome\n\nFor technical work, use:\n\n- system or domain\n- method or intervention\n- comparison baseline\n- evaluation metric\n\n### 2. Plan the Search\n\nCreate a search protocol before collecting sources:\n\n- databases to search\n- date range\n- languages\n- publication types\n- inclusion criteria\n- exclusion criteria\n- exact search strings\n\nMinimum useful database set:\n\n- PubMed for biomedical and life-sciences literature.\n- arXiv for CS, math, physics, quantitative biology, and preprints.\n- Semantic Scholar or Crossref for broad academic discovery.\n- Domain-specific sources when relevant, such as clinical-trial registries,\n  patent databases, standards bodies, or official technical docs.\n\n### 3. Search and Log Evidence\n\nKeep a search log that makes the review reproducible:\n\n```markdown\n| Database | Date searched | Query | Filters | Results | Export |\n| --- | --- | --- | --- | ---: | --- |\n| PubMed | 2026-05-11 | `(\"CRISPR\"[tiab] OR \"Cas9\"[tiab]) AND \"sickle cell\"[tiab]` | 2020:2026, English | 86 | PMID list |\n| arXiv | 2026-05-11 | `CRISPR sickle cell gene editing` | q-bio, 2020:2026 | 9 | BibTeX |\n```\n\nSave raw IDs, URLs, DOIs, abstracts, and notes separately from the final prose.\n\n### 4. Deduplicate\n\nDeduplicate in this order:\n\n1. DOI\n2. PMID or arXiv ID\n3. exact title\n4. normalized title plus first author and year\n\nRecord how many duplicates were removed.\n\n### 5. Screen Sources\n\nScreen in stages:\n\n1. title\n2. abstract\n3. full text\n\nFor systematic work, record exclusion reasons:\n\n- wrong population\n- wrong intervention\n- wrong outcome\n- not primary research\n- duplicate\n- unavailable full text\n- outside date range\n\n### 6. Extract Data\n\nUse a structured extraction table:\n\n```markdown\n| Study | Design | Population\u002FData | Method | Comparator | Outcome | Key finding | Limitations |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| Author Year | RCT\u002Fcohort\u002Freview\u002Fetc. | sample or corpus | method | baseline | measured outcome | result | caveat |\n```\n\nFor technical papers, include dataset, benchmark, metric, baseline, and\nreproducibility notes.\n\n### 7. Synthesize\n\nGroup evidence by theme rather than summarizing papers one by one.\n\nUseful synthesis lenses:\n\n- strongest evidence\n- conflicting evidence\n- methodological weaknesses\n- population or dataset limits\n- recency and replication\n- practical implications\n- unanswered questions\n\nSeparate claims by confidence:\n\n- **High confidence**: replicated, high-quality evidence across sources.\n- **Medium confidence**: plausible but limited by sample, method, or recency.\n- **Low confidence**: early, speculative, single-source, or weakly measured.\n\n### 8. Verify Citations\n\nBefore finalizing:\n\n- verify DOI, PMID, arXiv ID, or official URL\n- check author names and publication year\n- do not cite a paper for a claim it does not make\n- mark preprints as preprints\n- distinguish reviews from primary evidence\n\n## Output Template\n\n```markdown\n# Literature Review: \u003CTopic>\n\nGenerated: \u003Cdate>\nReview type: \u003Cnarrative | scoping | systematic | meta-analysis>\nSearch window: \u003Cdates>\nDatabases: \u003Clist>\n\n## Research Question\n\n## Search Strategy\n\n## Inclusion and Exclusion Criteria\n\n## Evidence Summary\n\n## Thematic Synthesis\n\n## Gaps and Limitations\n\n## References\n\n## Search Log\n```\n\n## Pitfalls\n\n- Do not treat search snippets as evidence.\n- Do not mix preprints, reviews, and primary studies without labeling them.\n- Do not omit negative or conflicting findings.\n- Do not claim systematic-review rigor without a reproducible protocol.\n- Do not use a single database for a broad claim unless the scope is explicitly\n  limited to that database.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","a73152352c0612252131e5cf84e91312a6cf17dc","documents-productivity\u002Fscientific-thinking-literature-review","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill literature-review",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill literature-review",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill literature-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdocuments-productivity\u002Fscientific-thinking-literature-review\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"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},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\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},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\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":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"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},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\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},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]