Skip to content
Module
Module 3 of 5Lesson 4 of 4~14 min

A skill's tools and permissions

A skill that can run commands or edit files without oversight quickly becomes a risk for your data and your repository. This lesson teaches you to decide which tools to allow, remove or keep under approval based on how serious each action is, and to set how the skill is launched and executed.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to choose which tools to pre-approve, remove or leave subject to approval for a skill, according to the risk of its actions, and set its invocation and execution mode accordingly.

Topics covered

  • skill permissions
  • allowed-tools
  • skill security
  • Claude Code
  • pre-approved tools

Where it fits

Design and write your skill

How do I write a skill that triggers at the right moment, produces a checkable result and has only the permissions it needs?

Lessons in this module

  1. Write a description that triggers at the right moment
  2. Scope your skill before writing it
  3. Write the SKILL.md and install it
  4. A skill's tools and permissions (this lesson)

What you will learn in this module

This lesson is part of the course Build reliable Claude Skills for your product work

  • Write a name and description that trigger the skill at the right moment, and choose who can invoke it.
  • Design a complete SKILL.md (frontmatter, checkable rules, procedure, output format, reference files) from a scoping brief.
  • Configure a skill's pre-approved and removed tools according to risk, without confusing pre-approval with restriction.

Related courses