[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74MT51B4NJMMCMPSE9MSDEJ":3,"skill-same:01M74MT51B4NJMMCMPSE9MSDEJ":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M74MT51B4NJMMCMPSE9MSDEJ","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.","pengqianhan\u002FAI-Human-Research-OS","pengqianhan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4286531?v=4","01M74M3DT9HNZ6HPAK8TX69EX9","PengqianHan","01M74M3DTVSN2GXW0JH2W396FK",3,"MIT","https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Ffoldseek_structural_search\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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","e71245365df78e06cd166602744bf2491f79910e","research-skills-hub\u002Fscience-skills\u002Ffoldseek_structural_search",0,"https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS","https:\u002F\u002Fpengqianhan.github.io\u002FAI-Human-Research-OS\u002F","https:\u002F\u002Fgithub.com\u002Fpengqianhan","Ph.D. candidate of The University of Auckland, New Zealand","2026-11-14 18:08:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add pengqianhan\u002FAI-Human-Research-OS --skill foldseek-structural-search",{"tool":39,"command":40},"bunx","bunx skills add pengqianhan\u002FAI-Human-Research-OS --skill foldseek-structural-search",{"tool":42,"command":43},"pnpm","pnpm dlx skills add pengqianhan\u002FAI-Human-Research-OS --skill foldseek-structural-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Ffoldseek_structural_search\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcitation.bib","REFERENCE","参考文档",445,"https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Ffoldseek_structural_search\u002Freferences\u002Fcitation.bib",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Fsearch.py","SCRIPT","脚本",8005,"https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Ffoldseek_structural_search\u002Fscripts\u002Fsearch.py",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M74MWYTHT498SVMN823896T7","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\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Fworkflow_skill_creator\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74MWWVCFZ8HQS8840F1V1FT","uv","Checks whether the uv Python package manager is installed and installs it if missing. Ensures uv is on PATH. Use when another skill requires uv as a prerequisite.","https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Fuv\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74MWRH5BTSWZ2C5PCTD5FV9","uniprot-database","Access protein metadata, function, taxonomy, and sequences across UniProtKB, UniParc, and UniRef. Use when searching for proteins, mapping identifiers, or retrieving functional annotations and publications. Don't use for sequence alignment, protein folding, or sequence similarity search (use specialized skills for those tasks).","https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Funiprot_database\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M74MWN1D3ER9F1FZPWH8HQC1","unibind-database","Queries the UniBind database for experimentally validated transcription factor (TF) binding sites. Use when retrieving direct TF-DNA interaction datasets, downloading binding site coordinates (BED\u002FFASTA) for local analysis, or listing available datasets by species, cell line, or TF name. Don't use to query specific intervals, locations, genes, motif models or expression data.","https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Funibind_database\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M74MWHHB5QZY3NR2FYA1EK4N","ucsc-conservation-and-tfbs","Fetch Evolutionary Conservation scores (phyloP, phastCons) and Transcription Factor Binding Sites (TFBS) from the UCSC Genome Browser. Use when analyzing whether genomic variants or regions are evolutionarily conserved, functionally important, or bounded by TF regulators across major projects (ENCODE, JASPAR, ReMap).","https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Fucsc_conservation_and_tfbs\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M74MWERYHSY87P21FDMVE6BA","string-database","Query the STRING database for protein-protein interactions (PPIs), functional enrichment, and homology. Use when the user asks about interactions between specific proteins, interaction evidence, confidence scores, protein interaction partners, or pathway enrichments.","https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Fstring_database\u002FSKILL.md",[],[]]