What is the fundamental difference between using Tools and using Skills?	Tools connect Claude to external data or actions (what it can do); Skills teach Claude a procedure or playbook (how it should be done).
What is the core file that defines the instructions and resources within a Skill?	The `SKILL.md` file.
How do Skills manage context when many are available, preventing context bloat?	Only the name and description load at startup; the full Skill loads into context only when the agent determines it is relevant.
What is the primary function of a Skill?	To standardize output by teaching Claude a specific, repeatable procedure (e.g., a status report format).
How are Skills initially uploaded and referenced in the system?	They are uploaded once to the workspace using `client.beta.skills.create` and referenced by their unique ID.
When making a message API call, where must Skills be attached?	They must be attached within the `container` configuration object, specifically the `container.skills` list.
What is the key benefit of using Skills for team processes?	They ensure consistent structure, tone, and sections in the output, regardless of who submits the prompt.
When should a Skill often be paired with code execution?	When the Skill's procedure needs to perform real work, such as running scripts in a terminal.
If a user wants Claude to "look up a code section" or "send an email," which feature should be used?	Tools.