AI / Agents Agents Archived

Why is sharing one set of agent skills across my team and three coding tools still a bootstrap script?

Teams write skills and instructions for coding agents, then copy them by hand between repos, laptops and tools like Claude Code and Codex, with no versions, no tests and no way to know which copy is current.

Who has it: Engineering teams and solo developers using two or more coding agents who maintain shared skills, AGENTS.md files and conventions.

“These are supposed to be portable between agents, and so distributing them is currently awkward.”

Quoted word for word from the public post linked below. Nobody submitted it to Real Problem AI.

Ask HN thread on how people manage skills files, 6 September 2026, 320 points, 299 comments.

Why it is archived

Trimmed to 100-cap (lowest opportunity_score)

Scoring breakdown

7.3/ 10

Problem Severity6

Feasibility today8

Market Signal9

Competition Gap6

Existing players

Claude Code plugins and skills · Install skills for one tool, not across every agent a team uses.
chezmoi dotfiles · How commenters sync skills today, by symlinks and their own scripts.
Skillsync · Launch HN product for moving chat sessions between agents, not for versioning and testing team skills.

What they are missing

A skills registry for teams: one source of skills with versions, owners and changelogs, installed into each agent's expected folder, with small test tasks that show a skill still works after a model or tool update.

Stack hint

01Git-backed skills registry

02Per-agent install adapters (Claude Code, Codex, Cursor)

03Skill test runner with sample tasks

04Usage logging to find unused or broken skills

#OCT9 · Canonical URL: https://www.realproblem.ai/archive/why-is-sharing-one-set-of-agent-skills-across-my-team-and-three-coding-tools-still-a-bootstrap-script