nushell-usage
Essential patterns, idioms, and gotchas for writing Nushell code. Use when writing Nushell scripts, functions, or working with Nushell's type system, pipelines, and data structures. Complements plugin development knowledge with practical usage patterns.
84
81%
Does it follow best practices?
Impact
85%
1.02xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
82%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 well-structured with a clear 'Use when' clause and good trigger terms specific to Nushell. Its main weakness is that the 'what' portion relies on abstract meta-terms ('patterns, idioms, gotchas') rather than listing concrete capabilities, and it could be more distinctive by specifying exactly what kinds of patterns or tasks it covers.
Suggestions
Replace abstract terms like 'patterns, idioms, and gotchas' with concrete actions such as 'write custom commands, handle errors, manipulate tables, work with closures and blocks'.
Sharpen distinctiveness by clarifying the boundary with the plugin development skill more explicitly, e.g., 'Use for general Nushell scripting, not for building Nushell plugins'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Nushell) and mentions some areas like 'type system, pipelines, and data structures,' but uses abstract terms like 'patterns, idioms, and gotchas' rather than listing concrete actions (e.g., 'write custom commands, handle errors, manipulate tables'). | 2 / 3 |
Completeness | Clearly answers both 'what' (patterns, idioms, and gotchas for writing Nushell code) and 'when' (explicit 'Use when writing Nushell scripts, functions, or working with Nushell's type system, pipelines, and data structures'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Nushell scripts', 'Nushell functions', 'Nushell's type system', 'pipelines', 'data structures'. These are terms a user would naturally use when seeking help with Nushell coding. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'complements plugin development knowledge' helps distinguish it from a plugin-focused skill, but terms like 'scripts', 'functions', 'pipelines', and 'data structures' are broad enough to potentially overlap with general shell scripting or other Nushell-related skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality Nushell patterns reference that excels at conciseness and actionability. Every section provides executable code with clear right/wrong annotations, and it focuses on non-obvious gotchas (pipeline input vs parameters, mutable variable capture, row conditions vs closures) that genuinely add value beyond what Claude would know. The main areas for improvement are the lack of bundle files to support the referenced advanced topics, and the content length could benefit from splitting some sections into reference files.
Suggestions
Provide the referenced bundle files (references/advanced-patterns.md and references/type-system.md) to support the progressive disclosure structure
Consider moving some of the longer reference sections (e.g., full iteration patterns, row conditions vs closures) into separate reference files to keep the main SKILL.md more focused on critical patterns and gotchas
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining basic concepts Claude already knows (like what Nushell is or what pipelines are), jumps straight into patterns with executable examples, and every section earns its place. The critical distinctions section immediately highlights non-obvious gotchas rather than teaching basics. | 3 / 3 |
Actionability | Nearly every pattern includes fully executable Nushell code with correct syntax, clear ✅/❌ annotations showing right vs wrong approaches, and concrete examples with expected outputs. The code is copy-paste ready and covers a comprehensive range of operations. | 3 / 3 |
Workflow Clarity | This is primarily a reference/patterns skill rather than a multi-step workflow skill, so explicit validation checkpoints are less critical. However, the content is well-sequenced within sections (e.g., the pipeline input vs parameters section builds logically). It lacks explicit feedback loops or validation steps for the more complex patterns like module creation or error handling chains, keeping it at a 2. | 2 / 3 |
Progressive Disclosure | The skill references two advanced files (references/advanced-patterns.md and references/type-system.md) with clear signaling, and links to external resources. However, no bundle files were provided, so these references cannot be verified. The main content itself is quite long (~300 lines) and some sections like the full iteration patterns or row conditions vs closures could potentially be split into reference files for better organization. | 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 | |
- Repository
- YPares/agent-skills
- Commit
d2b7dff
- 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.