Package repeatable work as skills
Separate an agent's role from task-specific instructions, examples and supporting resources.
Who does the work, and how?
The infographic describes an agent as who does the work and a skill as how to perform a recurring task. A skill can package instructions, templates, examples, reference material and scripts.
The image's migration example illustrates a repeatable procedure: inspect a schema, create a named migration, include rollback considerations and test locally. Those are workflow ideas, not authorization to change a real database.
Make discovery meaningful
A skill needs a clear name and description so a supported host can identify when it is relevant. The image shows a SKILL.md entry point and supporting folders.
Supported directories, automatic activation and personal-skill availability differ by product. The illustrated project and home-directory paths are not a guarantee that every cloud session can access your local files.
Review executable resources
Treat scripts as code that needs review and restricted permissions. Loading a skill must not expand an agent's authorization. Require approval before high-impact actions, even when a skill presents them as an ordinary step.