From 6654f6b60cd9d5be8b54c6fafe44346dabeb3b76 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Mon, 24 Aug 2026 15:19:57 +0100 Subject: [PATCH] feat: add 'Information access' category to retrospective skill for improved agent insights --- skills/in-progress/retro/SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/skills/in-progress/retro/SKILL.md b/skills/in-progress/retro/SKILL.md index fc020ea..f5fed82 100644 --- a/skills/in-progress/retro/SKILL.md +++ b/skills/in-progress/retro/SKILL.md @@ -20,6 +20,7 @@ The user has asked for a **retrospective**. You are suggesting improvements to t - **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. +- **Information access**: look for opportunities to increase the agent's access to information. Teeing dev server logs, readonly access to third-party services. _Use when_ a crucial piece of information was not available to the agent. 4. Present these candidates to the user, in order of severity.