CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

backend-dev-guidelines

Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).

Quality

79%

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 ./skills_all/backend-dev-guidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured, highly actionable backend guide with concrete code patterns and checklists, weakened by padding (HTTP status table, status metadata, duplicated blocks) and a progressive-disclosure failure: all seven referenced resource files are absent from the bundle and one link path is inconsistent, so the promised deep-dive navigation leads nowhere. Tightening the inline bulk and shipping the referenced files would raise both conciseness and organization.

Suggestions

Remove the 'HTTP Status Codes' table and the trailing 'Skill Status / Line Count / Progressive Disclosure' metadata block, and merge the two overlapping import-path tables into one — all restate knowledge Claude already has or duplicate content already in the body.

Ship the seven referenced resources/*.md files (architecture-overview, routing-and-controllers, services-and-repositories, middleware-guide, database-patterns, configuration, testing-guide) and fix the inconsistent link at 'See architecture-overview.md' to use the resources/ prefix like every other reference.

Move the full directory-structure listings and the detailed 'What Goes Where' import matrix into the appropriate resource files, keeping SKILL.md to the checklists, core principles, and navigation guide.

DimensionReasoningScore

Conciseness

The body is mostly dense, repo-specific guidance, but includes several padded sections: an 'HTTP Status Codes' table (200=Success, 400=Bad Request) explaining concepts Claude already knows, a trailing 'Skill Status: COMPLETE ✅ / Line Count: ~540 lines' metadata block, a duplicated observability import block (lines ~328 and ~451), and two overlapping import-path tables ('Maps To / Use For' and 'What Goes Where'). Not score 2 because the bulk is genuinely actionable rather than explanation of known concepts.

3 / 5

Actionability

Concrete ❌/✅ code patterns (tRPC delegation, env.mjs, Prisma projectId filtering, parameterized ClickHouse queries) and real test helpers (makeZodVerifiedAPICall, prepare()/caller, vitest streams) make most guidance executable. Not score 5 because several snippets are placeholders ('// 200 lines of logic here', '// Operation here', 'filter: [...]') and no full withMiddlewares/createAuthedProjectAPIRoute route example is shown.

4 / 5

Workflow Clarity

Three checklists (tRPC feature, public API endpoint, queue processor) give clear step sequences with exact file locations, and each includes a Tests step plus the queue checklist's error-classification guidance. Not score 5 because verification is listed as a task rather than an explicit checkpoint — no 'run jest/vitest to verify before proceeding' command or feedback loop is stated.

4 / 5

Progressive Disclosure

Navigation is well-signaled (Navigation Guide table plus a Resource Files section with one-line descriptions, references only one level deep), but none of the seven referenced resources/*.md files exist in the bundle, one link at 'See architecture-overview.md' drops the resources/ prefix, and ~555 lines of directory listings and import tables are inlined in SKILL.md. This is real structure with real organization problems — above anchor 2's 'minimal structure/buried references', below anchor 4 because the promised reference files are missing and paths are inconsistent.

3 / 5

Total

14

/

20

Passed

Description

87%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 strong description that explicitly states both what the skill covers and when to use it, with a well-defined Langfuse-specific niche and rich technology keywords. Its weaknesses are limited action-verb variety and omission of several natural trigger terms (middleware, authentication, background jobs) that the body itself lists as activation conditions.

DimensionReasoningScore

Specificity

Names many concrete artifacts and technologies ('creating tRPC routers, public API endpoints, BullMQ queue processors, services', 'Prisma database access, ClickHouse analytics queries', 'traceException error handling'). Not score 5 because the action verbs are limited to 'creating/working with/covers' — it enumerates domains more than distinct concrete actions; not score 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers what ('Comprehensive backend development guide... Covers layered architecture..., dual database system..., projectId filtering..., observability patterns, and testing strategies') and when ('Use when creating tRPC routers... or working with tRPC procedures, Next.js API routes, Prisma database access...') with concrete trigger phrases, matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Good keyword coverage with natural variations ('tRPC routers' and 'tRPC procedures', 'public API endpoints' and 'Next.js API routes', 'Redis queues', 'Zod v4 validation', 'env.mjs configuration'). Not score 5 because common natural phrasings users would say are missing — 'middleware', 'authentication/authorization', 'background jobs', 'migrations' — which are major activities the body itself covers.

4 / 5

Distinctiveness Conflict Risk

Anchored to a specific niche ('Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo') with repo-specific triggers (BullMQ queue processors, projectId tenant isolation, env.mjs), giving it a clear niche with minimal conflict risk against generic backend or frontend skills.

5 / 5

Total

18

/

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 (564 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 16 missing

Warning

Total

14

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/backend-dev-guidelines/SKILL.md

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.