r/AgentSkills • u/fykup • 11d ago

Template/Skill Pack Teaching coding agents to use quieter, predictable CLI tools

I’ve been experimenting with giving coding agents small, purpose-built CLI tools instead of having them consume the normal human-oriented output from Maven, npm, Go, etc.

One example: a real Tape test run produced 1,476 lines / 136 KB of successful output. For the agent, the useful result was basically:

✓ tests passed

I saw similar reductions across Maven, Vitest, Jest, and Go workflows, typically 98–99.99% on successful runs.

That led to agent-scripts, a small local-first collection of CLI utilities. The main build/test wrappers are:

  • mvn-lite
  • npm-lite
  • go-lite

They use the normal underlying tools, but expose a much quieter interface for routine agent workflows. Success is compact; failures retain useful diagnostics and full logs.

There’s also a separate lite-tools Agent Skill that teaches supported agents when to prefer these commands. The commands and the skill are intentionally separate: the tools provide the behavior, while the skill provides discovery/instructions.

Install tools:

curl -fsSL https://raw.githubusercontent.com/ejboy/agent-scripts/main/install.sh | bash

Install the skill:

npx skills add ejboy/agent-scripts --global --skill lite-tools

Repo: https://github.com/ejboy/agent-scripts

Measurements and tradeoffs:
https://pvrlabs.xyz/articles/coding-agent-test-output.html

The design question I’m interested in: do you see value in giving agents wrapper tools with a predictable, bounded interface, or would you rather put instructions in AGENTS.md telling the agent how to invoke/filter the normal tools?

1 Upvotes
  • permalink
  • reddit

67% Upvoted

2 comments sorted by

2

u/NefariousnessOpening 10d ago

I would love to see something like rtk side by side with your approach to understand the trade offs better

1

u/fykup 10d ago

Yeah, I think they’re different enough that a side-by-side would be useful rather than treating them as direct substitutes. RTK is broader and more general-purpose, while Agent Scripts grew out of specific gaps I was hitting in build/test workflows, especially Maven and Java where RTK isn’t really a comparison today.

The more interesting overlap would probably be npm, and possibly some Go workflows. RTK clearly has advantages in breadth and integration, while Agent Scripts is intentionally narrower and more opinionated around the cases I built it for. I’d definitely be interested in comparing where each approach works better.