<< All versions

Skill v1.0.1

LLM-judged scan95/100
fmschulz/omics-skills/bio-workflow-methods-docwriter

1 files

──Details
PublishedSeptember 25, 2026 at 11:00 PM
Content Hashsha256:955e201f61a107da...
Git SHA7a4eb5bace3f
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 3.3 KB)
SKILL.md3.3 KBactive
SKILL.md · 75 lines · 3.3 KB

version: "1.0.1" name: bio-workflow-methods-docwriter description: Generate reproducible Methods from Nextflow, Snakemake, or CWL run artifacts. Use when documenting exact commands, versions, parameters, QC gates, provenance, and outputs.


Bio Workflow Methods Docwriter

Create publication-ready Methods and run documentation from real workflow artifacts.

Instructions

  1. Collect the workflow evidence package (logs, configs, version files).
  2. Build run_manifest.yaml strictly from evidence.
  3. Validate the manifest against the schema.
  4. Draft METHODS.md with a concise workflow summary at the top.
  5. Verify QC gates and reproducibility details are captured.

Resolve the installed skill with:

bash
METHODS_SKILL="${METHODS_SKILL:-$HOME/.agents/skills/bio-workflow-methods-docwriter}"

Quick Reference

TaskAction
Evidence checklistSee reference/evidence-checklist.md
Standards to align withSee reference/standards.md
Manifest schemaschemas/run-manifest.schema.json (LinkML source: schemas/workflow-run-schema.yaml)
Drafting templatesMETHODS.md template, paper-summary YAML
Extract a Nextflow draftuv run "$METHODS_SKILL/scripts/extract_nextflow_run.py" --help
Extract Snakemake evidenceuv run --script "$METHODS_SKILL/scripts/extract_snakemake_run.py" --help
Extract CWL evidenceuv run --script "$METHODS_SKILL/scripts/extract_cwl_run.py" --help
Validate manifestuv run "$METHODS_SKILL/scripts/validate_run_manifest.py" run_manifest.yaml
ExamplesSee examples/

Input Requirements

  • Workflow artifacts (Nextflow/Snakemake/CWL logs and configs)
  • Tool version records or container digests
  • QC reports and output manifests

Output

Quality Gates

  • [ ] No invented commands, versions, or parameters
  • [ ] Every step has inputs, outputs, and versions captured
  • [ ] Commands were sourced from task scripts, not environment-bearing wrappers, and contain no credentials
  • [ ] No NOT CAPTURED, UNKNOWN, or TBD placeholder remains in a required field
  • [ ] Workflow summary appears at top of METHODS.md
  • [ ] The engine-specific extractor output passes validate_run_manifest.py; the fixture-backed Nextflow path proves trace, task script, input, output, version, and final-output evidence end to end.

Examples

Example 1: Validate a manifest

bash
METHODS_SKILL="${METHODS_SKILL:-$HOME/.agents/skills/bio-workflow-methods-docwriter}"
uv run "$METHODS_SKILL/scripts/validate_run_manifest.py" run_manifest.yaml

Troubleshooting

Issue: Missing tool versions in logs Solution: Use NOT CAPTURED only while assembling a draft. The final validator rejects it; recover the version from provenance or report the missing evidence in limitations without claiming a reproducible manifest.

← v1.0.0All versionsv1.0.2 →