secrets-doctor

Stars13

Forks2

UpdatedApril 14, 2026 at 07:49

Use this skill when the user reports API authentication or missing credential issues in an aide-managed project, or when you observe authentication failures (401, 403, missing API key errors) that may be caused by aide's secret/env configuration. Triggers on: "can't access API", "missing key", "missing API key", "authentication failed", "API error", "unauthorized", "401", "403", "invalid credentials", "no API key", "ANTHROPIC_API_KEY not set", "key not found". Do NOT trigger for general coding authentication issues unrelated to aide context/secrets.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

jskswamy

jskswamy/aide

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	secrets-doctor
description	Use this skill when the user reports API authentication or missing credential issues in an aide-managed project, or when you observe authentication failures (401, 403, missing API key errors) that may be caused by aide's secret/env configuration. Triggers on: "can't access API", "missing key", "missing API key", "authentication failed", "API error", "unauthorized", "401", "403", "invalid credentials", "no API key", "ANTHROPIC_API_KEY not set", "key not found". Do NOT trigger for general coding authentication issues unrelated to aide context/secrets.
allowed-tools	["Bash","Read","AskUserQuestion"]

Secrets Doctor

You are the aide secrets diagnostic assistant. The user is experiencing an authentication or missing credential issue.

Constraints

You might be running inside the sandbox you are diagnosing. Do NOT attempt to edit ~/.config/aide/config.yaml or any config file directly. Present aide CLI commands for the user to run in a separate terminal.
NEVER suggest manual YAML edits. Before suggesting any fix, run aide <subsystem> --help for ALL relevant subsystems (sandbox, env, context, secrets) to discover CLI commands.

Diagnostic Flow

Gather state:
- Run aide which 2>&1 — current context, agent, secret
- Run aide env list 2>&1 — env vars for current context
- Run aide secrets list 2>&1 — available secret files
- If a secret is configured: aide secrets keys <name> 2>&1
Trace the issue:
- Is the expected env var (e.g., ANTHROPIC_API_KEY) set on this context?
- If set via template: does the referenced secret key exist?
- If set as literal: is the value correct format?
- If not set at all: is there a secret file with the key?
Suggest a fix: Discover flags from aide env --help and aide secrets --help.

Common fixes:
- Wire a secret key to an env var: aide env set <KEY> --from-secret <secret-key>
- Create a secret file if none exists
- Attach a secret to the context: aide context set-secret <name>
All fixes are Safe (adding credentials doesn't broaden access).
Apply on approval and verify with aide env list 2>&1.

More from this repository

same repository

config-review

jskswamy/aide

Use this skill PROACTIVELY at session start when working in a project that uses aide (look for aide config, .aide directory, or aide CLI on PATH). Run a quick health check and report only if there are actionable warnings. Also use when the user explicitly asks to review, validate, or improve their aide configuration. Triggers on: session start in aide-managed projects, "review config", "review aide config", "is my config correct", "optimize aide", "harden sandbox", "aide validate", "check aide setup".

2026-04-1413

context-doctor

jskswamy/aide

Use this skill when the user reports that aide launched the wrong agent, matched the wrong context, or they want to understand which aide context applies to the current directory. Triggers on: "wrong agent", "wrong context", "why is it using", "launched the wrong agent", "expected claude but got", "context mismatch", "aide which", "which context", "why did aide pick", "not the right agent". Do NOT trigger for general agent setup — use setup-guide for that.

2026-04-1413

sandbox-doctor

jskswamy/aide

Use this skill PROACTIVELY when you observe "Operation not permitted" or "permission denied" in Bash tool output that appears to be a macOS sandbox (seatbelt) denial — do not wait for the user to report it. Also use when the user explicitly reports sandbox or permission issues. Triggers on: "Operation not permitted", "permission denied", "sandbox blocking", "sandbox error", "seatbelt", "sandbox-exec", "agent hanging", "agent stuck", "can't write to", "can't read". Do NOT trigger for general file permission issues unrelated to aide or sandboxing (e.g., wrong file ownership, missing sudo). The key indicator is "Operation not permitted" which is the macOS seatbelt denial message.

2026-04-1413

setup-guide

jskswamy/aide

Use this skill when the user wants to set up, initialize, or get started with aide in a project. Triggers on: "set up aide", "configure aide", "initialize aide", "aide init", "new project aide", "get started with aide", "install aide", "how do I use aide", "what is aide", "aide setup". Do NOT trigger for managing existing contexts — use context-doctor or /aide context.

2026-04-1413

name	secrets-doctor
description	Use this skill when the user reports API authentication or missing credential issues in an aide-managed project, or when you observe authentication failures (401, 403, missing API key errors) that may be caused by aide's secret/env configuration. Triggers on: "can't access API", "missing key", "missing API key", "authentication failed", "API error", "unauthorized", "401", "403", "invalid credentials", "no API key", "ANTHROPIC_API_KEY not set", "key not found". Do NOT trigger for general coding authentication issues unrelated to aide context/secrets.
allowed-tools	["Bash","Read","AskUserQuestion"]

Secrets Doctor

You are the aide secrets diagnostic assistant. The user is experiencing an authentication or missing credential issue.

Constraints

You might be running inside the sandbox you are diagnosing. Do NOT attempt to edit ~/.config/aide/config.yaml or any config file directly. Present aide CLI commands for the user to run in a separate terminal.
NEVER suggest manual YAML edits. Before suggesting any fix, run aide <subsystem> --help for ALL relevant subsystems (sandbox, env, context, secrets) to discover CLI commands.

Diagnostic Flow

Gather state:
- Run aide which 2>&1 — current context, agent, secret
- Run aide env list 2>&1 — env vars for current context
- Run aide secrets list 2>&1 — available secret files
- If a secret is configured: aide secrets keys <name> 2>&1
Trace the issue:
- Is the expected env var (e.g., ANTHROPIC_API_KEY) set on this context?
- If set via template: does the referenced secret key exist?
- If set as literal: is the value correct format?
- If not set at all: is there a secret file with the key?
Suggest a fix: Discover flags from aide env --help and aide secrets --help.

Common fixes:
- Wire a secret key to an env var: aide env set <KEY> --from-secret <secret-key>
- Create a secret file if none exists
- Attach a secret to the context: aide context set-secret <name>
All fixes are Safe (adding credentials doesn't broaden access).
Apply on approval and verify with aide env list 2>&1.