6 posts tagged #skills.
Loop engineering's six building blocks are all context primitives wearing new names. The scheduling is cron. The part that decides whether the loop works is the context delivered on every iteration.
Stored session transcripts are an external memory most people throw away after 30 days. A skill that forks a cheap model to grep, expand, and re-rank them turns 'what did we decide about X' into ranked snippets — so the agent stops re-making old mistakes.
Your debugging ability isn't intelligence, it's a procedure — and procedures are exactly what you can write down once and hand to an agent. Bootstrap the whole library with a meta-skill.
You don't author a skill from a blank page. You send a subagent to research the problem once, and the research becomes the skill — a build artifact, not a document.
The highest-leverage thing you can do for your agent isn't a better prompt — it's a better interface. Deep modules are persistent context the agent reads at a glance.
Your judgment — which tradeoff, which edge cases, which empty states — lives only in your head until something extracts it. A saved procedure that explores the repo, then grills you one branch at a time, turns a vague idea into a codebase-aware spec the agent can build against.