Prompt, skill or agent?
A prompt gives a particular task. A skill documents a reusable way to perform work. An agent chooses actions using the tools available to it. A saved instruction does not grant access to email, a CRM or private files. Capabilities and permissions depend on the environment.
Example: a weekly team summary
A repeated reporting task benefits from consistent inputs and acceptance criteria.
A template for your task
Name: Weekly team summary. Use when: preparing a report from the agreed spreadsheet. Inputs: period, data and metric definitions. Steps: check coverage and missing values; calculate metrics; separate facts from hypotheses; list open questions. Output: a brief summary and a change table. Check: every figure matches the source. Boundary: do not send the report or modify the source without a separate instruction.
Review a skill before use
Look for a specific task, expected inputs and a definition of done. For external skills, inspect instructions and executable files, requested data, destinations and proposed actions. Popularity is not a substitute for review.
Test before sharing
Try a normal case, incomplete input and conflicting information. Keep a versioned instruction and an expected example. Recheck after changes to the model or workflow. Remove credentials and private customer information before distributing files.
Keep simple tasks simple
A short prompt may be enough for a one-off request. Skills are useful when a team wants to maintain and repeat a defined procedure.
Common questions
Can I share a skill?
Yes, where you have permission to distribute its contents. Remove secrets and personal information and check compatibility with the recipient’s tool.
Are Claude and Codex skills identical?
The general idea is similar, but supported files, loading and capabilities can differ. Check the relevant documentation and test the transfer.
Related documentation
The examples and review approach are original. Check each tool’s documentation for current capabilities.