performance-lint-rules

Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxc_linter/src/rules/ or when explicitly auditing those rules for performance improvements.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

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

A focused, well-structured instruction-only skill that delivers concrete Rust-specific performance guidance without padding and assumes Claude's competence. It could be strengthened with a complete worked example and an explicit validation step in its embedded node-kind workflow.

Suggestions

Add one small complete worked example (e.g. a before/after 'run' entry point with an AstKind match and the follow-up 'cargo lintgen' command) to push actionability from concrete hints to copy-paste-ready.

Make the embedded node-kind workflow's verification explicit by framing 'assert_rule_runs_on_node_types' coverage as a validate-then-proceed checkpoint with a re-run instruction on failure.

Dimension	Reasoning	Score
Conciseness	Lean and efficient prose that assumes Claude's familiarity with AST nodes, lintgen, and regex semantics; every section and bullet earns its place with only the rationale needed to apply the guidance, matching anchor 5.	5 / 5
Actionability	Provides concrete, near-executable guidance via specific APIs and commands (e.g. 'ctx.scoping().get_binding(scope_id, name)', 'cargo lintgen', 'as_bytes().array_windows()'), but lacks a complete worked code example, placing it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	Mostly a reference/guidelines doc, but the top-level-node-kind section embeds a clear sequence (change node kinds -> run 'cargo lintgen' -> add 'assert_rule_runs_on_node_types' coverage) with a verification-leaning step; minor checkpoint gaps keep it at anchor 4.	4 / 5
Progressive Disclosure	Around 50 lines with no need for external references, organized into clear, well-labeled section headers, which per the simple-skills note qualifies for anchor 5 on progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

82%Weight 40%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.

A tightly scoped, well-constructed description that clearly answers both what it does and when to use it, with strong distinctiveness and natural trigger phrasing. Its only weakness is modest action specificity, naming just two activities rather than a comprehensive list.

Dimension	Reasoning	Score
Specificity	Names the domain ('Oxc linter rule implementations') and 1-2 concrete actions ('reviewing Rust rule code', 'auditing those rules for performance improvements'), but does not enumerate several specific actions, so it sits at the anchor-3 level rather than 4.	3 / 5
Completeness	Explicitly states both what ('Performance review guidance for Oxc linter rule implementations') and when ('Use only when reviewing Rust rule code under crates/oxc_linter/src/rules/ or when explicitly auditing those rules for performance improvements'), mirroring the anchor-5 example.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would say ('reviewing Rust rule code', 'auditing those rules for performance improvements', 'Oxc linter') plus a concrete path trigger, but is missing a few common synonyms, matching the anchor-4 example.	4 / 5
Distinctiveness Conflict Risk	Scoped to a very narrow niche tied to a specific crate path and tool, giving it distinct triggers with minimal overlap risk, matching the anchor-5 example.	5 / 5
	Total	17 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: oxc-project/oxc
Path: .agents/skills/performance-lint-rules/SKILL.md
Commit: 1aa5ec1

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