tRPC router architecture, procedure design, and Vertical Slice Architecture patterns. Use when building tRPC APIs, designing procedures, or structuring backend slices.
71
Quality
56%
Does it follow best practices?
Impact
100%
1.47xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/tech-trpc/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with explicit 'Use when' guidance and good trigger terms specific to tRPC development. The main weakness is that the capabilities are described at a conceptual level (architecture, patterns) rather than listing concrete actions the skill enables. The technology-specific focus provides good distinctiveness.
Suggestions
Replace abstract terms like 'architecture' and 'patterns' with concrete actions such as 'create routers, define procedures, implement input validation, structure feature slices'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (tRPC) and mentions 'router architecture, procedure design, and Vertical Slice Architecture patterns' but these are somewhat abstract concepts rather than concrete actions like 'create routers' or 'implement input validation'. | 2 / 3 |
Completeness | Clearly answers both what (tRPC router architecture, procedure design, VSA patterns) and when ('Use when building tRPC APIs, designing procedures, or structuring backend slices') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'tRPC', 'APIs', 'procedures', 'backend slices', 'router'. These are terms developers would naturally use when seeking help with tRPC development. | 3 / 3 |
Distinctiveness Conflict Risk | tRPC is a specific technology with distinct terminology. The combination of 'tRPC', 'procedures', and 'Vertical Slice Architecture' creates a clear niche unlikely to conflict with general API or backend skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is a meta-template about skill usage rather than actual tRPC guidance. It lacks any concrete code examples, router patterns, procedure designs, or VSA implementation details. The troubleshooting and workflow sections are generic boilerplate that could apply to any skill, providing no tRPC-specific value.
Suggestions
Add concrete tRPC router and procedure code examples showing actual patterns (e.g., input validation with Zod, context usage, error handling)
Include specific VSA slice structure examples showing how to organize tRPC procedures within vertical slices
Replace generic workflow steps with tRPC-specific guidance (e.g., 'Define input schema with Zod', 'Create procedure with proper middleware', 'Export from slice router')
Remove or minimize the generic troubleshooting section and replace with tRPC-specific gotchas and solutions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes boilerplate troubleshooting sections that don't add tRPC-specific value. The examples and workflow sections are generic templates rather than domain-specific guidance. | 2 / 3 |
Actionability | No concrete code, commands, or tRPC-specific examples are provided. The content describes what to do abstractly ('Use tech-trpc guidance', 'Apply the skill rules') without showing actual router patterns, procedure definitions, or VSA implementations. | 1 / 3 |
Workflow Clarity | The 3-step workflow is extremely vague ('Identify', 'Apply', 'Validate') with no tRPC-specific steps, validation checkpoints, or concrete actions. It reads as a generic meta-workflow rather than guidance for building tRPC APIs. | 1 / 3 |
Progressive Disclosure | References a rules index file which is appropriate, but the main content provides no substantive overview of tRPC patterns. The skill body itself is mostly meta-content about skill triggering rather than actual tRPC guidance. | 2 / 3 |
Total | 6 / 12 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.