nx-run-tasks

Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.

1.14x

Quality

77%

Does it follow best practices?

Impact

95%

1.14x

Average score across 3 eval scenarios

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/nx-run-tasks/SKILL.md

Quality

Content

87%Scale 1-3

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-crafted, concise skill that provides actionable Nx task-running guidance with concrete commands and examples. Its main weakness is the lack of error handling or validation guidance — there's no mention of what to do when tasks fail, how to interpret output, or how to debug common issues. The structure and progressive disclosure are appropriate for the skill's scope.

Suggestions

Add a brief section on handling task failures — e.g., how to read error output, retry individual tasks, or use --verbose for debugging.

Consider adding a validation step or feedback loop, such as checking task exit codes or reviewing nx run-many summary output to confirm all tasks passed.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It avoids explaining what Nx is or how package managers work, and only includes the note about npx/pnpx/yarn as a practical reminder. Every section delivers actionable information without padding.	3 / 3
Actionability	Provides concrete, copy-paste ready commands throughout (nx run, nx run-many, nx affected, nx show project). Multiple real-world examples with flags and patterns are included, covering common use cases like filtering by project, tag, and pattern.	3 / 3
Workflow Clarity	The skill logically sequences from discovering tasks to running single tasks to running multiple/affected tasks, which is a reasonable flow. However, there are no validation checkpoints or feedback loops — e.g., no guidance on checking task output, handling failures, or verifying results after running tasks.	2 / 3
Progressive Disclosure	For a skill of this size and scope (~50 lines, single concern), the content is well-organized into clear sections with headers. It appropriately suggests --help for deeper exploration rather than inlining all details. No bundle files are needed for this straightforward reference.	3 / 3
	Total	11 / 12 Passed

Description

67%Scale 1-3

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 adequately covers the basics with an explicit 'USE WHEN' clause and domain identification (Nx workspace), which is good. However, it uses vague phrasing ('Helps with') and could be more specific about concrete capabilities beyond listing generic task types. Adding more Nx-specific trigger terms and concrete actions would improve both specificity and distinctiveness.

Suggestions

Replace 'Helps with running tasks' with more specific actions like 'Executes and configures Nx workspace tasks, manages task pipelines, and runs affected commands'.

Add Nx-specific trigger terms such as 'nx run', 'nx affected', 'monorepo', 'project.json', 'nx graph' to improve distinctiveness from generic build tool skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Nx workspace) and lists some actions (build, test, lint, serve, run tasks), but uses 'helps with' which is vague, and 'any other tasks' is a catch-all that reduces specificity.	2 / 3
Completeness	Clearly answers both 'what' (running tasks in an Nx workspace) and 'when' (explicit 'USE WHEN' clause specifying build, test, lint, serve, or other workspace tasks).	3 / 3
Trigger Term Quality	Includes relevant keywords like 'Nx workspace', 'build', 'test', 'lint', 'serve', and 'tasks', but misses common variations users might say such as 'nx run', 'monorepo', 'nx affected', 'project targets', or specific file references like 'project.json'.	2 / 3
Distinctiveness Conflict Risk	The Nx workspace context provides some distinctiveness, but terms like 'build', 'test', 'lint', and 'serve' are very common across many build tools and could overlap with generic CI/CD, npm scripts, or other build system skills.	2 / 3
	Total	9 / 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: whimzyLive/nightshift-ai
Path: skills/nx-run-tasks/SKILL.md
Commit: 8a737ca

Reviewed: about 8 hours 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.