CtrlK
BlogDocsLog inGet started
Tessl Logo

lint-new

Create a new ESLint rule with tests for eslintPluginScraps. Use when asked to "create a lint rule", "add an eslint rule", "scaffold a rule", "write a new scraps rule", or "new design system lint rule". Covers rule creation, test authoring, registration, and autofix implementation.

96

1.14x
Quality

96%

Does it follow best practices?

Impact

96%

1.14x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

The body is a tight, action-oriented workflow that assumes competence, leans on real bundled references for depth, and provides copy-paste templates and verification commands. Its only soft spot is workflow clarity, where validation is present but not framed as an explicit validate→fix→retry feedback loop.

Suggestions

Framing the test step as an explicit feedback loop ('run tests → if failures, fix and re-run → only proceed when green') would lift workflow clarity to the top anchor, especially for a code-generation skill.

The autofix 'Do NOT autofix when' list could note how to surface a non-fixable case to the user (e.g., report without a fix) so Claude handles the ambiguous case concretely rather than silently skipping.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — utility tables, copy-paste code templates, and direct commands with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Fully executable guidance: exact file paths, complete TypeScript rule and test templates, the pnpm test-ci command, and a concrete fixer API with method variants — copy-paste ready for the common cases.

5 / 5

Workflow Clarity

Clear four-step sequence (archetype → utilities → create → register) with a verify checkpoint via pnpm test-ci in Steps 3 and 4, but the validate step is 'run tests' rather than an explicit validate→fix→retry feedback loop, leaving it just below the top anchor.

4 / 5

Progressive Disclosure

Clear overview in SKILL.md with well-signaled one-level-deep references (rule-archetypes.md, schema-patterns.md, style-collector-guide.md), all real bundle files, each loaded conditionally via a decision table — easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

100%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.

The description is a strong, concise trigger: it names the precise domain, enumerates the four concrete capabilities it covers, and provides five natural user phrases as explicit triggers. It cleanly satisfies the 'what' and 'when' requirements with no padding.

DimensionReasoningScore

Specificity

Names the domain (eslintPluginScraps rule creation) and lists multiple concrete actions — 'rule creation, test authoring, registration, and autofix implementation' — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (Create a new ESLint rule with tests for eslintPluginScraps) and 'when' (Use when asked to...) with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say: 'create a lint rule', 'add an eslint rule', 'scaffold a rule', 'write a new scraps rule', 'new design system lint rule' — multiple synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche tied to a specific plugin (eslintPluginScraps) with distinct scaffolding triggers; minimal overlap risk with unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getsentry/sentry
Reviewed

Table of Contents

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.