tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-rest-apisGenerate complete REST API implementations from OpenAPI specifications or database schemas. Use when generating RESTful API implementations. Trigger with phrases like "generate REST API", "create RESTful API", or "build REST endpoints".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
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 | 13 / 16 Passed | |
Implementation
22%This skill content is a template-like skeleton that lacks concrete, actionable guidance. It provides abstract instructions without executable code examples, has formatting issues with step numbering, and relies heavily on external references without giving Claude enough information to actually generate REST APIs. The content explains what to do conceptually but not how to do it specifically.
Suggestions
Add concrete, executable code examples showing actual REST API endpoint generation for at least one framework (e.g., Express.js or FastAPI)
Fix the step numbering and add explicit validation checkpoints (e.g., 'Verify routes are accessible before adding authentication middleware')
Remove redundant overview sentences and replace with a concise example of input (OpenAPI spec snippet) and expected output (generated code)
Explain the 'Bash(api:rest-*)' command pattern with specific examples of valid commands and their outputs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary filler phrases like 'This skill provides automated assistance for rest api generator tasks' and 'This skill provides automated assistance for the described functionality' which are redundant. The prerequisites section explains things Claude would know, but the overall structure is reasonably compact. | 2 / 3 |
Actionability | No executable code examples provided. Instructions are vague and abstract ('Generate boilerplate code', 'Implement endpoint handlers with business logic'). The Bash command reference 'Bash(api:rest-*)' is unexplained and not copy-paste ready. No concrete examples of what generated code should look like. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with apparent numbering issues (two separate sequences both starting at 1). No validation checkpoints between steps. Missing feedback loops for error recovery. No clear indication of when to verify work before proceeding. | 1 / 3 |
Progressive Disclosure | References external files appropriately (implementation.md, errors.md, examples.md) which is good structure. However, the main content is thin and relies too heavily on external references without providing enough actionable content in the skill itself. The overview section is essentially empty of useful information. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
N/ASomething went wrong
Reviewed
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.