Review a skill before binding it to a teammate

Read the skill as instructions that can influence the AI tool. Check its resources and assumptions before connecting it to a role with real project access.

Work through these checks

1. Instructions

understand the requested actions. Record the evidence or the unresolved question before moving on.

2. Resources

locate every referenced file. Record the evidence or the unresolved question before moving on.

3. Dependencies

identify required tools. Record the evidence or the unresolved question before moving on.

4. Permissions

review the chosen execution environment. Record the evidence or the unresolved question before moving on.

5. Fixture

test with a small safe input. Record the evidence or the unresolved question before moving on.

Put the checklist to work

A skill that references templates/report.docx needs that template available; copying SKILL.md alone does not supply it.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

A marketplace role or imported skill is not automatically endorsed by every service it references.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.