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
output-interpretationExplain and validate AlphaFold 3 output directories, ranking/confidence files, optional embeddings/distograms, compression, and output-oriented troubleshooting.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a user asks what an AlphaFold 3 result directory contains, whether a run produced expected outputs, how to choose a prediction, or why optional output files are missing or compressed.
../input-preparation/.--save_embeddings, --save_distogram, --compress_large_output_files, --force_output_dir, or separate data/inference runs, use ../running-predictions/.../python-apis/.references/output-files.md describes expected job directory layout, sanitized naming, required and optional files, sample/seed subdirectories, and zstandard compression behavior.references/confidence-metrics.md explains ranking_score, pLDDT, PAE, pTM, ipTM, chain and chain-pair metrics, and antibody-antigen interface ranking.references/troubleshooting.md covers missing files, absent embeddings/distograms, low rankings or clashes, compressed large files, output directory collisions, and low-confidence predictions.Run the bundled script on a completed AlphaFold 3 job directory:
python scripts/summarize_outputs.py /path/to/job_output
The script uses only the Python standard library. It reports expected top-level files, seed/sample directories, optional embedding/distogram directories, .npz member names when available, ranking_scores.csv rows, and keys from summary confidence JSON files. It does not import AlphaFold 3 and does not decompress .zst files.
seed-<seed>_sample-<sample> directory per seed/sample prediction, each with a model CIF, full confidences JSON, and summary confidences JSON.<job>_ranking_scores.csv to find the highest ranking_score; the top-level <job>_model.cif and confidence files are copied from that best-ranked sample..cif.zst or _confidences.json.zst files appear, the run used compression for large output files; summary JSON, ranking CSV, terms, embeddings, and distograms remain normally readable.