Skip to content
AI Primer
workflow

Agent Skills supports Codex, Cursor, Gemini CLI, and VS Code through new libraries and plugins

New guides, plugins, and reusable libraries show the Agent Skills format moving beyond Claude Code into multiple coding-agent clients and runtimes. That matters because workflows are becoming portable artifacts instead of one-off prompts tied to a single harness.

5 min read
Agent Skills supports Codex, Cursor, Gemini CLI, and VS Code through new libraries and plugins
Agent Skills supports Codex, Cursor, Gemini CLI, and VS Code through new libraries and plugins

TL;DR

You can inspect the Obsidian skills repo, browse OpenAI's skills repository, and check the Codex locked-use docs. There is also a live plugin example in DAIR Academy plus the matching plugin repo, and Cursor is now pushing its own builder surface through the Cursor SDK docs.

Agent Skills

The clearest signal this week came from the teaching material, not a launch post. nerdai described Agent Skills as an open standard built for Claude Code and now adopted across Cursor, Gemini CLI, VS Code, GitHub Copilot, Codex, and others.

That matters because the unit of reuse changes. Instead of copying a system prompt between tools, a skill package can expose discovery, activation, and execution behavior that a compliant client knows how to load.

Libraries and installers

Two different distribution patterns showed up at the same time:

The pattern is simple: skills are getting package surfaces, install flows, and repos of their own.

Codex as a host runtime

OpenAI's weekly Codex rollout was nominally about product features, but the bundle reads like infrastructure for longer-running, more composable workflows.

Once a client has goals, plugins, permissions, remote control, and long-running sessions, skills stop looking like a side feature. They look like the task layer sitting on top of the runtime.

Specialized skills

The interesting examples are already narrow.

  • /lesson-generator can build a course on any topic, call an image generator, and return the result as an HTML artifact omarsar0's launch post.
  • Steph Ango's Obsidian skills package teaches agents Obsidian-flavored Markdown, .base files, JSON Canvas, CLI workflows, and Defuddle-based web extraction, according to pauliusztin_'s repo walkthrough.
  • swyx's Kakuna package is explicitly framed as a hardening suite with checklists, subagent parallelism, and strong opinions about codebase hygiene swyx's Kakuna thread.
  • autoreview is already being used on large refactors, where steipete's report said it ran for five hours fixing issues, while steipete's scratch-log suggestion argued for persistent logs of agent decisions during bigger changes.

These are not generic "be better at coding" prompts. They encode domain objects, review habits, and multi-step workflows that travel between agent harnesses.

SDKs and shared memory

Portability is also spreading one layer below skills.

Cursor's SDK now exposes Composer 2.5 in Python and TypeScript, with Cursor linking its own /sdk skill as the on-ramp cursor_ai's SDK launch. In parallel, LLMpsycho's agentmemory post pitched persistent memory for Claude Code, Cursor, Codex CLI, Hermes, OpenCode, and any MCP client through a single project.

The bigger shift is that memory, SDKs, and skills are all being framed as cross-client building blocks at the same time. When that stack stabilizes, the harness matters less than the artifact you install into it.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 3 threads
Libraries and installers1 post
Codex as a host runtime3 posts
Specialized skills3 posts
Share on X