executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
model-export-evaluationOperate DeepFilterNet ONNX export, exported-artifact validation, model inspection, and objective/DNSMOS evaluation workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to export a DeepFilterNet model to ONNX, inspect a model summary, validate a completed export directory, or run objective speech-enhancement evaluation such as VoiceBank-DEMAND, DNS2020, or DNSMOS.
deepFilter/deep-filter-py usage, use python-enhancement.Before acting, identify:
config.ini.If these facts are missing, ask for them or stop with the smallest explicit prerequisite list. Do not silently download models, benchmark datasets, or DNSMOS assets unless the user has allowed network access for this task.
From this sub-skill directory:
python scripts/check_export_artifacts.py /path/to/export-dir
python scripts/check_export_artifacts.py /path/to/export-dir --check-npz
Use the first command for the deployable ONNX/config/version core. Use --check-npz when the debug/reference NPZ files should also be present and readable.
python -m df.scripts.export --model-base-dir /path/to/model-dir --epoch best /path/to/export-dir
Add --no-check only when ONNX Runtime parity checking is intentionally skipped. Add --simplify only when onnxsim is installed and simplification is desired. See the reference before changing --opset.
python -m df.scripts.model_summary --model-base-dir /path/to/model-dir --type table
python -m df.scripts.model_summary --model-base-dir /path/to/model-dir --type torch
Use summaries to confirm that the intended checkpoint/model family loaded. If model loading fails, route to python-enhancement before continuing here.
Use benchmark scripts only after the dataset layout and optional metric dependencies are present. VoiceBank-DEMAND and DNS2020 use paired clean/noisy references; DNSMOS uses noisy/enhanced clips and may require local ONNX downloads or API credentials. Command shapes and skip conditions are in references/export-and-evaluation.md.
Stop and report rather than guessing when:
config.ini, version.txt, enc.onnx, erb_dec.onnx, or df_dec.onnx is missing from an export intended for deployment.--check-npz validation fails for generated *_input.npz or *_output.npz files.onnx, onnxruntime, MonkeyType, or onnxsim is missing for a requested export/check/simplify mode.DNS_AUTH_KEY/--api-key, but those are unavailable or unauthorized.