Instructions for handling API keys and credentials safely, verifying their presence, and prompting the user to add them if missing using a safe protocol.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Many skills require API keys or other credentials to function or to access higher rate limits. This skill defines the standard safe credentials protocol for verifying and prompting for these credentials without leaking sensitive keys into the agent context or the conversation history.
As soon as a skill that requires a credential or API key looks relevant to the
user's request, you MUST immediately verify if the credential is present in
the .env file (typically located in your home directory ~/.env or the
project root) — before doing any other work for that skill.
CRITICAL: You must verify the presence of the credential without printing its value to the terminal or reading it into your context.
Use grep in quiet and suppress-errors mode (-sq) to check if the variable is
defined in ~/.env. The -s flag ensures the command works cleanly even if
~/.env does not exist yet.
grep -sq "^CREDENTIAL_NAME=" ~/.env
Replace CREDENTIAL_NAME with the actual credential name required by the
calling skill (e.g., ALPHAGENOME_API_KEY or USER_EMAIL).
.env file does not exist yet), the credential is missing.
You MUST IMMEDIATELY stop and prompt the user to add it using the
instructions in
Prompting the User to Add Credentials
before attempting to run any scripts or tools. Do not conclude the turn by
simply stating that the key is missing.[!CRITICAL] If verification fails (any non-zero exit code), you MUST NOT attempt to execute any tools or scripts from the calling skill, nor should you conclude the turn by simply reporting the missing key. You MUST IMMEDIATELY generate the appropriate terminal command from the templates below and prompt the user to run it. The template command will create the
.envfile if it does not already exist.
NEVER run cat ~/.env, grep "VAR" ~/.env (without -q), echo $VAR, or
printenv to check for credentials.
If a credential is missing, do NOT ask the user to paste it into the chat. This would leak the value into the agent's context and the conversation history.
Instead, you MUST generate a specific command for the user to run in their terminal by replacing the placeholders in one of the templates below.
CRITICAL: Before presenting the command to the user, you MUST replace:
CREDENTIAL_NAME with the actual variable name needed (e.g.,
ALPHAGENOME_API_KEY, USER_EMAIL).ENV_FILE with the resolved literal path to the .env file (usually
~/.env).All credentials are treated as sensitive. The read -s flag hides the user's
typing. You MUST inform the user that their typing will be hidden.
CRITICAL: When requesting a credential, you MUST also provide the user with the appropriate registration link or instructions provided by the calling skill so they know how to obtain the value if they do not have one.
printf "Enter CREDENTIAL_NAME (typing hidden): " && read -s val && echo && echo "CREDENTIAL_NAME=$val" >> "ENV_FILE" && echo "Saved."
All helper scripts inside the calling skills load these credentials
automatically from the .env file using dotenv.
You do NOT need to manually read the keys, export them to the shell
environment, or pass them as CLI arguments, when calling the helper scripts that
require them. As long as you have verified the key is present in .env using
the safe protocol above, simply run the script directly — the script will load
the credential automatically.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Retrieve and analyze AlphaFold predicted structures for a protein. Use when the user provides a specific UniProt Accession ID and wants structural confidence metrics (pLDDT), domain boundary analysis, or disorder assessment. Do not use if the user only has a protein name, gene name, or amino acid sequence — ask for a UniProt ID first.
日本語の概要は準備中です。原文の説明を表示しています。
Constructs deep-links and URLs for the AlphaGenome Atlas website. Supports generating single-variant exploration links (1-based chr:pos:ref>alt), genomic locus views (1-based closed chr:start-end), candidate summary tables, and AlphaGenome reference vs. alternate predictions. Use whenever visualizing, exploring, charting, or linking genetic variants and genomic loci on the AlphaGenome Atlas, or when asked to inspect, view, or link predictions for a genomic variant.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes genetic variant effects on gene expression (RNA-seq), chromatin accessibility (DNASE), histone marks (ChIP), and transcription factors using the AlphaGenome API. Use when the user asks about non-coding variant effects, pathogenicity, clinical significance, disease associations, functional effects, gene expression changes, splicing disruption, or regulatory effects in promoters and enhancers. Also use for resolving biological terms to tissue/cell-type ontologies (UBERON/CL) or analyzing variants in chr:pos:ref>alt format.
日本語の概要は準備中です。原文の説明を表示しています。
Score, annotate, and analyze the functional impact of genetic variants using AlphaGenome Variant Impact (AVI) scores. Query variants in chr:pos:ref>alt format, annotate VCF/tabular callsets, perform saturation mutagenesis window scans (1-based closed chr:start-end), and extract GENCODE v46 GTF gene/exon/junction coordinates all via the AlphaGenome Atlas API.
日本語の概要は準備中です。原文の説明を表示しています。
Query the ChEMBL database for bioactive molecules, drug targets, bioactivity data, approved drugs, and chemical structures. Use when the user asks about compounds, targets, IC50/Ki values, drug mechanisms, or structure searches.
日本語の概要は準備中です。原文の説明を表示しています。
Query ClinicalTrials.gov via APIv2. Use when you want to search for trials by condition, drug, location, status, or phase; retrieve trial details by NCT ID; check eligibility/inclusion criteria; count trials across conditions or time periods; identify a sponsor's trial portfolio; find recruiting trials for patient matching.
日本語の概要は準備中です。原文の説明を表示しています。