CtrlK
BlogDocsLog inGet started
Tessl Logo

backend-dev-guidelines

You are a senior backend engineer operating production-grade services under strict architectural and reliability constraints. Use when routes, controllers, services, repositories, express middleware, or prisma database access.

56

Quality

63%

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/AI-Agents-Safe-Coding-Skills/skills/backend-dev-guidelines/SKILL.md

The canonical home for this skill is backend-dev-guidelines in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a strong, actionable doctrine with concrete code, explicit anti-patterns, and a validation checklist, making it highly usable. It is slightly over-explained in places and carries a duplicated section, which keeps conciseness at the midpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient with bullet lists and tight code snippets, but includes unnecessary framing ('This skill defines how backend code must be written, not merely suggestions'), a somewhat elaborate BFRI section, and a duplicated 'When to Use' section that could be trimmed.

3 / 5

Actionability

It provides concrete, mostly executable TypeScript examples for routes, BaseController, Sentry, unifiedConfig, Zod, DI, and asyncErrorWrapper, plus explicit ❌/✅ patterns, a directory tree, and a naming table, with only minor gaps where snippets are illustrative rather than full runnable files.

4 / 5

Workflow Clarity

A BFRI pre-flight gate, numbered doctrine, and an Operator Validation Checklist give a clear sequence with explicit checkpoints; the checklist is post-hoc rather than a mid-process validate→fix→retry loop, leaving minor gaps for data-touching operations.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a single well-organized SKILL.md with clearly labeled sections, so the absence of external references is appropriate; minor content like the BFRI table and integration list is inlined where it could optionally be split.

4 / 5

Total

15

/

20

Passed

Description

60%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 signals its backend niche with solid trigger terms and an explicit 'Use when' clause, but leads with a second-person persona statement instead of concrete actions, hurting specificity. Rewriting in third person with enumerated actions would lift it across the board.

Suggestions

Rewrite in third person and lead with concrete actions (e.g. 'Builds and refactors Node.js/Express backend code following a routes→controllers→services→repositories layering.') instead of the 'You are a senior backend engineer' persona.

Add natural trigger synonyms users actually say, such as 'API endpoints', 'TypeScript', 'Node.js', and 'database access', to broaden keyword coverage.

Make the 'when' clause more task-oriented (e.g. 'Use when creating or refactoring API routes, services, repositories, middleware, or Prisma data access') rather than listing nouns.

DimensionReasoningScore

Specificity

The description frames a persona ('You are a senior backend engineer operating production-grade services') with abstract constraints rather than listing concrete actions, and the rubric mandates a -1 specificity penalty for second-person ('You are') voice, pulling an already-weak action list down to 1.

1 / 5

Completeness

It provides both a 'what' (senior backend engineer on production services under architectural/reliability constraints) and an explicit 'when' ('Use when routes, controllers...'), though the 'what' is persona-framed and the trigger list could be more specific.

4 / 5

Trigger Term Quality

It includes several natural terms users say ('routes, controllers, services, repositories, express middleware, prisma database access'), with good coverage though missing common synonyms like 'API', 'endpoints', 'TypeScript', or 'Node'.

4 / 5

Distinctiveness Conflict Risk

The Node/Express/Prisma layered-backend niche with concrete trigger terms is mostly distinct with only minor overlap risk against general backend or related guidelines skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.