[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ECNAXNBF4CTZ2JD09DESKA":3,"skill-same:01M7ECNAXNBF4CTZ2JD09DESKA":148},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7ECNAXNBF4CTZ2JD09DESKA","peer-review",null,"Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments. Use for authorized review of scientific manuscripts, protocols, preprints, or research proposals; reporting-guideline selection; claim–evidence checks; methods, statistics, reproducibility, ethics, figure\u002Ftable, and citation critique; or revision-response planning.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: peer-review\ndescription: Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments. Use for authorized review of scientific manuscripts, protocols, preprints, or research proposals; reporting-guideline selection; claim–evidence checks; methods, statistics, reproducibility, ethics, figure\u002Ftable, and citation critique; or revision-response planning.\nlicense: MIT\ncompatibility: Python 3.11+ standard library. Bundled CLIs are deterministic and local-only; they accept bounded JSON, CSV, or Markdown and make no network, model, image, or external-service calls.\nmetadata:\n  version: \"2.1\"\n  skill-author: K-Dense Inc.\n---\n\n# Peer Review\n\nSupport an accountable human reviewer with a rigorous, fair, actionable assessment. Treat every unpublished submission and review as confidential.\n\n## Mandatory safety boundary\n\nBefore reading or analyzing unpublished content:\n\n1. Confirm the user is authorized by the publisher, editor, author, or other material owner.\n2. Check the target venue’s review, confidentiality, co-review, retention, and AI\u002Ftool policies.\n3. Record conflicts, competence limits, requested scope, and specialist-review needs.\n4. Default to local-only processing.\n\nIf authorization is unclear, do not inspect or quote the manuscript. Ask for confirmation or use only the bundled local CLIs, whose reports do not echo manuscript text.\n\nNever:\n\n- Send unpublished manuscript, supplement, review, or editorial text to an external service without specific publisher\u002Fauthor authorization and venue permission\n- Upload confidential content to a public model, search engine, citation service, grammar tool, plagiarism checker, or image service\n- Reuse content for training, benchmarking, product improvement, or unrelated research\n- Read broad environment state, `.env` files, API keys, or credentials\n- Call a network, LLM, or image API from bundled tools\n- Invoke another skill or a PDF\u002Fimage pipeline automatically\n- Impersonate an assigned reviewer, editor, journal, funder, or author\n- Fabricate manuscript details, review findings, citations, analyses, experiments, reproduction, or an editorial outcome\n- Announce a decision that belongs to an editor or panel\n\nDelete local copies and derivatives when policy requires; otherwise retain only what the controlling policy authorizes. Record deletion or retention without copying confidential content into the record.\n\nRead `references\u002Fethical_review_practice.md` before handling confidential material.\n\n## Human accountability\n\nLabel generated text as a working draft. The accountable human must:\n\n- Read the complete authorized submission and relevant supplements\n- Verify every factual statement, calculation, citation, and manuscript location\n- Resolve conflicts and disclose assistance as required\n- Rewrite comments in their own expert judgment\n- Submit through the authorized channel\n\nAutomated coverage, consistency, or lint results are not peer review and do not establish manuscript merit.\n\n## Intake gate\n\nCopy and complete `assets\u002Freview_intake_template.json`, then run:\n\n```bash\npython3 scripts\u002Fvalidate_review_intake.py completed-intake.json\n```\n\nProceed only when status is `READY_FOR_LOCAL_REVIEW`.\n\nThe validator blocks:\n\n- Undocumented authorization\n- Missing human accountability\n- Unassessed or unresolved conflicts\n- Unknown review model or unchecked venue policy\n- Unauthorized AI assistance\n- External service use\n- Data reuse\n- Missing deletion\u002Fretention planning\n\nIt validates declarations, not their truth.\n\n## Review workflow\n\n### 1. Establish scope and available evidence\n\nRecord:\n\n- Submission type and stage\n- Review question and requested focus\n- Target venue and review model\n- Materials actually available: manuscript, supplements, protocol, registration, analysis plan, data\u002Fcode statement, prior decision, or response letter\n- Competence areas and limits\n- Missing material that prevents assessment\n\nDo not infer absent content. Use “not reported” or “not available for review.”\n\n### 2. Orient without deciding\n\nCreate a short neutral map:\n\n- Research question\n- Population or system\n- Design and unit\n- Intervention, exposure, test, or model\n- Comparator\u002Freference\n- Outcomes and timing\n- Principal claims\n\nDo not write an acceptance\u002Frejection recommendation. Identify what evidence would be needed to evaluate each claim.\n\n### 3. Select reporting guidance\n\nCopy `assets\u002Fstudy_profile_template.json` and run:\n\n```bash\npython3 scripts\u002Fselect_reporting_guidelines.py local-profile.json\n```\n\nFor checklist coverage:\n\n```bash\npython3 scripts\u002Fselect_reporting_guidelines.py \\\n  local-profile.json \\\n  --coverage local-coverage.csv\n```\n\nUse the current base guideline, explanation\u002Felaboration, applicable extensions, and target venue policy. See `references\u002Freporting_standards.md`.\n\n**Critical distinction:** reporting completeness is not design quality, risk of bias, validity, or merit. Never convert missing items into an automatic score or publication judgment.\n\n### 4. Map claims to evidence\n\nPrioritize central, causal, mechanistic, safety, diagnostic, prediction, and generalization claims.\n\nFor each claim, record:\n\n- Location and claim ID\n- Supporting result, figure, table, analysis, or citation IDs\n- Direction, magnitude, population, outcome, timepoint, and uncertainty alignment\n- Limitation or alternative explanation\n- Bounded requested action\n\nRun:\n\n```bash\npython3 scripts\u002Fvalidate_claim_evidence.py local-claim-matrix.csv\n```\n\nStart from `assets\u002Fclaim_evidence_matrix_template.csv`. The report emits IDs and counts, not claim text.\n\n### 5. Review methods and statistics\n\nAssess in this order:\n\n1. Question and target quantity\n2. Design and unit of inference\n3. Sampling, allocation, controls, masking, and timing\n4. Sample-size or precision rationale\n5. Inclusion, exclusion, attrition, and missingness\n6. Analysis–design alignment and assumptions\n7. Multiplicity and prespecification\n8. Effect estimates, uncertainty, denominators, and harms\n9. Interpretation, causality, and generalizability\n\nUse `references\u002Fcommon_issues.md` and `references\u002Fstatistical_reproducibility.md`.\n\nFor a structured local audit:\n\n```bash\npython3 scripts\u002Faudit_statistics_reproducibility.py \\\n  local-statistics-reproducibility.json\n```\n\nStart from `assets\u002Fstatistical_reproducibility_template.json`. Request specialist review when a central method exceeds competence; do not hide uncertainty behind a generic critique.\n\n### 6. Review reproducibility and transparency\n\nCheck, as applicable:\n\n- Protocol, registration, amendments, and analysis-plan consistency\n- Data provenance, exclusions, transformations, and accession IDs\n- Software, package, model, and parameter versions\n- Code, environment, seeds, run instructions, and tests\n- Data, code, materials, and model availability or justified restrictions\n- Domain metadata standards\n\nDo not claim reproduction unless authorized inputs were actually run with documented commands, environment, and outputs.\n\n### 7. Review ethics and integrity\n\nCheck applicable approvals, consent, welfare, privacy, community governance, funding, sponsor role, conflicts, authorship\u002Fcontribution, registration, biosafety, and dual-use concerns.\n\nDescribe observable evidence and uncertainty. Do not accuse authors or investigate them. Route credible concerns through the confidential editor channel under venue policy.\n\n### 8. Review figures, tables, and citations\n\nFor figures and tables, assess:\n\n- Consistency with text and supplements\n- Denominators, units, axes, scales, uncertainty, and legends\n- Accessible encoding and sufficient context\n- Image acquisition\u002Fprocessing disclosure and source-data policy\n\nThis skill has no image-generation or PDF-conversion workflow. Use only user-authorized local artifacts and tools.\n\nFor Pandoc-style citations such as `[@ref-id]`:\n\n```bash\npython3 scripts\u002Faudit_citations.py local-manuscript.md local-references.csv\n```\n\nStart from `assets\u002Fcitation_references_template.csv`. This checks key consistency and identifier format only; it does not verify that a source exists or supports a claim.\n\n### 9. Draft actionable comments\n\nGenerate a private scaffold only after intake passes:\n\n```bash\npython3 scripts\u002Fgenerate_review_scaffold.py \\\n  completed-intake.json \\\n  -o private-review.md\n```\n\nEvery major\u002Fminor comment should include:\n\n- **Location**\n- **Observation**\n- **Evidence or criterion**\n- **Why it matters**\n- **Requested action**\n\nPrioritize:\n\n- Claim–evidence alignment\n- Methods and statistical validity\n- Reproducibility and transparency\n- Ethics and participant\u002Fanimal protection\n- Reporting needed for appraisal\n- Figures, tables, limitations, and citations\n\nRequests for new work must be necessary to support a central claim and proportionate to scope. Offer narrowing, clarification, sensitivity analysis, correction, or limitation language when that is sufficient.\n\n### 10. Keep channels separate\n\n**Comments to authors** contain the scientific review, strengths, major\u002Fminor comments, and limitations.\n\n**Confidential comments to editor** contain only policy-appropriate conflicts, competence limits, assistance disclosure, specialist requests, or substantiated integrity\u002Fprocess concerns that require a separate route.\n\nDo not place ordinary criticism only in confidential notes. Do not reveal reviewer identity under an anonymized process.\n\n### 11. Lint and finalize\n\n```bash\npython3 scripts\u002Flint_review.py private-review.md\n```\n\nThe linter checks channel separation, unresolved placeholders, a narrow abusive-language lexicon, role\u002Fdecision phrases, and required actionability fields. It emits line numbers and rule IDs, not review text. Human tone and scientific review remain mandatory.\n\nBefore handoff:\n\n- Verify all locations and evidence.\n- Remove unsupported or speculative criticism.\n- Confirm professional, non-abusive language.\n- State review limits and specialist needs.\n- Disclose permitted assistance.\n- Remove all placeholders.\n- Ensure no invented citation, experiment, reanalysis, or outcome.\n- Follow the documented deletion\u002Fretention rule.\n\n## Local tool index\n\n- `scripts\u002Fvalidate_review_intake.py` — scope, authorization, conflicts, policy, handling\n- `scripts\u002Fselect_reporting_guidelines.py` — dated selector and non-scoring coverage audit\n- `scripts\u002Fvalidate_claim_evidence.py` — claim\u002Fevidence alignment matrix\n- `scripts\u002Faudit_statistics_reproducibility.py` — methods\u002Fstatistics\u002Freproducibility checklist\n- `scripts\u002Faudit_citations.py` — local citation\u002Freference consistency\n- `scripts\u002Fgenerate_review_scaffold.py` — separated private Markdown scaffold\n- `scripts\u002Flint_review.py` — tone, channel, and actionability lint\n\nFull schemas and exit codes: `references\u002Ftool_reference.md`.\n\n## References and assets\n\n- `references\u002Fethical_review_practice.md` — COPE\u002FICMJE duties, confidentiality, AI, channels\n- `references\u002Freporting_standards.md` — current major guidelines and verified domain standards\n- `references\u002Fstatistical_reproducibility.md` — methods, statistics, and reproducibility review\n- `references\u002Fcommon_issues.md` — contextual issue patterns and constructive responses\n- `references\u002Fsecurity_validation.md` — baseline remediation and local scan results\n- `assets\u002Fsource_ledger.csv` — authoritative sources verified 2026-07-23\n- `assets\u002Freporting_guidelines.json` — local selector catalog\n- `assets\u002Freview_scaffold_template.md` — private structured draft\n\nThe source ledger is dated. Recheck live primary sources and the target venue policy for a later review, without exposing confidential manuscript text in search queries.\n","# Peer Review\n\nSupport an accountable human reviewer with a rigorous, fair, actionable assessment. Treat every unpublished submission and review as confidential.\n\n## Mandatory safety boundary\n\nBefore reading or analyzing unpublished content:\n\n1. Confirm the user is authorized by the publisher, editor, author, or other material owner.\n2. Check the target venue’s review, confidentiality, co-review, retention, and AI\u002Ftool policies.\n3. Record conflicts, competence limits, requested scope, and specialist-review needs.\n4. Default to local-only processing.\n\nIf authorization is unclear, do not inspect or quote the manuscript. Ask for confirmation or use only the bundled local CLIs, whose reports do not echo manuscript text.\n\nNever:\n\n- Send unpublished manuscript, supplement, review, or editorial text to an external service without specific publisher\u002Fauthor authorization and venue permission\n- Upload confidential content to a public model, search engine, citation service, grammar tool, plagiarism checker, or image service\n- Reuse content for training, benchmarking, product improvement, or unrelated research\n- Read broad environment state, `.env` files, API keys, or credentials\n- Call a network, LLM, or image API from bundled tools\n- Invoke another skill or a PDF\u002Fimage pipeline automatically\n- Impersonate an assigned reviewer, editor, journal, funder, or author\n- Fabricate manuscript details, review findings, citations, analyses, experiments, reproduction, or an editorial outcome\n- Announce a decision that belongs to an editor or panel\n\nDelete local copies and derivatives when policy requires; otherwise retain only what the controlling policy authorizes. Record deletion or retention without copying confidential content into the record.\n\nRead `references\u002Fethical_review_practice.md` before handling confidential material.\n\n## Human accountability\n\nLabel generated text as a working draft. The accountable human must:\n\n- Read the complete authorized submission and relevant supplements\n- Verify every factual statement, calculation, citation, and manuscript location\n- Resolve conflicts and disclose assistance as required\n- Rewrite comments in their own expert judgment\n- Submit through the authorized channel\n\nAutomated coverage, consistency, or lint results are not peer review and do not establish manuscript merit.\n\n## Intake gate\n\nCopy and complete `assets\u002Freview_intake_template.json`, then run:\n\n```bash\npython3 scripts\u002Fvalidate_review_intake.py completed-intake.json\n```\n\nProceed only when status is `READY_FOR_LOCAL_REVIEW`.\n\nThe validator blocks:\n\n- Undocumented authorization\n- Missing human accountability\n- Unassessed or unresolved conflicts\n- Unknown review model or unchecked venue policy\n- Unauthorized AI assistance\n- External service use\n- Data reuse\n- Missing deletion\u002Fretention planning\n\nIt validates declarations, not their truth.\n\n## Review workflow\n\n### 1. Establish scope and available evidence\n\nRecord:\n\n- Submission type and stage\n- Review question and requested focus\n- Target venue and review model\n- Materials actually available: manuscript, supplements, protocol, registration, analysis plan, data\u002Fcode statement, prior decision, or response letter\n- Competence areas and limits\n- Missing material that prevents assessment\n\nDo not infer absent content. Use “not reported” or “not available for review.”\n\n### 2. Orient without deciding\n\nCreate a short neutral map:\n\n- Research question\n- Population or system\n- Design and unit\n- Intervention, exposure, test, or model\n- Comparator\u002Freference\n- Outcomes and timing\n- Principal claims\n\nDo not write an acceptance\u002Frejection recommendation. Identify what evidence would be needed to evaluate each claim.\n\n### 3. Select reporting guidance\n\nCopy `assets\u002Fstudy_profile_template.json` and run:\n\n```bash\npython3 scripts\u002Fselect_reporting_guidelines.py local-profile.json\n```\n\nFor checklist coverage:\n\n```bash\npython3 scripts\u002Fselect_reporting_guidelines.py \\\n  local-profile.json \\\n  --coverage local-coverage.csv\n```\n\nUse the current base guideline, explanation\u002Felaboration, applicable extensions, and target venue policy. See `references\u002Freporting_standards.md`.\n\n**Critical distinction:** reporting completeness is not design quality, risk of bias, validity, or merit. Never convert missing items into an automatic score or publication judgment.\n\n### 4. Map claims to evidence\n\nPrioritize central, causal, mechanistic, safety, diagnostic, prediction, and generalization claims.\n\nFor each claim, record:\n\n- Location and claim ID\n- Supporting result, figure, table, analysis, or citation IDs\n- Direction, magnitude, population, outcome, timepoint, and uncertainty alignment\n- Limitation or alternative explanation\n- Bounded requested action\n\nRun:\n\n```bash\npython3 scripts\u002Fvalidate_claim_evidence.py local-claim-matrix.csv\n```\n\nStart from `assets\u002Fclaim_evidence_matrix_template.csv`. The report emits IDs and counts, not claim text.\n\n### 5. Review methods and statistics\n\nAssess in this order:\n\n1. Question and target quantity\n2. Design and unit of inference\n3. Sampling, allocation, controls, masking, and timing\n4. Sample-size or precision rationale\n5. Inclusion, exclusion, attrition, and missingness\n6. Analysis–design alignment and assumptions\n7. Multiplicity and prespecification\n8. Effect estimates, uncertainty, denominators, and harms\n9. Interpretation, causality, and generalizability\n\nUse `references\u002Fcommon_issues.md` and `references\u002Fstatistical_reproducibility.md`.\n\nFor a structured local audit:\n\n```bash\npython3 scripts\u002Faudit_statistics_reproducibility.py \\\n  local-statistics-reproducibility.json\n```\n\nStart from `assets\u002Fstatistical_reproducibility_template.json`. Request specialist review when a central method exceeds competence; do not hide uncertainty behind a generic critique.\n\n### 6. Review reproducibility and transparency\n\nCheck, as applicable:\n\n- Protocol, registration, amendments, and analysis-plan consistency\n- Data provenance, exclusions, transformations, and accession IDs\n- Software, package, model, and parameter versions\n- Code, environment, seeds, run instructions, and tests\n- Data, code, materials, and model availability or justified restrictions\n- Domain metadata standards\n\nDo not claim reproduction unless authorized inputs were actually run with documented commands, environment, and outputs.\n\n### 7. Review ethics and integrity\n\nCheck applicable approvals, consent, welfare, privacy, community governance, funding, sponsor role, conflicts, authorship\u002Fcontribution, registration, biosafety, and dual-use concerns.\n\nDescribe observable evidence and uncertainty. Do not accuse authors or investigate them. Route credible concerns through the confidential editor channel under venue policy.\n\n### 8. Review figures, tables, and citations\n\nFor figures and tables, assess:\n\n- Consistency with text and supplements\n- Denominators, units, axes, scales, uncertainty, and legends\n- Accessible encoding and sufficient context\n- Image acquisition\u002Fprocessing disclosure and source-data policy\n\nThis skill has no image-generation or PDF-conversion workflow. Use only user-authorized local artifacts and tools.\n\nFor Pandoc-style citations such as `[@ref-id]`:\n\n```bash\npython3 scripts\u002Faudit_citations.py local-manuscript.md local-references.csv\n```\n\nStart from `assets\u002Fcitation_references_template.csv`. This checks key consistency and identifier format only; it does not verify that a source exists or supports a claim.\n\n### 9. Draft actionable comments\n\nGenerate a private scaffold only after intake passes:\n\n```bash\npython3 scripts\u002Fgenerate_review_scaffold.py \\\n  completed-intake.json \\\n  -o private-review.md\n```\n\nEvery major\u002Fminor comment should include:\n\n- **Location**\n- **Observation**\n- **Evidence or criterion**\n- **Why it matters**\n- **Requested action**\n\nPrioritize:\n\n- Claim–evidence alignment\n- Methods and statistical validity\n- Reproducibility and transparency\n- Ethics and participant\u002Fanimal protection\n- Reporting needed for appraisal\n- Figures, tables, limitations, and citations\n\nRequests for new work must be necessary to support a central claim and proportionate to scope. Offer narrowing, clarification, sensitivity analysis, correction, or limitation language when that is sufficient.\n\n### 10. Keep channels separate\n\n**Comments to authors** contain the scientific review, strengths, major\u002Fminor comments, and limitations.\n\n**Confidential comments to editor** contain only policy-appropriate conflicts, competence limits, assistance disclosure, specialist requests, or substantiated integrity\u002Fprocess concerns that require a separate route.\n\nDo not place ordinary criticism only in confidential notes. Do not reveal reviewer identity under an anonymized process.\n\n### 11. Lint and finalize\n\n```bash\npython3 scripts\u002Flint_review.py private-review.md\n```\n\nThe linter checks channel separation, unresolved placeholders, a narrow abusive-language lexicon, role\u002Fdecision phrases, and required actionability fields. It emits line numbers and rule IDs, not review text. Human tone and scientific review remain mandatory.\n\nBefore handoff:\n\n- Verify all locations and evidence.\n- Remove unsupported or speculative criticism.\n- Confirm professional, non-abusive language.\n- State review limits and specialist needs.\n- Disclose permitted assistance.\n- Remove all placeholders.\n- Ensure no invented citation, experiment, reanalysis, or outcome.\n- Follow the documented deletion\u002Fretention rule.\n\n## Local tool index\n\n- `scripts\u002Fvalidate_review_intake.py` — scope, authorization, conflicts, policy, handling\n- `scripts\u002Fselect_reporting_guidelines.py` — dated selector and non-scoring coverage audit\n- `scripts\u002Fvalidate_claim_evidence.py` — claim\u002Fevidence alignment matrix\n- `scripts\u002Faudit_statistics_reproducibility.py` — methods\u002Fstatistics\u002Freproducibility checklist\n- `scripts\u002Faudit_citations.py` — local citation\u002Freference consistency\n- `scripts\u002Fgenerate_review_scaffold.py` — separated private Markdown scaffold\n- `scripts\u002Flint_review.py` — tone, channel, and actionability lint\n\nFull schemas and exit codes: `references\u002Ftool_reference.md`.\n\n## References and assets\n\n- `references\u002Fethical_review_practice.md` — COPE\u002FICMJE duties, confidentiality, AI, channels\n- `references\u002Freporting_standards.md` — current major guidelines and verified domain standards\n- `references\u002Fstatistical_reproducibility.md` — methods, statistics, and reproducibility review\n- `references\u002Fcommon_issues.md` — contextual issue patterns and constructive responses\n- `references\u002Fsecurity_validation.md` — baseline remediation and local scan results\n- `assets\u002Fsource_ledger.csv` — authoritative sources verified 2026-07-23\n- `assets\u002Freporting_guidelines.json` — local selector catalog\n- `assets\u002Freview_scaffold_template.md` — private structured draft\n\nThe source ledger is dated. Recheck live primary sources and the target venue policy for a later review, without exposing confidential manuscript text in search queries.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":27},{"version":25,"skill-author":26},"2.1","K-Dense Inc.","Python 3.11+ standard library. Bundled CLIs are deterministic and local-only; they accept bounded JSON, CSV, or Markdown and make no network, model, image, or external-service calls.","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fscientific-skills\u002Fpeer-review",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill peer-review",{"tool":42,"command":43},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill peer-review",{"tool":45,"command":46},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill peer-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002FSKILL.md",true,[50,56,60,64,68,72,76,80,84,88,94,98,102,106,110,114,120,124,128,132,136,140,144],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fcitation_references_template.csv","ASSET","资产文件",196,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Fcitation_references_template.csv",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fclaim_evidence_matrix_template.csv",745,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Fclaim_evidence_matrix_template.csv",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Freporting_checklist_template.csv",968,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Freporting_checklist_template.csv",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Freporting_guidelines.json",13446,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Freporting_guidelines.json",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Freview_intake_template.json",1290,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Freview_intake_template.json",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Freview_scaffold_template.md",3025,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Freview_scaffold_template.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Fsource_ledger.csv",9147,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Fsource_ledger.csv",{"path":81,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fstatistical_reproducibility_template.json",7281,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Fstatistical_reproducibility_template.json",{"path":85,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fstudy_profile_template.json",197,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fassets\u002Fstudy_profile_template.json",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fcommon_issues.md","REFERENCE","参考文档",13999,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Freferences\u002Fcommon_issues.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fethical_review_practice.md",11131,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Freferences\u002Fethical_review_practice.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Freporting_standards.md",14032,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Freferences\u002Freporting_standards.md",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fsecurity_validation.md",3547,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Freferences\u002Fsecurity_validation.md",{"path":107,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fstatistical_reproducibility.md",11712,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Freferences\u002Fstatistical_reproducibility.md",{"path":111,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Ftool_reference.md",7781,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Freferences\u002Ftool_reference.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002F_common.py","SCRIPT","脚本",13896,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002F_common.py",{"path":121,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Faudit_citations.py",7097,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Faudit_citations.py",{"path":125,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":126,"sourceHtmlUrl":127},"scripts\u002Faudit_statistics_reproducibility.py",10455,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Faudit_statistics_reproducibility.py",{"path":129,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":130,"sourceHtmlUrl":131},"scripts\u002Fgenerate_review_scaffold.py",2634,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Fgenerate_review_scaffold.py",{"path":133,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":134,"sourceHtmlUrl":135},"scripts\u002Flint_review.py",9085,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Flint_review.py",{"path":137,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":138,"sourceHtmlUrl":139},"scripts\u002Fselect_reporting_guidelines.py",13594,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Fselect_reporting_guidelines.py",{"path":141,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":142,"sourceHtmlUrl":143},"scripts\u002Fvalidate_claim_evidence.py",7083,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Fvalidate_claim_evidence.py",{"path":145,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":146,"sourceHtmlUrl":147},"scripts\u002Fvalidate_review_intake.py",14466,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Fpeer-review\u002Fscripts\u002Fvalidate_review_intake.py",[149,156,164,173,181,188],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":19},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":19},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":19},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":19},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":19},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":19},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]