Look up help for a nu command using the nudoccommand MCP tool. This allows the user and Claude to retreive information about a command within the conversation. It also ensures Claude and the user are operating on the same information about the command itself.
EnglishThis skill is used to inspect the structure of a nu expression. It surfaces the data's described type, it's length (if applicable), and a sample of the value. The sample will contain the raw value itself for non-enumerable types, otherwise it will contain the first three values of the enumerable.
EnglishUse when writing Nushell iteration, conditionals, or error handling — for/each/reduce/any/all/take while, if/match, try/catch, the ? postfix operator. Especially relevant when choosing between for (env-propagating) and each (isolated), or when an error path needs to skip vs surface vs default. Trigger phrases: "iterate", "loop", "filter", "map", "reduce", "for loop", "try catch", "error handling", "match", "conditional".
EnglishUse when writing Nushell code that touches $env — setting or reading environment variables, persisting env across calls, scoping env to a closure, or debugging why an env mutation isn't visible somewhere. Covers do --env, with-env, the for vs each env-propagation distinction, and Nushell's automatic env vars. Trigger phrases: "env mutation", "$env", "scope", "load-env", "with-env", "do --env", "env doesn't propagate", "auto env var".
EnglishUse when organizing Nushell code into reusable units — writing a .nu file as a module, exporting commands with export def, setting up shared env via export-env, defining a module's main command, or importing/using another module with use. Trigger phrases: "nu module", "reusable nu code", "export def", "use foo.nu", "nu script organization", "module main command".
EnglishUse when writing or transforming Nushell records (key-value structures) or tables — including $env manipulation, record literals, column projection with select/reject, building records from iterables, or any time keys/values/columns are being added, removed, filtered, or restructured. Trigger phrases: "record", "table", "key/value", "select column", "build a record", "filter columns", "transform $env".
EnglishUse when manipulating strings in Nushell — parsing structured text with parse '{a} {b}', interpolating with $"...", splitting/joining/replacing, converting between strings and structured formats (json/csv/yaml/toml), or any string operation that bash would handle with sed/awk/grep. Trigger phrases: "parse string", "split", "join", "str replace", "string interpolation", "regex", "from csv", "from json string".
EnglishIncludes Command Help, Inspect Shape, Nushell Control Flow, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Command Help
Look up help for a nu command using the nudoccommand MCP tool. This allows the user and Claude to retreive information about a command within the conversation. It also ensures Claude and the user are operating on the same information about the command itself.
Inspect Shape
This skill is used to inspect the structure of a nu expression. It surfaces the data's described type, it's length (if applicable), and a sample of the value. The sample will contain the raw value itself for non-enumerable types, otherwise it will contain the first three values of the enumerable.
Nushell Control Flow
Use when writing Nushell iteration, conditionals, or error handling — for/each/reduce/any/all/take while, if/match, try/catch, the ? postfix operator. Especially relevant when choosing between for (env-propagating) and each (isolated), or when an error path needs to skip vs surface vs default. Trigger phrases: "iterate", "loop", "filter", "map", "reduce", "for loop", "try catch", "error handling", "match", "conditional".
Nushell Env Scoping
Use when writing Nushell code that touches $env — setting or reading environment variables, persisting env across calls, scoping env to a closure, or debugging why an env mutation isn't visible somewhere. Covers do --env, with-env, the for vs each env-propagation distinction, and Nushell's automatic env vars. Trigger phrases: "env mutation", "$env", "scope", "load-env", "with-env", "do --env", "env doesn't propagate", "auto env var".
Nushell Modules
Use when organizing Nushell code into reusable units — writing a .nu file as a module, exporting commands with export def, setting up shared env via export-env, defining a module's main command, or importing/using another module with use. Trigger phrases: "nu module", "reusable nu code", "export def", "use foo.nu", "nu script organization", "module main command".
Nushell Records
Use when writing or transforming Nushell records (key-value structures) or tables — including $env manipulation, record literals, column projection with select/reject, building records from iterables, or any time keys/values/columns are being added, removed, filtered, or restructured. Trigger phrases: "record", "table", "key/value", "select column", "build a record", "filter columns", "transform $env".
Nushell Strings
Use when manipulating strings in Nushell — parsing structured text with parse '{a} {b}', interpolating with $"...", splitting/joining/replacing, converting between strings and structured formats (json/csv/yaml/toml), or any string operation that bash would handle with sed/awk/grep. Trigger phrases: "parse string", "split", "join", "str replace", "string interpolation", "regex", "from csv", "from json string".
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Command Help skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.