foldseek-structural-searchlisted

## Prerequisites 1. **`uv`**: Read the `uv` skill and follow its Setup instructions to ensure `uv` is installed and on PATH. 2. **User Notification**: If .licenses/foldseek_structural_search_LICENSE.txt does not already exist in the workspace root directory then (1) prominently notify the user to check the terms at https://search.foldseek.com/search and https://github.com/steineggerlab/foldseek, then (2) create the file recording the notification text and timestamp. ## Goal Submit a user-provided 3D protein structure file (`.cif`, `.mmcif`, or `.pdb`) to the Foldseek web server API to find structurally similar proteins. Report the top structural hits, interpret key alignment metrics, summarize the inferred protein functions, save the Markdown-formatted table to a `.md` file, and save the full detailed results to a local JSON file. ## Core Rules - **File Requirement**: This tool absolutely cannot search by sequence, name, or accession ID. It strictly requires a `.pdb`, `.cif`, or `.mmcif` file path. - **Strict Validation**: Never bypass the input validation or the database allowlist check. - **Do Not Parse the JSON**: Rely entirely on the generated `.md` file for your immediate summary. The JSON is saved purely for subsequent, specialized tool use. - **No Raw Parsing**: Do not attempt to parse or read the raw 3D coordinates yourself; always pass the file to the script. - **Notification**: If this skill is used, ensur