Skip to main content
← Back to list
01Issue
BugShippedSwamp CLI
Assigneesstack72

#370 swamp-vault skill documents 'swamp vault read' but correct subcommand is 'read-secret'

Opened by leeehinman · 5/18/2026· Shipped 5/18/2026

Description

The swamp-vault skill (shown to agents as project instructions) documents reading a secret as:

swamp vault read <vault_name> <key>

But the actual CLI subcommand is read-secret, not read:

swamp vault read-secret <vault_name> <key>

Running swamp vault read produces an error or unexpected behavior.

Steps to Reproduce

  1. Follow the swamp-vault skill's "read a secret" example
  2. Run: swamp vault read <vault_name> <key>
  3. Observe: command not found / error

Expected Behavior

The skill documentation should match the CLI. Either the skill should be updated to use read-secret, or (if read is intentionally an alias) it should be added to the CLI.

Environment

  • swamp version: 20260516.045246.0-sha.e6eda98d
  • Discovered via: agent attempting to read a vault secret and producing wrong command for user
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_MERGEDCOMPLETE

Shipped

5/18/2026, 6:47:36 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack725/18/2026, 5:32:37 PM
Editable. Press Enter to edit.

stack72 commented 5/18/2026, 6:29:34 PM

Investigated the skill documentation thoroughly. The SKILL.md body already correctly documents read-secret everywhere — Quick Reference table (line 45), Read a Secret section (lines 175, 178), and the vault expression example (line 239). The only place vault read appeared without -secret was in the frontmatter trigger phrase list, which listed "vault read" instead of "vault read-secret". This trigger phrase is what likely caused the agent to infer swamp vault read as a valid CLI command. Fix: changed the trigger to "vault read-secret" in PR #1395.

Sign in to post a ripple.