CtrlK
BlogDocsLog inGet started
Tessl Logo

api-generator

Generates Express REST APIs.

54

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./steps/02-skill-with-frontmatter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 content is highly actionable with complete executable code and is reasonably token-efficient, but it lacks validation/feedback steps for its database and file operations and inlines module code that would benefit from being split into reference files.

DimensionReasoningScore

Conciseness

The body is mostly concrete, executable code with little concept-explanation fluff (it does not explain what Express or JWT is), with only minor padding in the "Key Principles" list, fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

It provides complete, copy-paste-ready TypeScript for every module (db.ts, auth.ts, routes.ts, index.ts) covering CRUD, login, export, import, and report endpoints, matching the fully-executable anchor.

5 / 5

Workflow Clarity

A rough sequence exists (Project Setup, per-file code patterns, Key Principles) but there are no validation checkpoints, and because the skill performs database operations the rubric caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

At ~200 lines with all module code inlined in a single SKILL.md and no reference bundle, it has good section headers but keeps content that belongs in separate files inline; the under-50-line exception does not apply, matching the some-structure anchor.

3 / 5

Total

15

/

20

Passed

Description

48%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 concise and names a specific niche, but it is bare: a single generic action and no usage trigger. It is distinguishable yet incomplete as activation guidance.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when the user asks to create or scaffold an Express REST API, build CRUD endpoints, or set up a Node.js backend."

Expand the action beyond the single verb "Generates" to list 2-3 concrete capabilities (e.g. scaffolds project structure, adds CRUD routes, wires JWT auth) to lift specificity.

Include natural synonyms/extensions users say ("endpoints", "Node.js API", "scaffold backend") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Generates Express REST APIs" names the domain and a single generic action ("Generates"), matching the anchor for minimal/generic actions rather than the 1-2 concrete actions required for a 3.

2 / 5

Completeness

It clearly states what the skill does ("Generates Express REST APIs") but has no "Use when..." trigger clause, so per the rubric guideline completeness is capped at 3 for a clear "what" with missing "when".

3 / 5

Trigger Term Quality

It includes relevant keywords a user might say ("Express", "REST", "APIs") but omits common variations/synonyms like "endpoints", "backend", or "Node.js", fitting the anchor for partial keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Express REST APIs" carves out a fairly specific niche with low conflict risk, sitting above the 3 midpoint but below 5 because it lacks the explicit trigger phrasing shown in the anchor-5 example.

4 / 5

Total

12

/

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
jbaruch/tessl-demo
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.