OpenParable
Skip to content
← Back to skills

Yao Secret

DevOps & Security
yao-secret

Yao Secret is an Agent Skill for devops & security published in the YaoApp/yao repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Secret management expert. ALWAYS invoke this skill when you need to read API keys, tokens, or other secrets configured by the user. Never hardcode credentials — use this skill to retrieve them securely.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/YaoApp/yao/blob/HEAD/tools/skills/yao-secret/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/yao-secret, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Secret Tools

Two tools for accessing user-configured secrets, called via bash.

secret_list

List available secret names and descriptions. Does not return secret values — use secret_read for that.

tai tool secret_list '{}'

No parameters required. Returns secrets configured for the current assistant.

secret_read

Read a secret value by name. Returns the decrypted value for use in scripts.

tai tool secret_read '{"name": "GITHUB_TOKEN"}'
tai tool secret_read '{"name": "AWS_SECRET_KEY"}'
ParameterTypeRequiredDescription
namestringyesSecret key name (e.g. GITHUB_TOKEN, AWS_SECRET_KEY)

Security: Never log, print, or expose the returned secret value in output visible to users.

Typical Workflow

  1. secret_list — discover what secrets are available
  2. secret_read — retrieve a specific secret by name
  3. Use the value in API calls, git auth, etc.

Guidelines

  • Always call secret_list first to check if a required secret exists before reading
  • Never hardcode API keys or tokens — always use secret_read
  • Secret values are decrypted at read time; treat them as sensitive
  • If a secret is not found, prompt the user to configure it in their settings
  • All output is JSON