orpc-contract-first
Guide for implementing oRPC contract-first API patterns in Dify frontend. Trigger when creating or updating contracts in web/contract, wiring router composition, integrating TanStack Query with typed contracts, migrating legacy service calls to oRPC, or deciding whether to call queryOptions directly vs extracting a helper or use-* hook in web/service.
94
89%
Does it follow best practices?
Impact
96%
2.66xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly defines its scope within a specific technical domain (oRPC in Dify frontend). It uses third person voice appropriately, provides explicit trigger conditions, and includes specific file paths and technology names that serve as excellent discriminators. The description effectively balances comprehensiveness with conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implementing contract-first API patterns, creating/updating contracts, wiring router composition, integrating TanStack Query, migrating legacy service calls, and deciding between queryOptions vs helpers/hooks. | 3 / 3 |
Completeness | Clearly answers both what (implementing oRPC contract-first API patterns in Dify frontend) and when (explicit 'Trigger when' clause listing five specific scenarios including creating contracts, wiring routers, integrating queries, migrating calls, and architectural decisions). | 3 / 3 |
Trigger Term Quality | Includes natural technical keywords users would say: 'oRPC', 'contract', 'TanStack Query', 'queryOptions', 'use-* hook', 'web/contract', 'web/service', 'router composition', 'legacy service calls'. These are terms developers working in this codebase would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (oRPC, TanStack Query, Dify frontend) and exact file paths (web/contract, web/service). Unlikely to conflict with other skills due to the precise technical niche and codebase-specific references. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides actionable TypeScript patterns for oRPC contract-first development. The decision rules for query/mutation usage and anti-patterns section are particularly valuable. However, it lacks validation steps in the workflow and could benefit from better progressive disclosure for complex topics like migration from legacy services.
Suggestions
Add validation checkpoint after step 1 (e.g., 'Verify contract compiles and types are inferred correctly before proceeding')
Include a brief error recovery pattern for when contract types don't match API responses at runtime
Consider extracting anti-patterns and migration guidance to separate reference files with clear links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, assuming Claude understands TypeScript, TanStack Query, and API patterns. No unnecessary explanations of basic concepts; every section provides actionable guidance. | 3 / 3 |
Actionability | Provides executable TypeScript code examples, concrete file paths, and specific decision rules. The query/mutation usage patterns are copy-paste ready with real import paths and options. | 3 / 3 |
Workflow Clarity | The 3-step core workflow is clear but lacks validation checkpoints. No guidance on verifying contract correctness, testing the integration, or handling errors when contracts don't match runtime behavior. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. For a skill of this complexity, references to separate files for anti-patterns examples or migration guides would improve navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- langgenius/dify
- Commit
4717168
- 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.