A hosted registry and sync service for agent 'skills' (SKILL.md-style instruction + script bundles) that works across Claude Code, Cursor, Codex, Pi, and OpenCode: publish once with versioning, install anywhere with one command, get diff and deprecation alerts when a skill you depend on changes. Adds a marketplace layer for paid skills with install analytics for authors.

Market Panorama

Competitive Intelligence

Users & Demand

Business Model

Market Sizing

Tech Solution & Build Plan

Go-to-Market Strategy

Risk Assessment

Action Recommendations

### Market definition and scope

The agent-skills registry market is the distribution layer for reusable agent skills — SKILL.md-style instruction-plus-script bundles that teach a coding harness how to do a repeatable job. A registry in this market does four things a bare GitHub repository cannot: it versions (semantic versioning on publish, deprecation flags on retirement), it installs (one command that writes the skill into the correct directory and format for Claude Code, Cursor, Codex, Pi, or OpenCode), it alerts (diff notifications when a dependency changes major versions), and it measures (install analytics by harness, version, and referrer — data GitHub has never given skill authors). The market excludes the harnesses themselves, the skill-authoring frameworks, and generic package managers that do not understand the skill file format. Its unit of value is the install that works everywhere and the upgrade that does not silently break.

Three buyer groups share one job. Agent power users run two or more harnesses daily — the Claude Code plus Cursor pair is now the norm — and maintain a personal skill library that currently must be copied into each tool's expected location by hand. Skill authors, usually senior engineers, publish skills to GitHub where they collect stars but no installs telemetry, no dependency graph, and no revenue path. Team leads want a private, curated skill set shared org-wide with governance: who can publish, what is deprecated, what the whole team runs. All three hit the same wall — every harness stores and loads skills differently, so a skill that works in one tool is a copy-paste project in the next, and an upstream change breaks consumers silently (packet expanded_analysis, 2026).

### Key trend signals

Four signals from this month define the window. First, a personal skill directory became a product: mattpocock/skills reached 883 stars described as 'Skills for Real Engineers. Straight from my .agents directory' — the stars are install-intent, not curiosity, because the repo's only use is to be copied into your own setup (GitHub Trending, October 2026). Second, methodology is being productized around skills: obra/superpowers at 455 stars packages an 'agentic skills framework & software development methodology' — proof that skills are becoming the unit of craft, not just config (GitHub Trending, October 2026). Third, a harness vendor is building ecosystem infrastructure: cursor/plugins at 150 stars is an official plugin specification, and historically vendor spec adoption precedes third-party registries — the VS Code extension marketplace and GitHub Actions ecosystem both followed this exact sequence (GitHub Trending, October 2026). Fourth, the workflow audience adopts at scale: DietrichGebert/ponytail at 1,194 stars, trending for a second straight month with the pitch 'makes your AI agent think like the laziest senior dev in the room,' shows the same developer population will standardize on whatever removes friction first (GitHub Trending, October 2026).

### Why now — what changed

Three things changed at once. Every major harness shipped skill-file support this cycle, which made skills a standard in name while leaving them fragmented in practice — each vendor chose its own directory, format, and loading convention, so the cross-harness problem was created by the very adoption that validates the category (packet problem_definition, 2026). The author side emerged as an economic class: when one engineer's .agents directory draws 883 stars in a trending cycle, skill authorship has an audience, and audiences without infrastructure are registries waiting to happen. And the adjacent infrastructure proved the model decades early: npm, the VS Code marketplace, and GitHub Marketplace all demonstrate that developers pay for distribution — free public hosting, paid private tiers, a marketplace take rate — which means the registry does not need to invent its business model, only port it (packet market_analysis, 2026).

### Market maturity assessment

This is an early market at the category-naming stage. Demand evidence is strong but pre-revenue: 1,697 combined stars across the four skills-related trending repos this month, sustained multi-month trending for the workflow audience (ponytail), and vendor-spec movement (cursor/plugins) — but no user yet says 'I need a skills registry'; they say 'I copy my skills folder into every tool.' The infrastructure layer has no dominant vendor: GitHub is the implicit registry by default, which is precisely the gap, because a Git host cannot version a directory's semantics, alert on dependency drift, or attribute installs. Public analysts place the AI developer-tools market in the $20-30B range growing at 20-30% CAGR (estimate based on Statista and MarketsandMarkets ranges, 2025-2026), of which the skills distribution slice is a brand-new, unmeasured layer.

### What this means for a solo founder

Own the neutral position before a vendor does. Concretely: target the 100k-200k multi-harness power users first, because they feel the copy-paste pain weekly and convert on a one-command install; build the format conversion for all five harnesses before adding any premium feature, since cross-harness install is the moat-adjacent capability no vendor can copy without abandoning its own ecosystem; lead with authors rather than users — hand-migrate the top 50 open skill repos, give each author the analytics dashboard free forever, and let their READMEs become your distribution; and move inside the current trending cycle, because the topic is primed now (1,697 stars this month) and a vendor registry announcement is the one event that closes this window on someone else's terms.

mattpocock/skills at 883 stars — 'Straight from my .agents directory' — its only use is installation, so its stars are install-intent proving the category.

A personal skill directory became a product

obra/superpowers at 455 stars packages an agentic skills framework with a full development methodology attached — skills are becoming the unit of craft.

Methodology is being productized around skills

cursor/plugins at 150 stars is an official plugin spec; vendor-spec adoption historically precedes third-party registries (VS Code extensions, GitHub Actions).

A harness vendor is building ecosystem infrastructure

DietrichGebert/ponytail at 1,194 stars, trending a second straight month — the same audience will standardize on whatever removes friction first.

Portable Agent Skills Registry