setperms
Set tool permissions for Claude Code. Configures allowed commands, rules, and preferences in .claude/ directory. Triggers on: setperms, init tools, configure permissions, setup project, set permissions, init claude.
86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with strong trigger term coverage and clear completeness. The explicit 'Triggers on:' clause provides excellent guidance for skill selection. The main weakness is that the capability description could be more specific about the concrete actions performed (e.g., what files are created, what configuration options are available).
Suggestions
Expand the capability description to list more specific actions like 'creates .claude/settings.json', 'defines command allowlists', or 'configures MCP tool access'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (tool permissions, Claude Code) and some actions (configures allowed commands, rules, preferences), but doesn't list comprehensive specific actions like 'create permission files', 'define command allowlists', or 'set up security rules'. | 2 / 3 |
Completeness | Clearly answers both what ('Set tool permissions for Claude Code. Configures allowed commands, rules, and preferences in .claude/ directory') and when ('Triggers on: setperms, init tools, configure permissions, setup project, set permissions, init claude'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'setperms', 'init tools', 'configure permissions', 'setup project', 'set permissions', 'init claude'. These are practical variations users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Claude Code tool permissions and .claude/ directory configuration. The trigger terms are highly specific to this use case and unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflow steps and good safety considerations (asking before overwrite, git guardrails). The main weakness is verbosity - the same tool information appears in multiple places, and the embedded file contents make the skill quite long. The skill would benefit from extracting the JSON and markdown templates to separate reference files.
Suggestions
Extract the settings.local.json and cli-tools.md content to separate template files and reference them, reducing duplication and skill length
Remove the 'What This Does' tool listing since the same information appears in the actual file contents - just describe the purpose briefly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the tool lists appear multiple times (in 'What This Does', the JSON permissions, and the rules file). The tables in the rules file are useful but add significant length. | 2 / 3 |
Actionability | Provides fully executable bash commands and complete JSON/markdown content to write. The step-by-step instructions are copy-paste ready with exact file paths and content. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoint (Step 1 checks for existing files and asks user before overwriting). The execution flow diagram and conditional logic for overwrites demonstrate good workflow design. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic - the full JSON permissions and rules markdown are embedded inline rather than referenced. The options section at the end adds useful variations but the core content could benefit from splitting. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.