api-contract
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-contractConfigure this skill should be used when the user asks about "API contract", "api-contract.md", "shared interface", "TypeScript interfaces", "request response schemas", "endpoint design", or needs guidance on designing contracts that coordinate backend and frontend agents. Use when building or modifying API endpoints. Trigger with phrases like 'create API', 'design endpoint', or 'API scaffold'.
Validation
88%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 14 / 16 Passed | |
Implementation
7%This skill is a hollow template with no actual content about API contracts, TypeScript interfaces, or endpoint design. It fails to deliver on its description's promise of guiding backend/frontend coordination. The generic boilerplate provides no actionable value and wastes context window space.
Suggestions
Add concrete TypeScript interface examples showing request/response schemas for common endpoint patterns
Include a step-by-step workflow for designing API contracts that coordinate backend and frontend agents, with validation checkpoints
Provide specific endpoint design patterns (REST conventions, error response formats, versioning) rather than generic placeholder text
Replace all generic instructions with API contract-specific guidance - what makes a good contract, how to handle breaking changes, schema validation approaches
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely generic boilerplate with no API contract-specific information. Every line could apply to any skill, wasting tokens on placeholder text that provides zero value. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no TypeScript interface examples, no endpoint design patterns, no request/response schemas. Instructions like 'Invoke this skill when trigger conditions are met' are completely vague and non-executable. | 1 / 3 |
Workflow Clarity | The 4-step 'instructions' are meaningless placeholders with no actual workflow for API contract design. No validation steps, no sequence for coordinating backend/frontend agents, no checkpoints. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) exist and are one level deep, but the main content is so empty that the structure is meaningless. The references use template variables ({baseDir}) suggesting incomplete setup. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
90%This description excels at trigger term coverage and completeness with explicit 'Use when' and 'Trigger with' clauses. The main weakness is that the actual capabilities are somewhat vague - it describes when to use the skill well but could be more specific about what concrete actions it performs (e.g., generating schemas, validating contracts, creating boilerplate).
Suggestions
Add specific concrete actions the skill performs, such as 'Generates TypeScript interfaces, validates request/response schemas, creates endpoint boilerplate'
Replace 'Configure this skill should be used when' with a cleaner opening that describes capabilities first, then triggers
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (API contracts, TypeScript interfaces, endpoint design) and mentions some actions like 'designing contracts' and 'building or modifying API endpoints', but lacks concrete specific actions like 'generate schemas', 'validate contracts', or 'create TypeScript types'. | 2 / 3 |
Completeness | Explicitly answers both what (guidance on designing contracts that coordinate backend and frontend agents, building/modifying API endpoints) and when (with clear 'Use when' clause and 'Trigger with phrases' guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'API contract', 'api-contract.md', 'shared interface', 'TypeScript interfaces', 'request response schemas', 'endpoint design', 'create API', 'design endpoint', 'API scaffold' - these are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API contracts and interface coordination between backend/frontend agents. The specific file reference 'api-contract.md' and focus on TypeScript interfaces makes it distinct from general coding or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
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.