Name: trpc-fullstack
Rating: 60 (1 reviews)
Author: administrakt0r

trpc-fullstack

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/trpc-fullstack/SKILL.md

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

Quality

Content

71%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 a clear step sequence, but it is a monolithic single file with no progressive disclosure and carries some conceptual padding Claude already knows. Splitting advanced material into reference files and trimming the overview would lift the weaker dimensions.

Suggestions

Move advanced/long-form material (e.g. the WebSocket subscription example, the full postRouter) into one-level-deep reference files under references/ and link to them from the body.

Trim the Overview and Core Concepts to assume Claude's knowledge of tRPC and focus only on the non-obvious decisions (e.g. the App Router vs Pages Router context split).

Add an explicit validation checkpoint after Step 6 (e.g. 'Start the dev server and hit /api/trpc to confirm the handler responds') to reach the top workflow-clarity anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-heavy, but the Overview and Core Concepts sections re-explain concepts Claude already knows (what a router/procedure is, 'think: endpoints', what tRPC is), which keeps it at the mostly-efficient anchor rather than lean.	3 / 5
Actionability	Seven sequenced steps plus four examples provide fully executable, copy-paste-ready TypeScript covering install, context, middleware, routers, handler mounting, client setup, queries, mutations, SSR callers, and subscriptions.	5 / 5
Workflow Clarity	Steps 1-7 are clearly numbered and ordered, but there are no explicit validation/verification checkpoints (e.g. 'start the server and confirm the endpoint responds'); the Common Pitfalls section provides error-recovery guidance that partially compensates.	4 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ absent) and ~460 lines are inlined into a single SKILL.md; section headers give internal structure, but content like the full subscription example and extended router code that could be offloaded to one-level-deep references is all inline.	3 / 5
	Total	15 / 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.

The description is specific and clearly niched to tRPC with good trigger keywords, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete use-when triggers would round it out.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when building TypeScript full-stack apps with tRPC, Next.js/React monorepos, or migrating REST/GraphQL to tRPC.'

Reframe the capability list as concrete verbs (e.g. 'define routers, validate inputs with Zod, chain auth middleware, wire real-time subscriptions') to nudge specificity toward 5.

Add a couple of natural synonyms users say ('type safety', 'monorepo') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('type-safe APIs with tRPC') and several concrete components ('routers, procedures, middleware, subscriptions, and Next.js/React integration patterns'), but lists capabilities as nouns rather than verbs and omits items like context factories and Zod validation, so it sits just below the comprehensive 5 anchor.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes the natural trigger 'tRPC' plus 'type-safe APIs' and 'Next.js/React', giving good keyword coverage a user would actually say, though common variations like 'monorepo' or the exact phrase 'type safety' are absent.	4 / 5
Distinctiveness Conflict Risk	The 'tRPC' niche is highly specific and distinct from other API/framework skills, giving a clear niche with minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/trpc-fullstack/SKILL.md
Commit: debb2ec

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.