What happened?
Case 1 - standalone skill:
shell-file-info skill references bash scripts/info.sh <file>. The script exists next to the SKILL.md. Auggie runs it from project root -> No such file or directory. Falls back to manual analysis.
Auggie output
◊ ✅ Running custom command "shell-file-info" with arguments: "bump.sh"
~ The user wants to run the shell-file-info skill on `bump.sh`.
● Terminal - bash scripts/info.sh bump.sh
⎿ Command error
⎿ /usr/bin/bash: scripts/info.sh: No such file or directory
● Read Directory - c:\workspaces\maximge-labs\agentic-plugins
⎿ Listed 14 entries
● c:\workspaces\maximge-labs\agentic-plugins\.claude\skills\shell-file-info\SKILL.md - read file
⎿ Read 15 lines
~ The skill says to run `bash scripts/info.sh <sh-file-path>`, but there's no `scripts/info.sh` file.
● c:\workspaces\maximge-labs\agentic-plugins\bump.sh - read file
⎿ Read 16 lines
~ The `scripts/info.sh` doesn't exist, so I need to manually analyze the file and report the metrics that the script would have reported.
● The scripts/info.sh script doesn't exist in the workspace, so I analyzed bump.sh directly and gathered all the metrics:
Case 2 - skill inside a plugin:
Same problem with pdf-processor skill inside aplugin, which references python "scripts/process.py". The script exists but can't be found at runtime.
What did you expect to happen?
Auggie should resolve relative scripts/ paths relative to the skill directory (where SKILL.md lives). This follows the Agent Skills spec and Augment's own docs. Claude Code handles this correctly.
Steps to reproduce
Steps to reproduce (case 1):
Steps to reproduce (case 2):
auggie plugin marketplace add maximge-labs/agentic-plugins
auggie plugin install aplugin@amarket
- Ask auggie to run the
pdf-processor skill on any PDF
- Same error with `scripts/process.py
Auggie version
0.22.0 (commit 053888ee)
Request ID
626be00d-ff70-4c94-9c61-5a0e91af1d55
Environment details
Environment
Anything else we need to know?
Workaround: use absolute path with ${CLAUDE_PLUGIN_ROOT} as shown in md-info, but this breaks the documented convention and doesn't work for standalone skills (case 1).
What happened?
Case 1 - standalone skill:
shell-file-info skill references
bash scripts/info.sh <file>. The script exists next to the SKILL.md. Auggie runs it from project root ->No such file or directory. Falls back to manual analysis.Auggie output
Case 2 - skill inside a plugin:
Same problem with pdf-processor skill inside
aplugin, which referencespython "scripts/process.py". The script exists but can't be found at runtime.What did you expect to happen?
Auggie should resolve relative
scripts/paths relative to the skill directory (where SKILL.md lives). This follows the Agent Skills spec and Augment's own docs. Claude Code handles this correctly.Steps to reproduce
Steps to reproduce (case 1):
/shell-file-info bump.shSteps to reproduce (case 2):
auggie plugin marketplace add maximge-labs/agentic-pluginsauggie plugin install aplugin@amarketpdf-processorskill on any PDFAuggie version
0.22.0 (commit 053888ee)
Request ID
626be00d-ff70-4c94-9c61-5a0e91af1d55
Environment details
Environment
Anything else we need to know?
Workaround: use absolute path with
${CLAUDE_PLUGIN_ROOT}as shown in md-info, but this breaks the documented convention and doesn't work for standalone skills (case 1).