Capabilities stay, tools change
Capability nodes name what must happen in tool-neutral terms. When a skill disappears, the capability still tells you what you need.
Capability
Action Design
Specify the exact steps, tools, and decision points a skill uses to get work done.
1 skill mapped
Capability
Content Modeling
Define content types, fields, and validation so content stays structured and queryable.
1 skill mapped
Capability
Deployment
Ship the product to a public URL with repeatable, reversible steps.
1 skill mapped
Capability
Documentation
Write the files that let humans and agents understand, use, and maintain the work.
1 skill mapped
Capability
Fact Verification
Check claims, sources, dates, and links before content is published.
2 skills mapped
Capability
Frontend Development
Implement the interface in real, maintainable code with the chosen stack.
1 skill mapped
Capability
Information Architecture
Structure content and navigation so users and agents can find what they need.
0 skills mapped
Capability
Keyword Research
Find the search terms a real audience uses, with demand and competition signals.
2 skills mapped
Capability
Project Context
Keep shared knowledge about the project available to every agent and session.
3 skills mapped
Capability
Requirement Planning
Turn a fuzzy goal into a concrete set of requirements the agent can act on.
2 skills mapped
Capability
Scope Definition
Draw the boundary of what a skill or task does and does not do.
1 skill mapped
Capability
Testing
Verify behavior, links, layout, and performance with automated and manual checks.
3 skills mapped
Capability
Validation
Judge whether the result actually meets the acceptance criteria.
3 skills mapped
Capability
Visual Design
Give the product a coherent visual language including color, type, spacing, and component states.
0 skills mapped
Capability
Writing
Produce clear, useful prose that matches the brief and the audience.
2 skills mapped