chmod
Change file mode/permissions. Use when setting read/write/execute permissions on files and directories.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.flox/pkgs/skill-coreutils/skills/chmod/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is functional and well-structured with a clear 'Use when' clause that makes it easy for Claude to know when to select this skill. Its main weaknesses are limited specificity in the actions it covers and missing common natural trigger terms like 'chmod', '755', or 'make executable' that users would frequently use when needing this skill.
Suggestions
Add more natural trigger terms users would say, such as 'chmod', '755', '644', 'make file executable', 'permission denied', 'rwx', or 'octal permissions'.
List additional specific actions beyond just 'change' — e.g., 'Sets file mode bits, changes ownership permissions, makes scripts executable, applies recursive permission changes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (file permissions) and the core action (change file mode/permissions), but doesn't list multiple specific concrete actions like setting ownership, recursive permissions, ACLs, or symbolic vs numeric modes. | 2 / 3 |
Completeness | Clearly answers both 'what' (change file mode/permissions) and 'when' (Use when setting read/write/execute permissions on files and directories) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'permissions', 'read/write/execute', 'file mode', and 'directories', but misses common natural terms users would say such as 'chmod', 'executable', 'rwx', '755', 'make file executable', or 'permission denied'. | 2 / 3 |
Distinctiveness Conflict Risk | File permissions/mode changes is a clear, narrow niche that is unlikely to conflict with other skills. The trigger terms are specific enough to distinguish this from general file operations or other system administration tasks. | 3 / 3 |
Total | 10 / 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 solid reference-style skill for chmod with excellent actionable examples and useful gotchas that add real value beyond what Claude already knows. The main weakness is verbosity — several tables (flags, symbolic mode symbols) document information Claude already has strong knowledge of, consuming tokens without proportional benefit. The gotchas section is the strongest part, providing genuinely useful warnings and alternative patterns.
Suggestions
Remove or significantly trim the flags table and symbolic mode symbol table — Claude already knows these. Focus token budget on the gotchas and the octal reference table which provide more unique value.
Consider trimming the synopsis section since Claude knows chmod's basic syntax, and lead with the most valuable content (examples and gotchas).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some information Claude already knows well, such as the full flags table (--help, --version), basic permission concepts, and the symbolic mode symbol table. The octal mode reference table and gotchas section add genuine value, but the overall content could be tightened. | 2 / 3 |
Actionability | The examples section is excellent — fully executable bash commands covering common use cases from basic to advanced (setuid, sticky bit, capital X, find-based differentiation). The gotchas section provides actionable alternatives (e.g., the find command pattern instead of recursive chmod). | 3 / 3 |
Workflow Clarity | For a single-command skill like chmod, there is no multi-step workflow needed. The content clearly presents the command patterns, and the gotchas section effectively serves as validation guidance (e.g., warning against 777, recommending find for recursive operations). The single-task nature is handled unambiguously. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections (Synopsis, Flags, Permission Modes, Examples, Gotchas), but it's somewhat monolithic — the full flags table and symbolic mode reference could be separated or trimmed. For a standalone skill with no bundle files, the structure is adequate but the inline reference tables make it longer than necessary. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- flox/floxenvs
- Commit
bb1f07d
- 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.