Generated 2.39:1 Open Skills masthead showing a reusable agent-skill workbench on the right side.

Open Skills.

Most agent wins disappear after the chat ends. You got the right workflow once, but next week you explain the context again, fight the same tool errors again, and re-teach the agent the same judgment again.

Open Skills is how you stop paying that tax. A skill is a compact operating procedure your agent loads on demand: when to use a method, which tools it calls, what standards matter, and what proof it owes you before it says done. The useful ones are personal. They carry your taste, requirements, dependencies, and hard-won decisions.

A good skill turns a one-off good session into repeatable behavior.

41 skills8 categories10 runbooks

This is where your agent gets your edge.

Open Skills is not a marketplace of generic superpowers. It is the layer where your standards, tools, preferences, and review habits become reusable instructions the agent can actually follow.

Stop re-explaining the work.

The skill remembers the procedure: inputs, tools, defaults, boundaries, and verification. You should not have to rebuild the same setup speech every time you open a new agent session.

Make taste operational.

Taste is not a vibe when it is written down as decisions. Your voice rules, visual standards, QA bar, and publishing habits can become part of how the agent works by default.

Build small, then compose.

One primitive handles transcription. Another handles voice. Another publishes. A runbook chains them into an actual workflow without turning every skill into a giant unreadable manual.

Start from the failure you keep repeating.

If the agent is close but unreliable, build a skill. If a workflow already uses several skills, study the runbooks. You can copy the prompts, adapt the primitives, or steal only the architecture.

Use the directory when you know the kind of capability you want to make repeatable: research, writing, publishing, media, QA, or agent operations.

Use runbooks when the real value is the chain: multiple skills handing work forward until a voice memo becomes a page, a release becomes a briefing, or a rough recording becomes a finished asset.