Separate skills from prompts, rules, tools, and MCP

A skill packages reusable know-how for an agent. It explains how to perform a class of tasks, including the choices, checks, and failure paths that matter.

A prompt asks for one result. Project rules apply broad instructions whenever an agent works in that project. A tool gives the agent a capability, such as reading a file or calling an API. MCP is one way to connect tools and data. The agent is the loop that chooses actions, observes results, and continues.

These pieces can work together. A release skill might tell an agent how to inspect a repository, which checks to run, and how to write a release report. Git and the shell provide the capabilities. Project rules may forbid force-pushing. Your prompt names the release you want reviewed.

Do not turn every useful paragraph into a skill. A fact belongs in project documentation. A permanent safety boundary belongs in project rules or permissions. A remote operation needs a tool. Create a skill when the missing piece is a repeatable procedure that an agent should discover for the right task.

For our project, write five short cards named Prompt, Rule, Skill, Tool, and MCP. Put one release-readiness responsibility on each card. If two cards claim the same responsibility, decide which layer should own it before continuing.