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

76%

Does it follow best practices?

Impact

95%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%Scale 1-5

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

This is a solid, well-structured skill that provides actionable Nx task-running guidance with concrete commands and examples. It efficiently covers the key use cases (single task, multiple tasks, affected tasks) with appropriate flags. Minor improvements could include showing package manager detection in practice and adding brief error-handling guidance.

Suggestions

Add a brief concrete example showing how to detect the package manager from the lockfile (e.g., 'If yarn.lock exists, prefix with yarn; if pnpm-lock.yaml, use pnpx').

Trim the opening sentence ('You can run tasks with Nx in the following way') as it adds no value — jump straight into the content.

Dimension	Reasoning	Score
Conciseness	Generally efficient and assumes Claude's competence. Minor verbosity in a few spots (e.g., 'You can run tasks with Nx in the following way' preamble, explaining what `project` means), but mostly lean and well-targeted.	4 / 5
Actionability	Provides concrete, copy-paste ready commands with clear examples for single tasks, run-many, and affected. Minor gap: no example of detecting the package manager from lockfile or showing the npx/pnpx prefix in action, which is mentioned but left abstract.	4 / 5
Workflow Clarity	Clear logical sequence from discovering tasks to running single/multiple/affected tasks, with useful flags at the end. This is not a destructive/batch operation requiring validation checkpoints, so the lack of explicit feedback loops is acceptable. Minor gap: no guidance on interpreting task output or handling failures beyond --nxBail.	4 / 5
Progressive Disclosure	Well-structured with clear section headers and a logical progression from simple to complex. The --help hint for deeper exploration is a good progressive disclosure pattern. No bundle files exist, and the content length is appropriate for a single file, though a separate reference for all available flags or plugin-specific configuration could improve it slightly.	4 / 5
	Total	16 / 20 Passed

Description

78%Scale 1-5

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 description with a clear USE WHEN clause that explicitly defines trigger scenarios. The Nx workspace domain is well-identified, and the listed task types (build, test, lint, serve) provide good trigger coverage. The main weakness is the slightly vague lead-in 'Helps with running tasks' and missing some Nx-specific terminology that power users might use.

Suggestions

Replace 'Helps with' with a more specific action verb like 'Executes and configures tasks' to increase specificity.

Add Nx-specific trigger terms like 'nx run', 'nx affected', 'monorepo', or 'project graph' to improve keyword coverage for power users.

Dimension	Reasoning	Score
Specificity	Names the domain (Nx workspace) and lists several concrete actions (build, test, lint, serve, run tasks), but 'Helps with running tasks' is somewhat vague as a lead-in and doesn't describe how it helps (e.g., configuring, executing, debugging).	3 / 5
Completeness	Clearly answers both 'what' (running tasks in an Nx workspace) and 'when' (explicit 'USE WHEN' clause with concrete trigger scenarios: execute build, test, lint, serve, or other workspace tasks).	5 / 5
Trigger Term Quality	Includes good natural keywords like 'build', 'test', 'lint', 'serve', 'Nx workspace', and 'tasks'. Missing some variations like 'nx run', 'nx affected', 'monorepo', or specific Nx terminology users might use.	4 / 5
Distinctiveness Conflict Risk	The Nx workspace focus provides good distinctiveness from general build/test skills. However, terms like 'build', 'test', 'lint', 'serve' are generic enough that they could overlap with non-Nx build tool skills if present.	4 / 5
	Total	16 / 20 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: mlbymolly/ruview-t4est
Path: .agents/skills/nx-run-tasks/SKILL.md
Commit: 4d1716f

Reviewed: 3 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.