[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BVAJF83YYCTT4E3FTCMAN5":3,"skill-same:01M7BVAJF83YYCTT4E3FTCMAN5":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BVAJF83YYCTT4E3FTCMAN5","foldseek-structural-search",null,"Performs 3D structural searches of proteins against various databases (PDB, AlphaFold, CATH, MGnify, etc.) using the Foldseek API. Use ONLY when the user provides a physical 3D coordinate file (.cif, .mmcif, or .pdb) and wants to find structurally similar proteins. Do NOT use if the user only provides a protein sequence, gene name, or UniProt ID.","nguyenhungtran18\u002Fskill-and-tool-tracker","nguyenhungtran18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F297063550?v=4","01M7BV0BFPRRFP84F2ME0FYZ9D","01M7BV0BG83FA5P22NJV0GR0A5",1,"MIT","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Ffoldseek_structural_search\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: foldseek-structural-search\ndescription: >\n    Performs 3D structural searches of proteins against various databases (PDB,\n    AlphaFold, CATH, MGnify, etc.) using the Foldseek API. Use ONLY when the\n    user provides a physical 3D coordinate file (.cif, .mmcif, or .pdb) and\n    wants to find structurally similar proteins. Do NOT use if the user only\n    provides a protein sequence, gene name, or UniProt ID.\n---\n\n## Prerequisites\n\n1.  **`uv`**: Read the `uv` skill and follow its Setup instructions to ensure\n    `uv` is installed and on PATH.\n2.  **User Notification**: If .licenses\u002Ffoldseek_structural_search_LICENSE.txt\n    does not already exist in the workspace root directory then (1) prominently\n    notify the user to check the terms at https:\u002F\u002Fsearch.foldseek.com\u002Fsearch and\n    https:\u002F\u002Fgithub.com\u002Fsteineggerlab\u002Ffoldseek, then (2) create the file\n    recording the notification text and timestamp.\n\n## Goal\n\nSubmit a user-provided 3D protein structure file (`.cif`, `.mmcif`, or `.pdb`)\nto the Foldseek web server API to find structurally similar proteins. Report the\ntop structural hits, interpret key alignment metrics, summarize the inferred\nprotein functions, save the Markdown-formatted table to a `.md` file, and save\nthe full detailed results to a local JSON file.\n\n## Core Rules\n\n-   **File Requirement**: This tool absolutely cannot search by sequence, name,\n    or accession ID. It strictly requires a `.pdb`, `.cif`, or `.mmcif` file\n    path.\n-   **Strict Validation**: Never bypass the input validation or the database\n    allowlist check.\n-   **Do Not Parse the JSON**: Rely entirely on the generated `.md` file for\n    your immediate summary. The JSON is saved purely for subsequent, specialized\n    tool use.\n-   **No Raw Parsing**: Do not attempt to parse or read the raw 3D coordinates\n    yourself; always pass the file to the script.\n-   **Notification**: If this skill is used, ensure this is mentioned in the\n    output.\n\n## Instructions\n\n1.  **Strict Input Validation:** Verify that the user has explicitly provided a\n    valid path to a `.cif`, `.mmcif`, or `.pdb` file in their workspace.\n    *   If the user provided a protein name, an amino acid sequence, or an\n        accession ID (e.g., a UniProt ID) but NO downloaded structure file,\n        **halt immediately**. Do not run the script.\n    *   Inform the user that Foldseek requires a physical 3D coordinate file,\n        and suggest downloading the structure first (e.g., using the AlphaFold\n        fetch tool).\n2.  **Database Validation:** Check if the user requested specific databases to\n    search.\n    *   **Allowed List:** `afdb50`, `afdb-swissprot`, `pdb100`, `BFVD`,\n        `mgnify_esm30`, `cath50`, `gmgcl_id`, `bfmd`, `afdb-proteome`.\n    *   If the user requests a database NOT on this list, **halt immediately**.\n        Do not run the script. Inform the user that the database is unsupported\n        and provide them with the allowed list.\n3.  **Generate File Names:** Generate descriptive output file names for both the\n    JSON data and the Markdown table based on the input file (e.g.,\n    `proteinA_foldseek_results.json` and `proteinA_foldseek_results.md`).\n4.  Execute the python script based on the user's request, redirecting the\n    standard output into your generated `.md` file:\n    *   **Default (No databases specified):** `uv run scripts\u002Fsearch.py\n        \u003Cpath-to-file> -o \u003Cgenerated-filename.json> > \u003Cgenerated-filename.md>`\n    *   **Custom (Valid databases specified):** `uv run scripts\u002Fsearch.py\n        \u003Cpath-to-file> -o \u003Cgenerated-filename.json> --databases \u003Cdb1,db2,db3> >\n        \u003Cgenerated-filename.md>`\n5.  The script will query the databases, save the full JSON payload, and write a\n    Markdown-formatted table to your specified `.md` file.\n6.  **Read the Results:** Open and read the newly generated `.md` file carefully\n    to view the Markdown table.\n7.  **Interpret the Metrics:** Summarize the top 3 to 5 structural matches that\n    have meaningfull annotations for the user. When reporting, assess the match\n    quality using these specific fields:\n    *   **Prob (Probability):** Values approaching 1.0 (100%) indicate extreme\n        confidence that the fold is a true structural homologue.\n    *   **Q-Cov (Query Coverage):** High percentages mean the match covers the\n        majority of the query protein's overall shape, rather than just a small\n        local motif.\n    *   **E-value & Seq Identity:** Use these to provide additional evolutionary\n        context.\n8.  **Perform Functional Analysis:** Analyze the text descriptions embedded\n    within the `Target ID` column for the reported matches.\n    *   Explicitly report the specific protein names\u002Ffunctions of the top\n        structural homologues.\n    *   Provide a synthesized overview summarizing the entire *variety* of\n        different functions, domains, or protein families found across the whole\n        list of homologues (e.g., \"Most hits are portal proteins, but there is\n        also a distinct cluster of viral capsid matches...\").\n9.  Explicitly inform the user of both newly created files (`.json` and `.md`)\n    and their locations so they can be seamlessly used in subsequent analysis\n    steps.\n\n## * If the API returns an error or the file is missing, inform the user clearly\n\nand ask them to verify the file path.\n","## Prerequisites\n\n1.  **`uv`**: Read the `uv` skill and follow its Setup instructions to ensure\n    `uv` is installed and on PATH.\n2.  **User Notification**: If .licenses\u002Ffoldseek_structural_search_LICENSE.txt\n    does not already exist in the workspace root directory then (1) prominently\n    notify the user to check the terms at https:\u002F\u002Fsearch.foldseek.com\u002Fsearch and\n    https:\u002F\u002Fgithub.com\u002Fsteineggerlab\u002Ffoldseek, then (2) create the file\n    recording the notification text and timestamp.\n\n## Goal\n\nSubmit a user-provided 3D protein structure file (`.cif`, `.mmcif`, or `.pdb`)\nto the Foldseek web server API to find structurally similar proteins. Report the\ntop structural hits, interpret key alignment metrics, summarize the inferred\nprotein functions, save the Markdown-formatted table to a `.md` file, and save\nthe full detailed results to a local JSON file.\n\n## Core Rules\n\n-   **File Requirement**: This tool absolutely cannot search by sequence, name,\n    or accession ID. It strictly requires a `.pdb`, `.cif`, or `.mmcif` file\n    path.\n-   **Strict Validation**: Never bypass the input validation or the database\n    allowlist check.\n-   **Do Not Parse the JSON**: Rely entirely on the generated `.md` file for\n    your immediate summary. The JSON is saved purely for subsequent, specialized\n    tool use.\n-   **No Raw Parsing**: Do not attempt to parse or read the raw 3D coordinates\n    yourself; always pass the file to the script.\n-   **Notification**: If this skill is used, ensure this is mentioned in the\n    output.\n\n## Instructions\n\n1.  **Strict Input Validation:** Verify that the user has explicitly provided a\n    valid path to a `.cif`, `.mmcif`, or `.pdb` file in their workspace.\n    *   If the user provided a protein name, an amino acid sequence, or an\n        accession ID (e.g., a UniProt ID) but NO downloaded structure file,\n        **halt immediately**. Do not run the script.\n    *   Inform the user that Foldseek requires a physical 3D coordinate file,\n        and suggest downloading the structure first (e.g., using the AlphaFold\n        fetch tool).\n2.  **Database Validation:** Check if the user requested specific databases to\n    search.\n    *   **Allowed List:** `afdb50`, `afdb-swissprot`, `pdb100`, `BFVD`,\n        `mgnify_esm30`, `cath50`, `gmgcl_id`, `bfmd`, `afdb-proteome`.\n    *   If the user requests a database NOT on this list, **halt immediately**.\n        Do not run the script. Inform the user that the database is unsupported\n        and provide them with the allowed list.\n3.  **Generate File Names:** Generate descriptive output file names for both the\n    JSON data and the Markdown table based on the input file (e.g.,\n    `proteinA_foldseek_results.json` and `proteinA_foldseek_results.md`).\n4.  Execute the python script based on the user's request, redirecting the\n    standard output into your generated `.md` file:\n    *   **Default (No databases specified):** `uv run scripts\u002Fsearch.py\n        \u003Cpath-to-file> -o \u003Cgenerated-filename.json> > \u003Cgenerated-filename.md>`\n    *   **Custom (Valid databases specified):** `uv run scripts\u002Fsearch.py\n        \u003Cpath-to-file> -o \u003Cgenerated-filename.json> --databases \u003Cdb1,db2,db3> >\n        \u003Cgenerated-filename.md>`\n5.  The script will query the databases, save the full JSON payload, and write a\n    Markdown-formatted table to your specified `.md` file.\n6.  **Read the Results:** Open and read the newly generated `.md` file carefully\n    to view the Markdown table.\n7.  **Interpret the Metrics:** Summarize the top 3 to 5 structural matches that\n    have meaningfull annotations for the user. When reporting, assess the match\n    quality using these specific fields:\n    *   **Prob (Probability):** Values approaching 1.0 (100%) indicate extreme\n        confidence that the fold is a true structural homologue.\n    *   **Q-Cov (Query Coverage):** High percentages mean the match covers the\n        majority of the query protein's overall shape, rather than just a small\n        local motif.\n    *   **E-value & Seq Identity:** Use these to provide additional evolutionary\n        context.\n8.  **Perform Functional Analysis:** Analyze the text descriptions embedded\n    within the `Target ID` column for the reported matches.\n    *   Explicitly report the specific protein names\u002Ffunctions of the top\n        structural homologues.\n    *   Provide a synthesized overview summarizing the entire *variety* of\n        different functions, domains, or protein families found across the whole\n        list of homologues (e.g., \"Most hits are portal proteins, but there is\n        also a distinct cluster of viral capsid matches...\").\n9.  Explicitly inform the user of both newly created files (`.json` and `.md`)\n    and their locations so they can be seamlessly used in subsequent analysis\n    steps.\n\n## * If the API returns an error or the file is missing, inform the user clearly\n\nand ask them to verify the file path.\n",{"name":5,"description":7},"main","900ea3c9eb045fd5b0317dc1103777ecf3ea4aeb","skills\u002Ffoldseek_structural_search",0,"https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker","https:\u002F\u002Fnguyenhungtran18.github.io\u002Fskill-and-tool-tracker\u002F","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18","2026-08-31 18:36:09",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill foldseek-structural-search",{"tool":37,"command":38},"bunx","bunx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill foldseek-structural-search",{"tool":40,"command":41},"pnpm","pnpm dlx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill foldseek-structural-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Ffoldseek_structural_search\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcitation.bib","REFERENCE","参考文档",445,"https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Ffoldseek_structural_search\u002Freferences\u002Fcitation.bib",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"scripts\u002Fsearch.py","SCRIPT","脚本",8005,"https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Ffoldseek_structural_search\u002Fscripts\u002Fsearch.py",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7BVP4P83TK60JZ4P8RP9VP7","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fxcode_project_setup\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7BVP01K4CSJJ8G90FT8S2D5","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7BVNY22GXD871GYTSH599F1","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7BVNQWF24RNKA8A4KM2HJ3T","workflow-skill-creator","Distills a completed user workflow or interaction into a reusable agent skill. Use when the user asks to turn their workflow, interaction, or multi-step process into a skill, or when they say \"make this a skill\", \"create a skill from what we just did\", \"package this workflow\" or similar. Do not use for creating skills from scratch without an existing workflow (use a generic skill-creator for that).","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow_skill_creator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7BVNNY67XPCQAQHY3FBKDGC","verify-and-stop","Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fverify-and-stop\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M7BVNKB4Z7SZT85B73ZZ90Y6","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[]]