[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74MSN31NH6T6D8SMEC6KFPV":3,"skill-same:01M74MSN31NH6T6D8SMEC6KFPV":47},{"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},"01M74MSN31NH6T6D8SMEC6KFPV","credentials",null,"Instructions for handling API keys and credentials safely, verifying their presence, and prompting the user to add them if missing using a safe protocol.","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\u002Fcredentials\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: credentials\ndescription: >-\n  Instructions for handling API keys and credentials safely, verifying their\n  presence, and prompting the user to add them if missing using a safe protocol.\n---\n\n# Safe Credentials Protocol\n\nMany skills require API keys or other credentials to function or to access\nhigher rate limits. This skill defines the standard safe credentials protocol\nfor verifying and prompting for these credentials without leaking sensitive keys\ninto the agent context or the conversation history.\n\n## Safe Verification (No Leaks)\n\nAs soon as a skill that requires a credential or API key looks relevant to the\nuser's request, you **MUST** immediately verify if the credential is present in\nthe `.env` file (typically located in your home directory `~\u002F.env` or the\nproject root) — **before doing any other work** for that skill.\n\n**CRITICAL**: You must verify the presence of the credential *without* printing\nits value to the terminal or reading it into your context.\n\n### How to verify:\n\nUse `grep` in quiet and suppress-errors mode (`-sq`) to check if the variable is\ndefined in `~\u002F.env`. The `-s` flag ensures the command works cleanly even if\n`~\u002F.env` does not exist yet.\n\n```bash\ngrep -sq \"^CREDENTIAL_NAME=\" ~\u002F.env\n```\n\nReplace `CREDENTIAL_NAME` with the actual credential name required by the\ncalling skill (e.g., `ALPHAGENOME_API_KEY` or `USER_EMAIL`).\n\n-   If the command **succeeds** (exit code 0), the credential is present. You\n    can proceed.\n-   If the command **fails** (any non-zero exit code — whether the credential is\n    missing or the `.env` file does not exist yet), the credential is missing.\n    You **MUST IMMEDIATELY** stop and prompt the user to add it using the\n    instructions in\n    [Prompting the User to Add Credentials](#prompting-the-user-to-add-credentials)\n    before attempting to run any scripts or tools. Do not conclude the turn by\n    simply stating that the key is missing.\n\n> [!CRITICAL] If verification fails (any non-zero exit code), you **MUST NOT**\n> attempt to execute any tools or scripts from the calling skill, nor should you\n> conclude the turn by simply reporting the missing key. You **MUST\n> IMMEDIATELY** generate the appropriate terminal command from the templates\n> below and prompt the user to run it. The template command will create the\n> `.env` file if it does not already exist.\n\n**NEVER** run `cat ~\u002F.env`, `grep \"VAR\" ~\u002F.env` (without `-q`), `echo $VAR`, or\n`printenv` to check for credentials.\n\n## Prompting the User to Add Credentials\n\nIf a credential is missing, do **NOT** ask the user to paste it into the chat.\nThis would leak the value into the agent's context and the conversation history.\n\nInstead, you **MUST** generate a specific command for the user to run in their\nterminal by replacing the placeholders in one of the templates below.\n\n**CRITICAL**: Before presenting the command to the user, you **MUST** replace:\n\n-   `CREDENTIAL_NAME` with the actual variable name needed (e.g.,\n    `ALPHAGENOME_API_KEY`, `USER_EMAIL`).\n-   `ENV_FILE` with the resolved literal path to the `.env` file (usually\n    `~\u002F.env`).\n\n### Template\n\nAll credentials are treated as sensitive. The `read -s` flag hides the user's\ntyping. You **MUST** inform the user that their typing will be hidden.\n\n**CRITICAL**: When requesting a credential, you **MUST** also provide the user\nwith the appropriate registration link or instructions provided by the calling\nskill so they know how to obtain the value if they do not have one.\n\n```bash\nprintf \"Enter CREDENTIAL_NAME (typing hidden): \" && read -s val && echo && echo \"CREDENTIAL_NAME=$val\" >> \"ENV_FILE\" && echo \"Saved.\"\n```\n\n## Running scripts requiring credentials\n\nAll helper scripts inside the calling skills load these credentials\nautomatically from the `.env` file using `dotenv`.\n\n**You do NOT need to** manually read the keys, export them to the shell\nenvironment, or pass them as CLI arguments, when calling the helper scripts that\nrequire them. As long as you have verified the key is present in `.env` using\nthe safe protocol above, simply run the script directly — the script will load\nthe credential automatically.\n","# Safe Credentials Protocol\n\nMany skills require API keys or other credentials to function or to access\nhigher rate limits. This skill defines the standard safe credentials protocol\nfor verifying and prompting for these credentials without leaking sensitive keys\ninto the agent context or the conversation history.\n\n## Safe Verification (No Leaks)\n\nAs soon as a skill that requires a credential or API key looks relevant to the\nuser's request, you **MUST** immediately verify if the credential is present in\nthe `.env` file (typically located in your home directory `~\u002F.env` or the\nproject root) — **before doing any other work** for that skill.\n\n**CRITICAL**: You must verify the presence of the credential *without* printing\nits value to the terminal or reading it into your context.\n\n### How to verify:\n\nUse `grep` in quiet and suppress-errors mode (`-sq`) to check if the variable is\ndefined in `~\u002F.env`. The `-s` flag ensures the command works cleanly even if\n`~\u002F.env` does not exist yet.\n\n```bash\ngrep -sq \"^CREDENTIAL_NAME=\" ~\u002F.env\n```\n\nReplace `CREDENTIAL_NAME` with the actual credential name required by the\ncalling skill (e.g., `ALPHAGENOME_API_KEY` or `USER_EMAIL`).\n\n-   If the command **succeeds** (exit code 0), the credential is present. You\n    can proceed.\n-   If the command **fails** (any non-zero exit code — whether the credential is\n    missing or the `.env` file does not exist yet), the credential is missing.\n    You **MUST IMMEDIATELY** stop and prompt the user to add it using the\n    instructions in\n    [Prompting the User to Add Credentials](#prompting-the-user-to-add-credentials)\n    before attempting to run any scripts or tools. Do not conclude the turn by\n    simply stating that the key is missing.\n\n> [!CRITICAL] If verification fails (any non-zero exit code), you **MUST NOT**\n> attempt to execute any tools or scripts from the calling skill, nor should you\n> conclude the turn by simply reporting the missing key. You **MUST\n> IMMEDIATELY** generate the appropriate terminal command from the templates\n> below and prompt the user to run it. The template command will create the\n> `.env` file if it does not already exist.\n\n**NEVER** run `cat ~\u002F.env`, `grep \"VAR\" ~\u002F.env` (without `-q`), `echo $VAR`, or\n`printenv` to check for credentials.\n\n## Prompting the User to Add Credentials\n\nIf a credential is missing, do **NOT** ask the user to paste it into the chat.\nThis would leak the value into the agent's context and the conversation history.\n\nInstead, you **MUST** generate a specific command for the user to run in their\nterminal by replacing the placeholders in one of the templates below.\n\n**CRITICAL**: Before presenting the command to the user, you **MUST** replace:\n\n-   `CREDENTIAL_NAME` with the actual variable name needed (e.g.,\n    `ALPHAGENOME_API_KEY`, `USER_EMAIL`).\n-   `ENV_FILE` with the resolved literal path to the `.env` file (usually\n    `~\u002F.env`).\n\n### Template\n\nAll credentials are treated as sensitive. The `read -s` flag hides the user's\ntyping. You **MUST** inform the user that their typing will be hidden.\n\n**CRITICAL**: When requesting a credential, you **MUST** also provide the user\nwith the appropriate registration link or instructions provided by the calling\nskill so they know how to obtain the value if they do not have one.\n\n```bash\nprintf \"Enter CREDENTIAL_NAME (typing hidden): \" && read -s val && echo && echo \"CREDENTIAL_NAME=$val\" >> \"ENV_FILE\" && echo \"Saved.\"\n```\n\n## Running scripts requiring credentials\n\nAll helper scripts inside the calling skills load these credentials\nautomatically from the `.env` file using `dotenv`.\n\n**You do NOT need to** manually read the keys, export them to the shell\nenvironment, or pass them as CLI arguments, when calling the helper scripts that\nrequire them. As long as you have verified the key is present in `.env` using\nthe safe protocol above, simply run the script directly — the script will load\nthe credential automatically.\n",{"name":5,"description":7},"main","e71245365df78e06cd166602744bf2491f79910e","research-skills-hub\u002Fscience-skills\u002Fcredentials",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 credentials",{"tool":39,"command":40},"bunx","bunx skills add pengqianhan\u002FAI-Human-Research-OS --skill credentials",{"tool":42,"command":43},"pnpm","pnpm dlx skills add pengqianhan\u002FAI-Human-Research-OS --skill credentials","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpengqianhan\u002FAI-Human-Research-OS\u002Fblob\u002Fmain\u002Fresearch-skills-hub\u002Fscience-skills\u002Fcredentials\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]