[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MAZPJCKTDC288AGDS8G2AQ":3,"skill-same:01M6MAZPJCKTDC288AGDS8G2AQ":90},{"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":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6MAZPJCKTDC288AGDS8G2AQ","reproducibility-statement",null,"Prepare the reproducibility, transparency and open-science parts of a paper, including data and code availability statements, reproducibility checklists (NeurIPS, ICML, ICLR, ACL Responsible NLP, Nature reporting summaries), research artifact packaging (Zenodo DOI, CITATION.cff, environment lockfiles, seeds), ethics\u002Fbroader-impact statements, CRediT author contributions, competing interests and AI-use disclosures. Use when a venue requires any of these statements or checklists, or when preparing code\u002Fdata for release alongside a paper.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Freproducibility-statement\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"reproducibility statement","reproducibility","when","writing","open science","for","availability","doi","impact","transparency","runtime","artifact","packaging","environment","ethics","open","data","reporting","release","code","author contributions","nlp","2026-11-10 10:12:30",false,"---\nname: reproducibility-statement\ndescription: Prepare the reproducibility, transparency and open-science parts of a paper, including data and code availability statements, reproducibility checklists (NeurIPS, ICML, ICLR, ACL Responsible NLP, Nature reporting summaries), research artifact packaging (Zenodo DOI, CITATION.cff, environment lockfiles, seeds), ethics\u002Fbroader-impact statements, CRediT author contributions, competing interests and AI-use disclosures. Use when a venue requires any of these statements or checklists, or when preparing code\u002Fdata for release alongside a paper.\nlicense: MIT\ncompatibility: No runtime dependencies.\nmetadata:\n  version: \"1.0\"\n  category: research-writing\n  maintainer: Kalaris Labs\n  author: Kalaris Labs (Sayan Chowdhury)\n  tags: reproducibility, data availability, code availability, open science, FAIR, checklist, CRediT, Zenodo, ethics statement\n---\n\n# Reproducibility and Transparency Statements\n\n## Workflow\n\n1. List every statement and checklist the venue requires (section 1).\n2. Deposit data and code, and obtain persistent identifiers before writing the statements.\n3. Draft each statement with concrete locations, licenses and access conditions.\n4. Verify every link and accession while logged out. Never claim availability that does not exist yet.\n5. Answer checklists honestly, with a justification for each \"No\".\n\nEditors increasingly desk-reject for missing or vague statements, and reviewers\ncheck them. Treat each as a precise, verifiable claim, never boilerplate.\n\n## 1. Find out what the venue requires\n\nCheck the current author guidelines and checklist for the target venue (the `venue-templates`\nand journal-format skills point to them). Common requirements:\n\n| Venue type | Typical requirement |\n|---|---|\n| ML conferences (NeurIPS, ICML, ICLR) | Paper checklist in the PDF (reproducibility, compute, licenses, broader impact, LLM usage), code encouraged |\n| ACL \u002F ARR venues | Responsible NLP checklist, limitations section (mandatory), ethics statement |\n| Nature Portfolio | Data and code availability statements, reporting summary, source data for figures |\n| PLOS | Mandatory data availability statement; data must be available without restriction unless legally exempt |\n| Clinical journals | Trial registration, data sharing statement (ICMJE), reporting guideline checklist (CONSORT, STROBE, ...) |\n| Cell Press | STAR Methods with Key Resources Table and resource availability section |\n\n## 2. Data availability statement\n\nState **where**, **how** and **under what conditions**, with persistent identifiers:\n\n> The processed data supporting the findings are available at Zenodo (https:\u002F\u002Fdoi.org\u002F10.5281\u002Fzenodo.XXXXXXX)\n> under CC BY 4.0. Raw sequencing reads are deposited in the SRA under BioProject PRJNAXXXXXX. Patient-level\n> clinical data cannot be shared publicly due to [regulation]. Requests can be made to [data access\n> committee contact], and access requires a data use agreement.\n\n- Use domain repositories where they exist (GEO\u002FSRA\u002FENA, PDB, PRIDE, OpenNeuro, Dryad, ICPSR,\n  PANGAEA). Otherwise use general ones (Zenodo, Figshare, OSF, Dataverse).\n- \"Available upon reasonable request\" alone is increasingly rejected. Explain the restriction and the access route.\n- Reserve DOIs before submission (Zenodo supports reserved DOIs). Use private reviewer links if the venue allows.\n\n## 3. Code availability and artifact packaging\n\nChecklist for the released repository:\n- [ ] Tagged release matching the paper version, archived to Zenodo (GitHub integration mints a DOI)\n- [ ] `README` with installation, a minimal example, and the exact commands that reproduce each table\u002Ffigure\n- [ ] Pinned environment: `uv.lock`\u002F`requirements.txt` with versions, `environment.yml`, or a container image digest\n- [ ] Random seeds, number of runs, and hardware noted, with variance reported (mean ± std over N seeds)\n- [ ] Data download\u002Fpreprocessing scripts (never ship data you're not licensed to redistribute)\n- [ ] Pretrained weights or checkpoints with checksums, if central to the claims\n- [ ] `LICENSE` (OSI-approved for code; CC BY for text\u002Fdata), and third-party licenses respected\n- [ ] `CITATION.cff` so GitHub shows \"Cite this repository\"\n- [ ] Anonymized for double-blind review (anonymous GitHub mirrors), de-anonymized for camera-ready\n\n## 4. Compute and environmental reporting (ML and simulation)\n\nReport hardware (GPU\u002FCPU type and count), total compute (GPU-hours) for main experiments\n*and* the full project, including hyperparameter search. Report software versions of key frameworks.\n\n## 5. Other statements\n\n- **Author contributions (CRediT)**: map each author to the 14 roles (Conceptualization,\n  Methodology, Software, Validation, Formal analysis, Investigation, Resources, Data curation,\n  Writing – original draft, Writing – review & editing, Visualization, Supervision,\n  Project administration, Funding acquisition).\n- **Competing interests**: declare financial and non-financial interests, or state \"none\".\n- **Funding**: funder names and grant numbers exactly as the funder requires.\n- **Ethics**: IRB\u002Fethics committee name and approval number, consent procedures, animal\n  welfare approvals, dual-use considerations.\n- **Use of AI tools**: follow the venue's policy. Most require disclosure of generative AI use in\n  writing or analysis and forbid listing AI as an author. Describe what was used and how outputs were verified.\n- **Limitations \u002F broader impact**: concrete failure modes, populations or settings where results\n  may not hold, potential misuse, and mitigations.\n\n## Rules\n\n- Every statement must be true at submission time. Verify each link and accession works (logged out, private window).\n- Don't claim \"fully reproducible\" unless someone other than the author has rerun it from the README.\n- Answer checklists honestly. \"No\" with a justification beats an unjustified \"Yes\".\n\n## Related skills\n\n`ml-paper-writing`, `scientific-writing`, `venue-templates`, `datalad`, `lamindb`,\n`research-grants` (data management plans).\n","# Reproducibility and Transparency Statements\n\n## Workflow\n\n1. List every statement and checklist the venue requires (section 1).\n2. Deposit data and code, and obtain persistent identifiers before writing the statements.\n3. Draft each statement with concrete locations, licenses and access conditions.\n4. Verify every link and accession while logged out. Never claim availability that does not exist yet.\n5. Answer checklists honestly, with a justification for each \"No\".\n\nEditors increasingly desk-reject for missing or vague statements, and reviewers\ncheck them. Treat each as a precise, verifiable claim, never boilerplate.\n\n## 1. Find out what the venue requires\n\nCheck the current author guidelines and checklist for the target venue (the `venue-templates`\nand journal-format skills point to them). Common requirements:\n\n| Venue type | Typical requirement |\n|---|---|\n| ML conferences (NeurIPS, ICML, ICLR) | Paper checklist in the PDF (reproducibility, compute, licenses, broader impact, LLM usage), code encouraged |\n| ACL \u002F ARR venues | Responsible NLP checklist, limitations section (mandatory), ethics statement |\n| Nature Portfolio | Data and code availability statements, reporting summary, source data for figures |\n| PLOS | Mandatory data availability statement; data must be available without restriction unless legally exempt |\n| Clinical journals | Trial registration, data sharing statement (ICMJE), reporting guideline checklist (CONSORT, STROBE, ...) |\n| Cell Press | STAR Methods with Key Resources Table and resource availability section |\n\n## 2. Data availability statement\n\nState **where**, **how** and **under what conditions**, with persistent identifiers:\n\n> The processed data supporting the findings are available at Zenodo (https:\u002F\u002Fdoi.org\u002F10.5281\u002Fzenodo.XXXXXXX)\n> under CC BY 4.0. Raw sequencing reads are deposited in the SRA under BioProject PRJNAXXXXXX. Patient-level\n> clinical data cannot be shared publicly due to [regulation]. Requests can be made to [data access\n> committee contact], and access requires a data use agreement.\n\n- Use domain repositories where they exist (GEO\u002FSRA\u002FENA, PDB, PRIDE, OpenNeuro, Dryad, ICPSR,\n  PANGAEA). Otherwise use general ones (Zenodo, Figshare, OSF, Dataverse).\n- \"Available upon reasonable request\" alone is increasingly rejected. Explain the restriction and the access route.\n- Reserve DOIs before submission (Zenodo supports reserved DOIs). Use private reviewer links if the venue allows.\n\n## 3. Code availability and artifact packaging\n\nChecklist for the released repository:\n- [ ] Tagged release matching the paper version, archived to Zenodo (GitHub integration mints a DOI)\n- [ ] `README` with installation, a minimal example, and the exact commands that reproduce each table\u002Ffigure\n- [ ] Pinned environment: `uv.lock`\u002F`requirements.txt` with versions, `environment.yml`, or a container image digest\n- [ ] Random seeds, number of runs, and hardware noted, with variance reported (mean ± std over N seeds)\n- [ ] Data download\u002Fpreprocessing scripts (never ship data you're not licensed to redistribute)\n- [ ] Pretrained weights or checkpoints with checksums, if central to the claims\n- [ ] `LICENSE` (OSI-approved for code; CC BY for text\u002Fdata), and third-party licenses respected\n- [ ] `CITATION.cff` so GitHub shows \"Cite this repository\"\n- [ ] Anonymized for double-blind review (anonymous GitHub mirrors), de-anonymized for camera-ready\n\n## 4. Compute and environmental reporting (ML and simulation)\n\nReport hardware (GPU\u002FCPU type and count), total compute (GPU-hours) for main experiments\n*and* the full project, including hyperparameter search. Report software versions of key frameworks.\n\n## 5. Other statements\n\n- **Author contributions (CRediT)**: map each author to the 14 roles (Conceptualization,\n  Methodology, Software, Validation, Formal analysis, Investigation, Resources, Data curation,\n  Writing – original draft, Writing – review & editing, Visualization, Supervision,\n  Project administration, Funding acquisition).\n- **Competing interests**: declare financial and non-financial interests, or state \"none\".\n- **Funding**: funder names and grant numbers exactly as the funder requires.\n- **Ethics**: IRB\u002Fethics committee name and approval number, consent procedures, animal\n  welfare approvals, dual-use considerations.\n- **Use of AI tools**: follow the venue's policy. Most require disclosure of generative AI use in\n  writing or analysis and forbid listing AI as an author. Describe what was used and how outputs were verified.\n- **Limitations \u002F broader impact**: concrete failure modes, populations or settings where results\n  may not hold, potential misuse, and mitigations.\n\n## Rules\n\n- Every statement must be true at submission time. Verify each link and accession works (logged out, private window).\n- Don't claim \"fully reproducible\" unless someone other than the author has rerun it from the README.\n- Answer checklists honestly. \"No\" with a justification beats an unjustified \"Yes\".\n\n## Related skills\n\n`ml-paper-writing`, `scientific-writing`, `venue-templates`, `datalad`, `lamindb`,\n`research-grants` (data management plans).\n",{"name":5,"license":15,"metadata":59,"description":7,"compatibility":65},{"tags":60,"author":61,"version":62,"category":63,"maintainer":64},"reproducibility, data availability, code availability, open science, FAIR, checklist, CRediT, Zenodo, ethics statement","Kalaris Labs (Sayan Chowdhury)","1.0","research-writing","Kalaris Labs","No runtime dependencies.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Freproducibility-statement",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill reproducibility-statement",{"tool":82,"command":83},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill reproducibility-statement",{"tool":85,"command":86},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill reproducibility-statement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Freproducibility-statement\u002FSKILL.md",true,[],[91,100,108,116,124,132],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":99},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":99},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":99},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":99},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":99},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":99},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]