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.

1.02x

Quality

95%

Does it follow best practices?

Impact

85%

1.02x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, token-efficient Nushell reference: dense executable examples with correct/incorrect contrasts, expected outputs inline, and a clean split into two verified one-level reference files. Strong across all dimensions with no significant weaknesses.

Dimension	Reasoning	Score
Conciseness	A lean, code-dense reference that assumes Claude's competence — nearly every section is terse executable snippets with inline comments, avoiding explanation of concepts Claude already knows.	3 / 3
Actionability	Overwhelmingly concrete and copy-paste ready: correct/incorrect (✅/❌) contrasts, named commands, and inline expected outputs like '# Result: ["" "found" ""]' and '# ((1-2)-3)-4 = -8'.	3 / 3
Workflow Clarity	As a single-purpose patterns reference the content is unambiguously organized with sequenced critical distinctions and explicit error-handling patterns (try/catch, complete, error make); the simple-skill allowance applies.	3 / 3
Progressive Disclosure	The body is an overview that points to two real, one-level-deep, verified reference files (references/advanced-patterns.md, references/type-system.md) with clear scope descriptions and easy navigation.	3 / 3
	Total	12 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, well-targeted description that names the Nushell domain, states what it covers, and gives an explicit 'Use when' trigger. The only mild weakness is that it enumerates activity areas rather than concrete discrete actions, keeping specificity at the middle anchor.

Suggestions

Replace the generic 'Essential patterns, idioms, and gotchas' framing with a few concrete verbs/actions (e.g. 'Define typed functions, build pipelines, transform records and tables, handle errors') to lift specificity to the top anchor.

Dimension	Reasoning	Score
Specificity	Names the Nushell domain and several activity areas (scripts, functions, type system, pipelines, data structures) but lists categories rather than multiple discrete concrete actions like 'extract, fill, merge'.	2 / 3
Completeness	Both what ('Essential patterns, idioms, and gotchas for writing Nushell code') and when ('Use when writing Nushell scripts, functions...') are explicitly stated with a clear trigger clause.	3 / 3
Trigger Term Quality	Natural user terms are well covered — 'Nushell scripts', 'functions', 'type system', 'pipelines', 'data structures' — matching the kinds of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Nushell, a distinctive niche with little risk of triggering for unrelated skills; the 'Complements plugin development' note is a mild, non-conflicting hint.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: YPares/agent-skills
Commit: ac633fa

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.