fix: prevent skill load failure when data-designer CLI is not installed#501
Conversation
Append `|| true` to the shell command that resolves the data-designer path so it always exits 0. Without this, the skill fails to load entirely when the CLI is missing, and the "If blank, see Troubleshooting" fallback is never reached.
Greptile SummaryMoves
|
| Filename | Overview |
|---|---|
| skills/data-designer/SKILL.md | Removes backtick CLI substitution at skill-load time; Troubleshooting updated to ask user permission before creating a venv or installing packages |
| skills/data-designer/workflows/autopilot.md | Adds step 1 to resolve CLI path at runtime with CLI_NOT_FOUND sentinel; all subsequent steps renumbered |
| skills/data-designer/workflows/interactive.md | Adds identical CLI-resolution step 1 as autopilot.md; subsequent steps renumbered consistently |
Sequence Diagram
sequenceDiagram
participant Agent
participant Shell
participant User
Agent->>Shell: command -v data-designer 2>/dev/null
alt Found in system PATH
Shell-->>Agent: /usr/local/bin/data-designer
Agent->>Shell: data-designer agent context
else Not in PATH
Shell-->>Agent: (empty, exit 1)
Agent->>Shell: test -x .venv/bin/data-designer && realpath ...
alt Found in .venv
Shell-->>Agent: .venv/bin/data-designer (resolved path)
Agent->>Shell: .venv/bin/data-designer agent context
else Not found anywhere
Shell-->>Agent: CLI_NOT_FOUND
Agent->>User: CLI not installed — would you like me to set up a venv?
end
end
Reviews (6): Last reviewed commit: "Merge branch 'main' into johnny/fix/skil..." | Re-trigger Greptile
Replace `|| true` (blank output) with `|| echo NOT_FOUND` so the agent sees a clear signal. Update the instruction to bold/imperative so it actually gets followed.
Remove the \!`command` substitution from SKILL.md and add a "Resolve CLI command" step to both workflows. The agent now runs the lookup itself and uses the result as the data-designer executable for all subsequent commands. If the command fails, the agent stops and follows Troubleshooting.
The resolve command now always exits 0 and outputs CLI_NOT_FOUND when the executable is missing, so the agent evaluates a value rather than reacting to a shell error.
Update Troubleshooting to ask the user before creating a venv or installing packages, instead of attempting it automatically.



Summary
!backtick command substitution from SKILL.md that resolved thedata-designerCLI path at skill load time — if the CLI wasn't installed, this could cause the skill to fail to load entirelyCLI_NOT_FOUNDsentinel (via|| echo CLI_NOT_FOUND) so the command always exits 0 — this prevents the agent from going into error-fixing mode and instead keeps it following the workflow instructions