CtrlK
BlogDocsLog inGet started
Tessl Logo

trpc-fullstack

Build end-to-end type-safe APIs with tRPC — routers, procedures, middleware, subscriptions, and Next.js/React integration patterns.

60

Quality

70%

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/trpc-fullstack/SKILL.md

The canonical home for this skill is trpc-fullstack in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive, highly actionable tRPC skill with excellent executable code examples covering the full stack from server setup to client components. Its main weaknesses are verbosity — the overview, 'when to use,' and core concepts sections explain things Claude already knows — and the monolithic structure that would benefit from splitting detailed examples and advanced topics into separate files. The workflow is well-sequenced but lacks explicit verification checkpoints.

Suggestions

Remove or drastically shorten the 'Overview,' 'When to Use This Skill,' and 'Core Concepts' sections — Claude already knows what tRPC is, what routers/procedures are, and when to use type-safe APIs.

Split the content into multiple files: keep SKILL.md as a concise overview with the setup steps, and move detailed examples (subscriptions, SSR caller, mutation patterns) into an EXAMPLES.md or PATTERNS.md file.

Add a brief verification step after Step 6 (e.g., 'Test: `curl http://localhost:3000/api/trpc/post.list?input={}` should return a valid response') to improve workflow clarity.

DimensionReasoningScore

Conciseness

The skill is quite long (~350+ lines) and includes some unnecessary explanation (e.g., 'Overview' section explaining what tRPC is, 'When to Use This Skill' section with 5 bullets, 'Core Concepts' section explaining routers/procedures/context/middleware). Claude already knows what tRPC is and how it works. The code examples are valuable but the surrounding prose could be significantly tightened.

3 / 5

Actionability

Excellent actionability — every step includes complete, executable TypeScript code with proper imports, type annotations, and realistic patterns (cursor-based pagination, cache invalidation, auth middleware, server-side callers). The examples cover all major use cases: queries, mutations, subscriptions, SSR, and client setup.

5 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced and logically ordered from installation through client setup. However, there are no explicit validation checkpoints (e.g., 'verify the server starts,' 'test the endpoint before proceeding'). Since this isn't a destructive/batch operation, the missing validation doesn't cap the score at 3, but adding verification steps would improve it.

4 / 5

Progressive Disclosure

The content is entirely self-contained in a single file with no bundle files. At ~350+ lines with detailed code examples for routers, context, middleware, subscriptions, client setup, and multiple component examples, this would benefit from splitting into separate files (e.g., SUBSCRIPTIONS.md, EXAMPLES.md, MIDDLEWARE.md). The 'Related Skills' and 'Additional Resources' sections provide external references but the core content is monolithic.

3 / 5

Total

15

/

20

Passed

Description

70%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 effectively identifies the tRPC domain with good specificity around its core constructs (routers, procedures, middleware, subscriptions) and framework integrations. Its main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know precisely when to select this skill. The technology-specific focus gives it excellent distinctiveness.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about tRPC, type-safe APIs, remote procedure calls in TypeScript, or integrating tRPC with Next.js or React.'

Include related terms users might mention such as 'zod validation', 'tanstack query', 'React Query', or 'TypeScript API' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific concepts: routers, procedures, middleware, subscriptions, and Next.js/React integration patterns. These are concrete tRPC constructs, though it could be more detailed about what actions are performed with each (e.g., 'create routers', 'define input validation', 'handle errors').

4 / 5

Completeness

The 'what' is clearly stated — building type-safe APIs with tRPC including specific constructs. However, there is no explicit 'when' clause (e.g., 'Use when the user asks about tRPC setup, type-safe API design, or React Query integration'). Per rubric guidelines, missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'tRPC', 'routers', 'procedures', 'middleware', 'subscriptions', 'Next.js', 'React', 'type-safe APIs', and 'end-to-end'. Missing some common user phrases like 'RPC', 'API routes', 'server functions', 'zod validation', or 'tanstack query' which are closely associated with tRPC usage.

4 / 5

Distinctiveness Conflict Risk

tRPC is a very specific technology with a clear niche. The mention of routers, procedures, middleware, and subscriptions in the tRPC context makes this highly distinct from general API skills, REST API skills, or GraphQL skills. Minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.