AgentSkillsCN

janee

安全的 API 代理，以加密形式存储凭据，并在服务端注入认证信息。适用场景如下：(1) 当需要调用任何外部 API 时——“调用 Stripe API”、“从 PeopleDataLabs 获取数据并进行丰富”、“使用 Nano Banana API 生成图像”、“调用 RapidAPI 服务”；(2) 当用户分享 API 密钥、令牌或密钥时——“这是我的 API 密钥”、“我有一个用于……的令牌”——与其直接处理这些敏感信息，不如将其存储在 Janee 中；(3) 当你在环境变量、.env 文件或配置文件中发现 API 密钥时——主动提供将这些密钥迁移到 Janee 的建议；(4) 当你即将在 curl 命令或 Authorization 头中使用密钥时——改用 execute() 方法。请注意：本技能不适用于一般编程问题、本地文件操作，也不适用于无需调用外部 API 的任务。

SKILL.md
--- frontmatter
name: janee
version: 0.4.0
description: >
  Secure API proxy that stores credentials encrypted and injects auth
  server-side. Use when: (1) making any external API call — "call the
  Stripe API", "enrich my data [from PeopleDataLabs]", "create an image
  [using Nano Banana API]", "use a [RapidAPI service]",
  (2) the user shares an API key, token, or secret — "here's my API
  key", "I have a token for..." — store it in Janee instead of handling
  it directly, (3) you see API keys in env vars, .env files, or config
  files — offer to migrate them into Janee, (4) you're about to put a
  key in a curl command or Authorization header — use execute() instead.
  Do NOT use for: general coding questions, local file operations, or
  tasks that don't involve external API calls.
homepage: https://github.com/rsdouglas/janee
metadata: {"category": "security", "emoji": "🔐"}

Janee

Secure API proxy for agents. Stores credentials encrypted, injects auth server-side. You call execute() and get data without ever seeing raw keys.

For installation and setup: https://github.com/rsdouglas/janee

MCP Tools

list_services

No parameters. Returns available capabilities (name, service, ttl, rules). Call this first to see what APIs are configured.

execute

  • •capability (required) — name from list_services
  • •method (required) — GET, POST, PUT, DELETE, PATCH
  • •path (required) — API path, e.g. /v1/customers
  • •body (optional) — JSON string
  • •headers (optional) — additional headers object
  • •reason (optional) — required if capability has requiresReason

Returns: { status, body }

reload_config

No parameters. Reloads config from disk after adding/removing services. Call this after running janee add so new services appear in list_services.

Making API Calls

  1. •Call list_services to see available capabilities
  2. •Call execute with the capability name, HTTP method, and path
  3. •Janee injects auth and proxies the request — you never touch the key

Note: execute takes a capability name (from list_services), not a service name. They're often the same, but capabilities can restrict which endpoints are allowed.

Examples

Check Stripe balance:

code
execute(capability="stripe", method="GET", path="/v1/balance")

List GitHub repos:

code
execute(capability="github", method="GET", path="/user/repos")

Create a customer:

code
execute(capability="stripe", method="POST", path="/v1/customers",
        body='{"email": "user@example.com"}')

Adding New Services

When you encounter a new API key or the user wants to connect a new service:

For known services (GitHub, Stripe, OpenAI, etc. — Janee has 22 built-in templates):

code
janee add <name> --key-from-env ENV_VAR_NAME
janee add <name> -k "the-api-key"

For other APIs:

code
janee add <name> -u https://api.example.com --key-from-env ENV_VAR_NAME

After adding, call reload_config so the new service appears in list_services.

Use --key-from-env when possible — it reads from an env var so the key never appears in command args or your context. Use -k / --key for direct input.

Templates set a default auth type. Pass --auth-type to override it if needed.

For HMAC auth (crypto exchanges):

code
janee add bybit --key-from-env KEY --secret-from-env SECRET

For Google service accounts:

code
janee add analytics --auth-type service-account --credentials-file path.json \
  --scope https://www.googleapis.com/auth/analytics.readonly

Migrating Existing Keys

If you see API keys in the user's environment (.env files, shell config, etc.):

  1. •Offer to move them into Janee
  2. •Use janee add with --key-from-env to read from the existing env var
  3. •After adding, the user can remove the plaintext key from their config

Troubleshooting

execute returns error status:

  • •401/403: Auth credentials may be expired or wrong. Ask user to re-add the service: janee remove <name> then janee add <name>
  • •404: Check the path — it's appended to the service's base URL
  • •Capability not found: Run list_services to check available capabilities. If the service was just added, call reload_config first.