[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CV73ZHRTG710ZEKSCX4TAW":3,"skill-same:01M7CV73ZHRTG710ZEKSCX4TAW":62},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CV73ZHRTG710ZEKSCX4TAW","blind-review-sanitizer",null,"Use blind-review-sanitizer for academic writing workflows that need structured anonymization, explicit assumptions, and clear output boundaries for double-blind submission.","mrsonord2240\u002Fopenscience-specialists","mrsonord2240","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76487430?v=4","01M7CTEM40S43GSJZ9A3YCCXZK","Samuel Nord","01M7CTEM4K69JD1GBYNHVJ9ZP4",2,"MIT","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Fmanuscript-revision-specialist\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fblind-review-sanitizer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blind-review-sanitizer\ndescription: Use blind-review-sanitizer for academic writing workflows that need structured anonymization, explicit assumptions, and clear output boundaries for double-blind submission.\nlicense: MIT\nauthor: AIPOCH\n---\n> **Source**: [https:\u002F\u002Fgithub.com\u002Faipoch\u002Fmedical-research-skills](https:\u002F\u002Fgithub.com\u002Faipoch\u002Fmedical-research-skills)\n\n# Blind Review Sanitizer\n\nStructured manuscript anonymization for double-blind peer review.\n\n## Quick Check\n\nUse this command to verify that the packaged script entry point can be parsed before deeper execution.\n\n```bash\npython -m py_compile scripts\u002Fmain.py\n```\n\n## Audit-Ready Commands\n\nUse these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.\n\n```bash\npython -m py_compile scripts\u002Fmain.py\npython scripts\u002Fmain.py --help\n```\n\n## When to Use\n\n- Use this skill when the task needs removal or review of author-identifying content in manuscripts prepared for double-blind submission.\n- Use this skill for academic writing tasks that require explicit assumptions, bounded scope, and a reproducible output format.\n- Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.\n\n## Workflow\n\n1. Confirm the submission target, source file type, anonymization strictness, and whether acknowledgments should be preserved.\n2. Check whether the provided material is a supported file format and whether author names or known identifiers are available.\n3. Use the packaged script for supported files; otherwise produce a manual anonymization checklist without claiming full sanitization.\n4. Return the sanitized artifact or a verification plan that separates changes made, remaining risks, and manual review points.\n5. If the request lacks a file path or enough identifiers, stop and request the minimum missing input.\n\n## Use Cases\n\n- Blind a manuscript before conference submission\n- Review acknowledgments and self-citations for deanonymization risk\n- Produce a manual anonymity checklist when automated processing is not possible\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `--input`, `-i` | string | Yes | - | Input manuscript file path (`.docx`, `.md`, `.txt`) |\n| `--output`, `-o` | string | No | auto-generated | Output path with blinded suffix when omitted |\n| `--authors` | string | No | - | Comma-separated author names for stronger detection |\n| `--keep-acknowledgments` | flag | No | false | Preserve acknowledgment section |\n| `--highlight-self-cites` | flag | No | false | Highlight self-citations without replacement |\n\n## Returns\n\n- Sanitized manuscript file for supported formats\n- Summary of removed identifiers when available\n- Explicit note when manual verification is still required\n\n## Example\n\n`python scripts\u002Fmain.py --input manuscript.md --authors \"Alice Chen,Bob Smith\"`\n\n## Risk Assessment\n\n| Risk Indicator | Assessment | Level |\n|----------------|------------|-------|\n| Code Execution | Local Python script execution only | Medium |\n| Network Access | No external API calls | Low |\n| File System Access | Reads manuscript files and writes blinded output | Medium |\n| Instruction Tampering | Standard prompt-guided workflow | Low |\n| Data Exposure | Sensitive manuscript content remains local to workspace | Medium |\n\n## Security Checklist\n\n- [ ] No hardcoded credentials or API keys\n- [ ] No unauthorized file system access (`..\u002F`)\n- [ ] Sensitive manuscript content stays within approved workspace\n- [ ] Input file paths validated before processing\n- [ ] Output file path reviewed before overwrite\n- [ ] Error messages do not fabricate successful sanitization\n- [ ] Manual review required before submission\n- [ ] Metadata cleanup handled separately when needed\n\n## Prerequisites\n\nOptional dependency: `python-docx` is required only for `.docx` processing.\n\n## Evaluation Criteria\n\n### Success Metrics\n- [ ] Script path parses successfully\n- [ ] Help output documents supported options\n- [ ] Sanitization stays within double-blind preparation scope\n- [ ] Missing file or missing identifiers trigger bounded fallback\n\n### Test Cases\n1. **Basic Functionality**: Help output and script parse succeed\n2. **Edge Case**: Missing file path triggers explicit stop condition\n3. **Output Quality**: Remaining anonymity risks are called out clearly\n\n## Lifecycle Status\n\n- **Current Stage**: Draft\n- **Next Review Date**: 2026-03-20\n- **Known Issues**: File metadata and embedded image review still require manual checks\n- **Planned Improvements**:\n  - Safer sample-file smoke test for richer audit coverage\n  - More explicit metadata cleanup guidance\n\n## Output Requirements\n\nEvery final response should make these items explicit when they are relevant:\n\n- Objective or requested deliverable\n- Inputs used and assumptions introduced\n- Workflow or decision path\n- Core result, recommendation, or artifact\n- Constraints, risks, caveats, or validation needs\n- Unresolved items and next-step checks\n\n## Error Handling\n\n- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.\n- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.\n- If `scripts\u002Fmain.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.\n- Do not fabricate files, citations, data, search results, or execution outcomes.\n\n## Input Validation\n\nThis skill accepts requests that match the documented purpose of `blind-review-sanitizer` and include enough context to complete the workflow safely.\n\nDo not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:\n\n> `blind-review-sanitizer` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.\n\n## References\n\n- [references\u002Faudit-reference.md](references\u002Faudit-reference.md) - Supported scope, audit commands, and fallback boundaries\n\n## Response Template\n\nUse the following fixed structure for non-trivial requests:\n\n1. Objective\n2. Inputs Received\n3. Assumptions\n4. Workflow\n5. Deliverable\n6. Risks and Limits\n7. Next Checks\n\nIf the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.\n\n## When Not to Use\n\n- Do not proceed when required input files, identifiers, parameters, or context are missing — ask the user to provide them first.\n- Do not assume capabilities beyond this skill's declared scope when the user requests external operations or inferences.\n- Do not proceed without user confirmation when overwriting existing results, executing high-cost batch operations, or expanding task scope.\n\n## Required Inputs\n\n| Field | Required | Format\u002FSource | Example | If Missing |\n|---|---|---|---|---|\n| User task description | Yes | Text | Research question, writing goal, analysis objective | Stop and ask user to provide |\n| Primary input material | Depends on task | Text, file path, ID, table, or literature | PMID, PDF, CSV, DOCX, keywords, etc. | Specify which material type is missing |\n| Output preference | No | Text | Language, format, target journal, template | Use skill default format |\n\n## Output Contract\n\n- Primary output: Structured result or target file aligned with this skill's objective.\n- Optional output: Intermediate check notes, issue list, supplementary suggestions, or generated file paths.\n- Format requirement: Unless the user specifies otherwise, prefer stable, reviewable Markdown or JSON; if the skill's bundled script requires a fixed format, use that format.\n- If partially complete: Must explicitly mark as PARTIAL and state which steps are completed and which remain.\n\n## Failure Handling\n\n- Missing critical input: Explicitly state which fields, files, or identifiers are missing and pause.\n- Script, template, or resource execution failure: Report the failing step, likely cause, and recovery suggestions — do not silently degrade.\n- Partial completion only: Return the verified portion first, then list remaining blockers and suggested next steps.\n\n## User Checkpoints\n\n- Before executing batch processing, overwriting files, long-running searches, or multi-stage generation, confirm scope and output format with the user.\n- Before proceeding when a key judgment is ambiguous, evidence is insufficient, or the workflow is entering the next stage, confirm with the user.\n\n## Quick Validation\n\n- Check that key scripts, templates, or reference file paths this skill depends on exist.\n- Check that the final output contains the core fields, sections, or files specified for this task.\n- Check that results clearly mark assumptions, limitations, and incomplete items.\n","> **Source**: [https:\u002F\u002Fgithub.com\u002Faipoch\u002Fmedical-research-skills](https:\u002F\u002Fgithub.com\u002Faipoch\u002Fmedical-research-skills)\n\n# Blind Review Sanitizer\n\nStructured manuscript anonymization for double-blind peer review.\n\n## Quick Check\n\nUse this command to verify that the packaged script entry point can be parsed before deeper execution.\n\n```bash\npython -m py_compile scripts\u002Fmain.py\n```\n\n## Audit-Ready Commands\n\nUse these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.\n\n```bash\npython -m py_compile scripts\u002Fmain.py\npython scripts\u002Fmain.py --help\n```\n\n## When to Use\n\n- Use this skill when the task needs removal or review of author-identifying content in manuscripts prepared for double-blind submission.\n- Use this skill for academic writing tasks that require explicit assumptions, bounded scope, and a reproducible output format.\n- Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.\n\n## Workflow\n\n1. Confirm the submission target, source file type, anonymization strictness, and whether acknowledgments should be preserved.\n2. Check whether the provided material is a supported file format and whether author names or known identifiers are available.\n3. Use the packaged script for supported files; otherwise produce a manual anonymization checklist without claiming full sanitization.\n4. Return the sanitized artifact or a verification plan that separates changes made, remaining risks, and manual review points.\n5. If the request lacks a file path or enough identifiers, stop and request the minimum missing input.\n\n## Use Cases\n\n- Blind a manuscript before conference submission\n- Review acknowledgments and self-citations for deanonymization risk\n- Produce a manual anonymity checklist when automated processing is not possible\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `--input`, `-i` | string | Yes | - | Input manuscript file path (`.docx`, `.md`, `.txt`) |\n| `--output`, `-o` | string | No | auto-generated | Output path with blinded suffix when omitted |\n| `--authors` | string | No | - | Comma-separated author names for stronger detection |\n| `--keep-acknowledgments` | flag | No | false | Preserve acknowledgment section |\n| `--highlight-self-cites` | flag | No | false | Highlight self-citations without replacement |\n\n## Returns\n\n- Sanitized manuscript file for supported formats\n- Summary of removed identifiers when available\n- Explicit note when manual verification is still required\n\n## Example\n\n`python scripts\u002Fmain.py --input manuscript.md --authors \"Alice Chen,Bob Smith\"`\n\n## Risk Assessment\n\n| Risk Indicator | Assessment | Level |\n|----------------|------------|-------|\n| Code Execution | Local Python script execution only | Medium |\n| Network Access | No external API calls | Low |\n| File System Access | Reads manuscript files and writes blinded output | Medium |\n| Instruction Tampering | Standard prompt-guided workflow | Low |\n| Data Exposure | Sensitive manuscript content remains local to workspace | Medium |\n\n## Security Checklist\n\n- [ ] No hardcoded credentials or API keys\n- [ ] No unauthorized file system access (`..\u002F`)\n- [ ] Sensitive manuscript content stays within approved workspace\n- [ ] Input file paths validated before processing\n- [ ] Output file path reviewed before overwrite\n- [ ] Error messages do not fabricate successful sanitization\n- [ ] Manual review required before submission\n- [ ] Metadata cleanup handled separately when needed\n\n## Prerequisites\n\nOptional dependency: `python-docx` is required only for `.docx` processing.\n\n## Evaluation Criteria\n\n### Success Metrics\n- [ ] Script path parses successfully\n- [ ] Help output documents supported options\n- [ ] Sanitization stays within double-blind preparation scope\n- [ ] Missing file or missing identifiers trigger bounded fallback\n\n### Test Cases\n1. **Basic Functionality**: Help output and script parse succeed\n2. **Edge Case**: Missing file path triggers explicit stop condition\n3. **Output Quality**: Remaining anonymity risks are called out clearly\n\n## Lifecycle Status\n\n- **Current Stage**: Draft\n- **Next Review Date**: 2026-03-20\n- **Known Issues**: File metadata and embedded image review still require manual checks\n- **Planned Improvements**:\n  - Safer sample-file smoke test for richer audit coverage\n  - More explicit metadata cleanup guidance\n\n## Output Requirements\n\nEvery final response should make these items explicit when they are relevant:\n\n- Objective or requested deliverable\n- Inputs used and assumptions introduced\n- Workflow or decision path\n- Core result, recommendation, or artifact\n- Constraints, risks, caveats, or validation needs\n- Unresolved items and next-step checks\n\n## Error Handling\n\n- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.\n- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.\n- If `scripts\u002Fmain.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.\n- Do not fabricate files, citations, data, search results, or execution outcomes.\n\n## Input Validation\n\nThis skill accepts requests that match the documented purpose of `blind-review-sanitizer` and include enough context to complete the workflow safely.\n\nDo not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:\n\n> `blind-review-sanitizer` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.\n\n## References\n\n- [references\u002Faudit-reference.md](references\u002Faudit-reference.md) - Supported scope, audit commands, and fallback boundaries\n\n## Response Template\n\nUse the following fixed structure for non-trivial requests:\n\n1. Objective\n2. Inputs Received\n3. Assumptions\n4. Workflow\n5. Deliverable\n6. Risks and Limits\n7. Next Checks\n\nIf the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.\n\n## When Not to Use\n\n- Do not proceed when required input files, identifiers, parameters, or context are missing — ask the user to provide them first.\n- Do not assume capabilities beyond this skill's declared scope when the user requests external operations or inferences.\n- Do not proceed without user confirmation when overwriting existing results, executing high-cost batch operations, or expanding task scope.\n\n## Required Inputs\n\n| Field | Required | Format\u002FSource | Example | If Missing |\n|---|---|---|---|---|\n| User task description | Yes | Text | Research question, writing goal, analysis objective | Stop and ask user to provide |\n| Primary input material | Depends on task | Text, file path, ID, table, or literature | PMID, PDF, CSV, DOCX, keywords, etc. | Specify which material type is missing |\n| Output preference | No | Text | Language, format, target journal, template | Use skill default format |\n\n## Output Contract\n\n- Primary output: Structured result or target file aligned with this skill's objective.\n- Optional output: Intermediate check notes, issue list, supplementary suggestions, or generated file paths.\n- Format requirement: Unless the user specifies otherwise, prefer stable, reviewable Markdown or JSON; if the skill's bundled script requires a fixed format, use that format.\n- If partially complete: Must explicitly mark as PARTIAL and state which steps are completed and which remain.\n\n## Failure Handling\n\n- Missing critical input: Explicitly state which fields, files, or identifiers are missing and pause.\n- Script, template, or resource execution failure: Report the failing step, likely cause, and recovery suggestions — do not silently degrade.\n- Partial completion only: Return the verified portion first, then list remaining blockers and suggested next steps.\n\n## User Checkpoints\n\n- Before executing batch processing, overwriting files, long-running searches, or multi-stage generation, confirm scope and output format with the user.\n- Before proceeding when a key judgment is ambiguous, evidence is insufficient, or the workflow is entering the next stage, confirm with the user.\n\n## Quick Validation\n\n- Check that key scripts, templates, or reference file paths this skill depends on exist.\n- Check that the final output contains the core fields, sections, or files specified for this task.\n- Check that results clearly mark assumptions, limitations, and incomplete items.\n",{"name":5,"author":24,"license":15,"description":7},"AIPOCH","main","e0956dc9606356ab78468936b502e55a365282e2","specialists\u002Fmanuscript-revision-specialist\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fblind-review-sanitizer",0,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists","https:\u002F\u002Fgithub.com\u002Fmrsonord2240","2026-10-12 03:19:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mrsonord2240\u002Fopenscience-specialists --skill blind-review-sanitizer",{"tool":38,"command":39},"bunx","bunx skills add mrsonord2240\u002Fopenscience-specialists --skill blind-review-sanitizer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mrsonord2240\u002Fopenscience-specialists --skill blind-review-sanitizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Fmanuscript-revision-specialist\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fblind-review-sanitizer\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"POLISH_CHANGELOG.md","REFERENCE","参考文档",617,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Fmanuscript-revision-specialist\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fblind-review-sanitizer\u002FPOLISH_CHANGELOG.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Faudit-reference.md",1041,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Fmanuscript-revision-specialist\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fblind-review-sanitizer\u002Freferences\u002Faudit-reference.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fmain.py","SCRIPT","脚本",13358,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Fmanuscript-revision-specialist\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fblind-review-sanitizer\u002Fscripts\u002Fmain.py",[63,71,78,85,92,99],{"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},"01M7CW36A6QAGWFE2C008M1XPG","bio-workflows-metabolomics-pipeline","Orchestrates the untargeted LC-MS metabolomics pipeline end-to-end (xcms 4.x feature extraction, QC\u002Fdrift\u002Fnormalization, confidence-stratified annotation, permutation-validated statistics, background-aware pathway mapping), naming what each stage decides and where it silently fails. Use when running a full LC-MS metabolomics study from raw mzML to enriched pathways and needing the honest handoffs between stages. Each stage defers to its component skill for parameters and traps; for stable-isotope flux (a separate branch, not this untargeted flow) see metabolomics\u002Fisotope-tracing.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-workflows-metabolomics-pipeline\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":67,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CW2Y18623NA2S1Y30FRQW1","bio-metabolomics-xcms-preprocessing","Programmatic untargeted LC-MS feature extraction in R with the modern xcms 4.x MsExperiment\u002FXcmsExperiment API, taking raw mzML to a feature table via CentWave peak detection, retention-time alignment, peak-density correspondence, gap-filling, CAMERA redundancy collapse, and built-in QC feature filtering. Use when converting centroided LC-MS runs into a features-by-samples matrix and deciding centWave\u002Fgrouping\u002Falignment parameters. For drift correction and QC\u002FCV filtering execution see metabolomics\u002Fnormalization-qc; for metabolite identification see metabolomics\u002Fmetabolite-annotation; for the MS-DIAL GUI alternative with MS2Dec deconvolution see metabolomics\u002Fmsdial-preprocessing; for downstream statistics see metabolomics\u002Fstatistical-analysis.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-xcms-preprocessing\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":67,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CW2M364HVWPNQEKE2WP4PP","bio-metabolomics-statistical-analysis","Decision-grade statistical analysis for metabolomics intensity tables. Covers transformation and scaling (Pareto vs unit-variance as a hidden hypothesis), unsupervised structure (PCA\u002FHCA for QC), permutation-validated PLS-DA\u002FOPLS-DA (R2 vs Q2, double CV, VIP as heuristic), univariate testing (Welch\u002FMann-Whitney\u002FANOVA\u002FLMM with covariate adjustment), and dependence-aware multiple testing. Use when testing which metabolites differ, building or validating a discriminant model, choosing a scaling, or correcting many correlated tests. For sample-wise normalization\u002Fdrift correction see metabolomics\u002Fnormalization-qc; for ML classifiers and selection-inside-CV leakage see machine-learning\u002Fbiomarker-discovery and machine-learning\u002Fmodel-validation; for pathway interpretation see metabolomics\u002Fpathway-mapping; for design\u002Fpower\u002Fmultiplicity regime see experimental-design\u002Fmultiple-testing.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-statistical-analysis\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":67,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CW2BCBF851WYE03Z8XPEDQ","bio-metabolomics-pathway-mapping","Maps metabolomics results to biological pathways via over-representation (ORA), metabolite-set enrichment (MSEA\u002FQEA), mummichog\u002FPSEA on raw m\u002Fz peaks, and network-diffusion enrichment (FELLA), with correct background-set construction and honest interpretive ceilings. Use when interpreting differential metabolites or an untargeted LC-MS feature table in pathway context, choosing ORA vs MSEA vs mummichog vs topology, or setting the reference\u002Fbackground set. For annotation confidence levels feeding ORA see metabolomics\u002Fmetabolite-annotation; for gene-set concepts see pathway-analysis\u002Fgo-enrichment and pathway-analysis\u002Fgsea; for joint gene+metabolite pathways see multi-omics-integration\u002Fmofa-integration.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-pathway-mapping\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CW21NSZMCPMF7D9CHJM718","bio-metabolomics-normalization-qc","Designs QC, corrects signal drift, removes batch effects, filters features, normalizes samples, and imputes missing values for untargeted LC-MS\u002FGC-MS metabolomics, framing each step as a measurement model that can create or erase biological signal. Use when processing a peak\u002Ffeature table before statistical analysis, choosing a drift-correction or sample-normalization method, deciding QC RSD vs D-ratio filtering, or handling left-censored missing values. The feature table is produced by metabolomics\u002Fxcms-preprocessing or metabolomics\u002Fmsdial-preprocessing; transformation\u002Fscaling for modeling defers to metabolomics\u002Fstatistical-analysis; cross-study design issues link to experimental-design\u002Fbatch-design.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-normalization-qc\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CW1SWVM0NYHVE6Q7MA3G7R","bio-metabolomics-msdial-preprocessing","Runs the MS-DIAL preprocessing workflow (peak picking, MS2Dec spectral deconvolution, alignment, gap-filling) and imports the alignment-result table into R or Python with honest filtering. Use when preprocessing LC-MS DDA\u002FDIA (SWATH) or GC-MS raw data with MS-DIAL, deciding MS-DIAL vs XCMS, configuring the MSDIALCUI console run, or parsing an MS-DIAL export into a clean feature matrix. For programmatic R peak detection and the feature-table-as-artifact framing see metabolomics\u002Fxcms-preprocessing; for lipid annotation mode see metabolomics\u002Flipidomics; for MSI-level confidence honesty see metabolomics\u002Fmetabolite-annotation; for drift correction and QC see metabolomics\u002Fnormalization-qc.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-msdial-preprocessing\u002FSKILL.md",[],[]]