chown

Change file owner and group. Use when adjusting file ownership, typically requires root/sudo.

Quality

80%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.flox/pkgs/skill-coreutils/skills/chown/SKILL.md

Quality

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 concise and well-structured with a clear 'Use when' clause that addresses both what the skill does and when to use it. Its main weakness is limited specificity in actions and missing some natural trigger terms users might use (e.g., 'chown', 'chgrp'). Overall it's a functional description that could be improved with additional trigger keywords and more detailed capability listing.

Suggestions

Add common command-related trigger terms like 'chown', 'chgrp', and variations such as 'change owner of a file' or 'recursive ownership'.

List additional specific actions such as 'change ownership recursively, transfer ownership between users, update group assignments' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (file ownership) and the core action (change file owner and group), but only describes one action rather than listing multiple specific concrete actions like recursive ownership changes, checking current ownership, etc.	2 / 3
Completeness	Clearly answers both 'what' (change file owner and group) and 'when' (use when adjusting file ownership, typically requires root/sudo), with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes relevant terms like 'file owner', 'group', 'file ownership', 'root/sudo', but misses common natural terms users would say such as 'chown', 'chgrp', 'permissions', or 'change owner of a file'.	2 / 3
Distinctiveness Conflict Risk	File ownership is a clear, narrow niche distinct from general file permissions (chmod), file management, or other system administration tasks. The mention of owner/group and root/sudo makes it unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

85%

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 reference skill for the chown command with strong actionability through concrete examples and useful gotchas. The main weakness is that the comprehensive flags table is largely unnecessary for Claude, who already knows coreutils well—the skill could be more concise by focusing only on the ownership formats, examples, and gotchas sections which provide the most unique value.

Suggestions

Consider trimming or removing the full flags table, as Claude already knows standard coreutils flags—keep only non-obvious flags like --from and --reference that pair with the examples

Remove the synopsis section since Claude knows chown's basic syntax; the ownership formats table already captures the important nuances

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some information Claude already knows well, such as the full flags table (Claude knows coreutils flags) and basic explanations. The ownership formats table and gotchas add genuine value, but the comprehensive flag listing is largely redundant for Claude.	2 / 3
Actionability	The examples section provides fully executable, copy-paste ready bash commands covering all major use cases. Each example is concrete with clear comments explaining the purpose.	3 / 3
Workflow Clarity	This is a single-command skill with no multi-step workflow needed. The gotchas section effectively serves as validation guidance (e.g., needs root/sudo, symlink behavior with -R, --from for safe bulk changes). For a simple skill, this is sufficient.	3 / 3
Progressive Disclosure	For a simple, single-purpose skill under 80 lines with no need for external references, the content is well-organized into logical sections (synopsis, flags, formats, examples, gotchas) that are easy to scan and navigate.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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: 5 days ago

Table of Contents

Discovery Implementation Validation

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.