AI / Agents Agents

Cite as: Real Problem AI problem “Why is there no good way to keep my AI agent skills organised, shared and working across tools?”. Opportunity score 7.8 out of 10 (severity 7, AI feasibility 9, market signal 8, competition gap 7). Category AI / Agents. Trend Agents. Source signal: Ask HN thread "How do you manage skills files?", 6 September 2026, 320 points, 123 comments.. Canonical URL: https://www.realproblem.ai/idea/why-is-there-no-good-way-to-keep-my-ai-agent-skills-organised-shared-and-working-across-tools.

Why is there no good way to keep my AI agent skills organised, shared and working across tools?

Developers and teams now write reusable skills and instruction files for Claude Code, Codex and other agents, then keep them in dotfiles, private repos and symlinks, with no way to find good ones, share them between tools or tell whether a skill still works.

Who has it: Developers and engineering teams who use coding agents daily and maintain their own skills, AGENTS.md and CLAUDE.md files.

Evidence

“How do you find skills, keep them organized, and make sure they actually work?”

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

Ask HN thread "How do you manage skills files?", 6 September 2026, 320 points, 123 comments.

Scoring breakdown

7.8/ 10
Problem Severity7
Feasibility today9
Market Signal8
Competition Gap7

Existing players

  • Dotfiles managers such as chezmoi with symlinks · Sync files between machines, but know nothing about whether a skill triggers or still works.
  • Community skill repositories on GitHub · Good starting points, but discovery is by reputation and every update is manual.
  • Company bootstrap scripts · Teams write their own scripts to push shared skills into each developer folder, and each agent reads a different path.

What they are missing

One place that stores skills once, installs them for every agent that reads them, runs a small test prompt to show whether each skill still triggers and helps, and flags skills the newer models no longer need.

Stack hint

01Git-backed skill registry
02Per-agent installers for Claude Code, Codex and others
03LLM-run skill tests and regression prompts
04Usage telemetry kept local

#OCT17 · Canonical URL: https://www.realproblem.ai/idea/why-is-there-no-good-way-to-keep-my-ai-agent-skills-organised-shared-and-working-across-tools