CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

expressjs-development

Comprehensive Express.js development skill covering routing, middleware, request/response handling, error handling, and building production-ready REST APIs

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/luxor-backend-toolkit/skills/expressjs-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill is highly actionable with comprehensive executable Express.js patterns, but it is a verbose monolithic reference that re-teaches Express basics Claude already knows and fails to progressively disclose content into separate files. Its one external reference is broken (EXAMPLES.md is missing).

Suggestions

Split the monolith: move the API Reference and full examples into separate files (REFERENCE.md, EXAMPLES.md) and link to them one level deep — and create the EXAMPLES.md that the body currently references but does not exist.

Trim Claude-already-knows content: remove the inline basic Express API listing and the redundant full REST API implementations repeated across the Core Concepts, Workflow Patterns, and Examples sections.

Add a sequenced build-and-verify workflow with explicit validation checkpoints (e.g. define routes → run `jest` → fix failures → re-run) so the CRUD/auth patterns carry a feedback loop.

DimensionReasoningScore

Conciseness

The ~1640-line body noticeably re-documents Express concepts Claude already knows (inline API reference listing app.use/res.json, basic routing, repeated full REST API implementations across sections), fitting 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Provides fully executable, copy-paste-ready code covering the common cases (CRUD, JWT auth, express-validator rules, Jest+Supertest tests, helmet/CORS/rate-limit, caching), matching the 'fully executable; copy-paste ready code; specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

Content is organized as a topical reference rather than a sequenced process; a rough topical sequence exists but there are no explicit validation checkpoints or feedback loops (e.g. run tests → fix → re-run), matching the 'steps listed but validation gaps; checkpoints missing or implicit' anchor.

3 / 5

Progressive Disclosure

The body is a monolith that inlines content clearly belonging in separate files (full API reference, examples, best-practice recipes), and the only external reference — 'See EXAMPLES.md' — points to a file that does not exist, fitting 'minimal structure; content that clearly belongs in separate files is inlined'.

2 / 5

Total

12

/

20

Passed

Description

66%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 clearly communicates the skill's scope with specific Express.js capability areas and natural trigger terms, but it omits any explicit 'when to use' guidance, which caps its completeness. Distinctiveness is good thanks to the named framework.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building REST APIs, backend services, microservices, or middleware pipelines with Express.js'.

Include natural synonyms users say ('Node.js backend', 'API server', 'web server') to broaden trigger coverage.

Convert topic-area names into crisp action verbs ('define routes', 'compose middleware pipelines', 'handle errors') to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names the Express.js domain and lists several concrete action areas ('routing, middleware, request/response handling, error handling, and building production-ready REST APIs'), matching the 'several specific actions; minor gaps' anchor; not a 5 because the items are topic-area names rather than crisp executable verbs.

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent trigger guidance; per the rubric, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user terms appear ('Express.js', 'REST APIs', 'routing', 'middleware'), but common synonyms a user might say ('Node.js backend', 'API server', 'web server') are absent, fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

Express.js is a clearly named niche with distinct triggers, but the broad 'development skill' framing leaves minor overlap risk with generic Node.js/backend or REST-API skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1644 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

manutej/luxor-claude-marketplace

Path

plugins/luxor-backend-toolkit/skills/expressjs-development/SKILL.md

Revision

1861cc9

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill