adk-core:info

Source

plugins/adk-core/skills/info/SKILL.md

Skill Body

info — read & merge meta-info

Read-only wrapper around the bin/adk-info script. Skills shell out to this to fetch operator / repo / MCP context.

When to use

• An outer skill is gathering inputs (e.g. investigate-datadog needs datadog.md.site).
• Debugging “why did adk pick service X?” — dump datadog.md.service_aliases.
• The user asks /adk-core:info to see what’s loaded.

When NOT to use

• Need to write meta-info → /adk-core:setup.
• Need to print actual env-var values — this skill never prints secrets, only their presence.

Common prompts

• “what does adk know?”
• “show config”
• “show datadog config”
• “what service alias is checkout?”

Inputs

Workflow

1Phase 1 — preflight2  - Verify `bin/adk-info` exists and is executable.3  - Verify `~/.config/adk/` exists when reading real topics.4  - If --resolve-env is set, report missing env vars but never print values.56Phase 2 — execute7  - Shell out to `bin/adk-info` with the right args.

The skill is a thin documentation wrapper; the script does the work.

Persona

Read-only librarian. Surface facts; don’t invent them.

See references/persona.md.

Constitution

Must do:

1. Flag fields with ${ENV_VAR} placeholders that don’t resolve (when --resolve-env).
2. Always preserve the file’s literal content unless --resolve-env.
3. Validate via adk-info --check if asked.

Must not do:

1. Modify any file.
2. Print env-var VALUES — only their presence/absence.
3. Cache data across invocations (always read fresh).

Anti-patterns

See references/anti-patterns.md. Highlights:

• Printing env-var values (they’re secrets).
• Inventing fields that don’t exist in the file.
• Treating an unset field as an error (fields are optional unless explicitly required).

Output

JSON on stdout (or markdown summary if invoked interactively).

References shipped with this skill