agent-look
Finds the screenshots you just took, reads the text via Spotlight OCR, renames generic files, and reports back with the useful evidence. It is the scout with binoculars.
Spotting
Tool family
Each practical tool gets a sharp identity up front.
We are not building a pile of vague abstractions. We are building a family of practical tools that agents can trust. Each one is legible at the beginning, useful on day one, and progressively less visible as the agent stack absorbs the pattern.
Agent skills
Package repeatable moves into named capabilities. A good skill starts visible enough to teach the pattern, then becomes something the agent reaches for automatically at the right moment.
Learned routinesAgent plugins
Extend the agent into real tools and environments. Browser control, local state, external systems, file access: practical reach with a clear job boundary and a clean handoff back to the agent.
Reach
The point is not to keep the tool in the foreground forever. The point is to give it enough shape that agents and humans both know what it is for. Once that is learned, the tool should feel like infrastructure, not ceremony.
Name the job clearly.
Give the tool a crisp purpose and an identity strong enough that people understand when it should be used.
Make it frictionless.
One command, one habit, one obvious move. The tool should solve a real annoyance immediately, not after a migration project.
Let it disappear.
As the agent stack matures, the skill becomes implicit. The capability remains, but the user no longer has to think about the machinery.