Agent-Native is Builder.io’s two-piece ecosystem: an MIT TypeScript framework (github.com/BuilderIO/agent-native) for apps where the agent and the UI call the same actions, and a curated pack of fifteen skills (github.com/BuilderIO/skills) that wires coding agents into those apps and adds workflow disciplines. Facts below verified as of 2026-09-13.
The pack is the half harness users meet first: fifteen SKILL.md directories that install anywhere the Agent Skills standard reaches, part workflow doctrine, part on-ramp to Builder.io’s stack.
What it is #
The framework defines each capability once as an action with a schema: the agent calls it as a tool, the UI calls it from code, and both paths get the same validation and permissions, exposed over HTTP, MCP, A2A, and a CLI.
The apps built on it (Slides, Plans, Mail, and a wider gallery) are what the bridge skills drive: /an opens a granted app beside the conversation, /webmcp prefers a page’s MCP tools over browser automation.
The rest of the pack is portable doctrine: /agent-watchdog audits another agent’s work, /plan-arbiter chooses between competing plans, /read-the-damn-docs forces a docs pass before guessing, /stay-within-limits pauses execution at 95% usage, with /visual-plan and /visual-recap as human review surfaces.
Install is npx @agent-native/skills@latest add, which writes to the shared .agents path (Codex, Pi, Cursor, OpenCode, Copilot) plus Claude Code’s native path, and the catalog repo doubles as a Claude Code and Cowork plugin marketplace; the npm package itself publishes from the framework monorepo.
Status #
Active and fast-moving, with a thin independent footprint. Both repos are MIT: the skills catalog at 4.2k stars, 208 forks, and 136 commits, the framework at 4.8k stars, 448 forks, and 5,377 commits, as of 2026-09-13. The npm package was created 2026-06-10, sits at 0.2.724 with nightly builds shipping several times a day, and pulled 14,212 downloads in the week of 2026-09-05 to 2026-09-11. No Hacker News threads and no independent coverage surfaced in this run’s searches, so the audience so far is GitHub and npm.
Strengths #
- The shared-action model sidesteps UI automation entirely: the agent never clicks, it calls the same validated function the UI calls.
- Roughly half the pack is framework-independent judgment discipline (watchdog, plan arbiter, docs-first, usage limits) that runs in any SKILL.md harness for free.
- Cross-harness by construction: the shared
.agentspath and the Vercel CLI plain-copy route mean no harness lock-in at install time.
Cautions #
- The pack’s gravity is Builder.io’s stack:
/anregisters the hosted Dispatch MCP endpoint,/visual-plandefaults to hosted share links (plan content to a hosted database, local-files mode is opt-in), and the installer offers managed AGENTS.md/CLAUDE.md instruction blocks. - 0.2.x with multiple nightlies a day is churn rather than stability, and the discipline skills are prompts, not enforcement, so whether
/plow-aheadplows or stalls is model judgment. /rewindneeds the separate signed Clips Desktop app on macOS with screen capture on your workstation; the install flow gates it, but it is capture software.- The thin community footprint (no HN threads, no third-party reviews found as of 2026-09-13) means no independent security eyes yet.
Pricing #
Free. Both repos are MIT, the hosted Dispatch endpoint and plans hosting cost nothing today, and I found no paid tier as of 2026-09-13.
Compared to #
- skills.sh: the ecosystem’s registry and ranking versus one vendor’s curated pack with an opinionated installer; complementary, and skills.sh’s plain-copy CLI installs this pack (minus
/rewindconfiguration). - Agent Skills open standard: the pack is spec-conformant SKILL.md directories, so it consumes the standard rather than competing with it.
- Anthropic Agent Skills: the other vendor pack, Claude-coupled where this one is cross-harness; both steer toward their vendor’s surface.
Bottom line #
Recommended as a cherry-pick source: take the discipline skills (/agent-watchdog, /plan-arbiter, /read-the-damn-docs) into any harness, and take the app bridges only if you actually use Agent-Native apps.
Not for teams that refuse vendor-managed instruction blocks or hosted MCP endpoints in their agent config.
My disagreeable claim: the apps and the framework are the least durable half, the workflow-discipline skills would survive Builder’s app bet failing, and the pack is an onboarding funnel wearing a toolbox costume.
Changes #
- 2026-09-13 - Created.
See also #
- skills.sh - the registry layer this pack sits alongside
- Agent Skills open standard - the packaging spec the pack follows
- Anthropic Agent Skills - the other vendor pack in the category
- MCP - the protocol the hosted Dispatch endpoint and app bridges ride
- Agentic Coding Tools Landscape - the map this category sits in
References #
https://github.com/BuilderIO/skills - the catalog repo: the fifteen skills, installer options, marketplace packaging, 4.2k stars as of 2026-09-13
https://github.com/BuilderIO/agent-native - the framework repo: shared-action architecture, app gallery, MIT, 4.8k stars as of 2026-09-13
https://www.agent-native.com/ - the framework landing
https://registry.npmjs.org/@agent-native/skills - package metadata: created 2026-06-10, latest 0.2.724, MIT, published from the monorepo, as of 2026-09-13
https://api.npmjs.org/downloads/point/last-week/@agent-native/skills - 14,212 weekly downloads, 2026-09-05 to 2026-09-11
https://hn.algolia.com/api/v1/search?query=%22builder.io%22%20skills&tags=story - the zero-hit search behind the missing-footprint statement