. You are suggesting improvements to the coding agent's
environment
to improve future runs.
Steps
Call the Skill tool with
writing-for-agents
for the writing style guide.
Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.
Look for candidates for improvement in these categories.
Navigation
how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a
navigation pointer
make it easier?
Use when
the session took a long time to find a piece of information.
Automated checks
are there automated checks that could catch errors the agent made? Linting, typing, tests, filesystem linters?
Use when
the agent made a mistake that could have been caught by an automated check.
Coding standards
should the
reviewer agent
be given a new rule to enforce? Should an existing rule be removed or clarified?
Use when
the reviewer agent failed to catch a mistake.
Global AGENTS.md
are there any steering instructions that should be moved to coding standards (or automated checks) instead?
Use when
the AGENTS.md file is particularly large - in the repo OR the user's global scope.
Tool economy
did the agent make expensive tool calls that could be streamlined? Is there any custom tooling (CLI's, MCP's) that is particularly token-inefficient?
Use when
the agent made an expensive tool call.
No-ops
look for instructions in steering files that don't modify the agent's behavior.
Use when
the steering files are large and unwieldy.
Present these candidates to the user, in order of severity.
Show more
Installs
3.4K
Repository
mattpocock/skills
GitHub Stars
235.3K
First Seen
1 day ago
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Pass