القائمة
Store and retrieve key-value secrets — encrypted secret store for API keys and env vars. Do NOT use for website passwords (use ravi-passwords) or reading messages (use ravi-inbox).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reply to the email you were just dispatched to handle. Use this skill whenever you are running under the ravix daemon (you'll see email headers `From:`, `To:`, `Subject:`, `Message-ID:` in your initial input) and the user has asked you to respond to that email. Do NOT use for composing new outbound emails — this is reply-only.
Manage contacts associated with your identity — list, search, create, update, and delete. Use ravi-contacts to resolve a person's name to their email or phone before sending (e.g. "email Alice" or "text Bob" → search contacts first). Do NOT use for website credentials (use ravi-passwords) or API keys (use ravi-secrets).
Send, compose, reply, reply-all, or forward emails with HTML formatting and attachments. Do NOT use for reading incoming email (use ravi-inbox) or for credentials (use ravi-passwords or ravi-secrets).
Get your agent identity (email, phone, owner name) and manage identities. Do NOT use for reading messages (use ravi-inbox), sending email (use ravi-email-send), or credentials (use ravi-passwords or ravi-secrets).
Read incoming SMS or email messages — verification codes, verification links, incoming mail. Do NOT use for sending email (use ravi-email-send) or managing credentials (use ravi-passwords or ravi-secrets).
Sign up for and log into services using your Ravi identity — handles onboarding, forms, verification codes read from SMS/email, and credential storage. Do NOT use for standalone inbox reading (use ravi-inbox) or email sending (use ravi-email-send).
| name | ravi-secrets |
| description | Store and retrieve key-value secrets — encrypted secret store for API keys and env vars. Do NOT use for website passwords (use ravi-passwords) or reading messages (use ravi-inbox). |
Store and retrieve key-value secrets (API keys, environment variables, tokens). All values are encrypted. Use descriptive key names for lookup and filtering.
# Store a secret
ravi secrets set OPENAI_API_KEY "sk-abc123..."
# List all secrets
ravi secrets list
# Retrieve a secret by key name
ravi secrets get OPENAI_API_KEY
# Delete a secret by UUID
ravi secrets delete <uuid>
ravi secrets list:
[
{
"uuid": "...",
"identity": 1,
"key": "OPENAI_API_KEY",
"value": "sk-abc123...",
"notes": "",
"created_dt": "2026-02-25T10:30:00Z",
"updated_dt": "2026-02-25T10:30:00Z"
}
]
ravi secrets get OPENAI_API_KEY:
{
"uuid": "...",
"identity": 1,
"key": "OPENAI_API_KEY",
"value": "sk-abc123...",
"notes": "",
"created_dt": "2026-02-25T10:30:00Z",
"updated_dt": "2026-02-25T10:30:00Z"
}
# Store a key
ravi secrets set OPENAI_API_KEY "sk-abc123..."
# Retrieve the key value
API_KEY=$(ravi secrets get OPENAI_API_KEY | jq -r '.value')
# List all available key names
ravi secrets list | jq -r '.[].key'
ravi secrets set ANTHROPIC_API_KEY "sk-ant-..."
ravi secrets set GITHUB_TOKEN "ghp_..."
ravi secrets set again (it will upsert). Creating a duplicate key name will return a validation error.test_key becomes TEST_KEY). Keys must match ^[A-Z][A-Z0-9_]*$ after uppercasing.OPENAI_API_KEY, STRIPE_SECRET_KEY.For complete endpoint details, request/response schemas, and parameters: Secrets