tech-trpc
tRPC router architecture, procedure design, and Vertical Slice Architecture patterns. Use when building tRPC APIs, designing procedures, or structuring backend slices.
66
48%
Does it follow best practices?
Impact
100%
1.47xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/tech-trpc/SKILL.mdQuality
Discovery
75%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 description has good structure with an explicit 'Use when' clause and targets a specific technology niche (tRPC + VSA). However, it could be stronger by listing concrete actions rather than abstract concepts, and by including more natural trigger terms users might use when working with tRPC.
Suggestions
Add concrete actions like 'create routers', 'define procedures with input/output validation', 'implement context and middleware'
Include additional trigger terms users might naturally say: 'type-safe API', 'zod schema', 'query', 'mutation', 'TypeScript API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (tRPC) and mentions 'router architecture, procedure design, and Vertical Slice Architecture patterns' but doesn't list concrete actions like 'create routers', 'define input validation', or 'implement middleware'. | 2 / 3 |
Completeness | Clearly answers both what (tRPC router architecture, procedure design, VSA patterns) and when (building tRPC APIs, designing procedures, structuring backend slices) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'tRPC', 'APIs', 'procedures', 'backend slices' but misses common variations users might say like 'type-safe API', 'TypeScript backend', 'zod validation', or 'query/mutation'. | 2 / 3 |
Distinctiveness Conflict Risk | tRPC is a specific technology with distinct terminology; the combination of 'tRPC' and 'Vertical Slice Architecture' creates a clear niche unlikely to conflict with general API or backend skills. | 3 / 3 |
Total | 10 / 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 generic template with no tRPC-specific substance. It lacks executable code examples, concrete router/procedure patterns, or any Vertical Slice Architecture guidance despite the description promising these. The troubleshooting and workflow sections are boilerplate that could apply to any skill.
Suggestions
Add concrete tRPC code examples showing router definition, procedure creation, and input/output validation with Zod schemas
Include a Vertical Slice Architecture example demonstrating how to structure a feature slice with tRPC procedures
Replace the generic 3-step workflow with tRPC-specific steps (e.g., 'Define input schema → Create procedure → Add to router → Test with client')
Either inline essential tRPC patterns in the skill body or ensure the referenced rules index contains substantive, actionable content
| 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 abstract processes ('Apply the skill rules') without showing actual router definitions, procedure patterns, or Vertical Slice Architecture implementations. | 1 / 3 |
Workflow Clarity | The 3-step workflow is extremely vague ('Identify', 'Apply', 'Validate') with no tRPC-specific steps, validation checkpoints, or concrete guidance. It reads as a generic meta-workflow applicable to any skill. | 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 is essentially a shell pointing elsewhere without giving users actionable quick-start content. | 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 | |
- Repository
- ravnhq/ai-toolkit
- Commit
7b466be
- 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.