CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trpc-fullstack

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

Quality

78%

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

Quality

Content

78%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.

Excellent actionable content: complete, executable code organized in a clear step-by-step setup flow with practical pitfalls and best-practice guidance. The main gaps are mild over-explanation of framework basics and a completely flat structure — no reference files — in a skill long enough to benefit from splitting.

Suggestions

Move the Examples section (PostList, CreatePost, subscriptions router) into a references/EXAMPLES.md and keep one short representative example inline in SKILL.md.

Trim the Overview and "Core Concepts" sections to a few lines each — Claude already knows what routers, middleware, and type safety are; keep only the tRPC-specific details (e.g. the dual context factories).

Add a validation checkpoint after Step 7 (e.g. "run `tsc --noEmit` and confirm client autocompletion for post.list appears") to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is code-first and dense with almost no filler — each step introduces a complete file rather than prose. Minor over-explanation remains: the Overview re-explains what tRPC is and why type safety matters, "Core Concepts" defines router/procedure basics Claude already knows, and Examples 1-2 include boilerplate React markup that could be trimmed. This matches the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the fully lean anchor 5.

4 / 5

Actionability

Every section provides complete, copy-paste-ready code: an install command, full source files with imports and paths (trpc.ts, context.ts, routers, root, route handler, client provider), and working examples covering the common cases — query with pagination, mutation with cache invalidation, server-side caller, and subscriptions. This matches the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

A clear 7-step sequence (install → instance → context factories → auth middleware → routers → root router/handler → client) with a consistent through-line, plus a Common Pitfalls section of Problem/Solution pairs that functions as error-recovery feedback. Not 5 because there are no explicit validation checkpoints (e.g. verifying the dev server compiles or types flow to the client after setup); not 3 because the sequence is coherent and recovery guidance for the known failure modes is present.

4 / 5

Progressive Disclosure

The skill ships as a single ~460-line SKILL.md with no references/, scripts/, or assets/ bundle files, so all content — including the ~120-line Examples section and the subscription deep-dive — is inlined. Section headers and the "Related Skills"/"Additional Resources" links provide some structure and navigation, but content that would benefit from being split into reference files sits inline, matching the 'some structure but content that should be separate is inline' anchor. It is not 2 because the file is well-sectioned and navigable, and not 4 because there are no one-level-deep reference files at all.

3 / 5

Total

16

/

20

Passed

Description

70%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, specific description with a clear niche and good natural keywords, weakened only by the absence of an explicit "Use when..." trigger clause. Adding that clause would raise completeness and make triggering more reliable.

Suggestions

Append an explicit trigger clause such as "Use when building or refactoring tRPC routers and procedures, wiring tRPC into a Next.js app, or migrating a REST/GraphQL API to tRPC."

Include one or two natural user phrasings (e.g. "tRPC setup", "end-to-end types") in the description to broaden trigger term coverage.

Mention input validation with Zod since it is a core part of the skill's procedures and would help distinguish it from generic Next.js API skills.

DimensionReasoningScore

Specificity

"Build end-to-end type-safe APIs with tRPC — routers, procedures, middleware, subscriptions, and Next.js/React integration patterns" names the domain and enumerates several concrete capabilities (routers, procedures, middleware, subscriptions, Next.js/React integration), matching the 'lists several specific actions; minor gaps in coverage' anchor. Not 5 because the enumerated items are components rather than multiple distinct action verbs, and coverage items like error formatting or input validation are absent.

4 / 5

Completeness

The description clearly answers 'what' (build end-to-end type-safe APIs with tRPC and its component patterns), but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3. The 'when' is only weakly implied by the mention of tRPC and Next.js/React.

3 / 5

Trigger Term Quality

"tRPC", "type-safe APIs", "Next.js", "React", "subscriptions", and "middleware" are terms users would naturally say when needing this skill, giving good keyword coverage. Not 5 because a few natural variations users might say (e.g. "tRPC setup", "server/client types", "create-t3-app") are missing; not 3 because the primary niche term and its surrounding vocabulary are all present.

4 / 5

Distinctiveness Conflict Risk

"tRPC" is a clear niche identifier — few other skills would trigger on these terms, and the enumerated capabilities (routers, procedures, subscriptions) are tRPC-specific, giving minimal conflict risk. It clearly matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

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.

Validation — 15 / 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

Path

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