Strip directory and suffix from filenames. Use when extracting just the filename from a path, or removing file extensions.
76
95%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 solid, concise description that clearly communicates a narrow utility task. It has explicit trigger guidance and uses natural keywords. The only minor weakness is that the capability description could be slightly more detailed about edge cases or specific behaviors.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Describes the domain (filenames/paths) and a couple of actions (strip directory, strip suffix), but doesn't list multiple concrete actions beyond those two. It's more specific than vague but not comprehensively detailed. | 2 / 3 |
Completeness | Clearly answers both 'what' (strip directory and suffix from filenames) and 'when' (Use when extracting just the filename from a path, or removing file extensions), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'filename', 'path', 'file extensions', 'directory', 'suffix'. These cover the common ways users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — stripping directory paths and suffixes from filenames is a narrow, well-defined task unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill for a simple utility command. It is concise, fully actionable with executable examples and expected outputs, and includes genuinely useful gotchas that go beyond what Claude might already know (e.g., the parameter expansion alternative, trailing slash behavior). The structure is clean and appropriate for the scope of the topic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It documents flags in a compact table, provides examples without unnecessary explanation, and the Gotchas section contains genuinely non-obvious information (like the parameter expansion alternative and trailing slash behavior). No concepts are over-explained. | 3 / 3 |
Actionability | Every example is a concrete, copy-paste ready bash command with expected output clearly shown. Common patterns like script name extraction and shell variable assignment are included, making this immediately usable. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose utility skill with no multi-step process. The single action (stripping directory/suffix) is unambiguous, and the examples clearly demonstrate each flag variation. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a simple single-purpose skill under 50 lines of substantive content with no need for external references, the content is well-organized into logical sections (Synopsis, Flags, Examples, Gotchas) that are easy to scan and navigate. | 3 / 3 |
Total | 12 / 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.
bb1f07d
Table of Contents
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.