
An Agent Skills Maturity Model for Engineering Teams
Our opinionated six-level model measures whether agent workflows are documented, discoverable, tested, governed, and portable—not how many Markdown files a repository contains.

Our opinionated six-level model measures whether agent workflows are documented, discoverable, tested, governed, and portable—not how many Markdown files a repository contains.

Ten real Agent Skills failure modes—from invalid metadata and false portability claims to unsafe scripts and invented evidence—with standards-based fixes.

Separate standards compliance, vendor compatibility, workflow quality, and runtime evidence with a ten-point Agent Skills audit designed for real engineering repositories.

Skill selection begins with metadata, not the hidden body. Learn the documented progressive-disclosure model and the observable evaluation method we use to improve routing.

Learn how Copilot, Codex, and Claude load repository instructions, and how we keep one source of truth while preserving tool-specific discovery paths.

Personas and skills are not interchangeable. Learn the separation we use between role, persistent repository rules, and task procedures—and where it is convention rather than standard.

Learn what the Agent Skills standard actually requires, what agents see during discovery, and the authoring practices we use to make workflows clear, safe, and testable.

A clean .github/ directory is the difference between agents that follow your standards and agents that guess. Here is the layout for skills, agents, and instructions — and the rules that keep each in its lane.
May we use Google Analytics to understand visits to this website? It will load only if you agree. Read ourPrivacy Policy.