CtrlK
BlogDocsLog inGet started
Tessl Logo

701-technologies-openapi

Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review an OpenAPI; Improve an OpenAPI; Improve API contract; Improve API schema design. Part of cursor-rules-java project

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-structured with good progressive disclosure, but the core OpenAPI-editing workflow is delegated to the reference file, leaving its steps abstract and its verification checkpoint generic.

Suggestions

Make the core workflow steps more executable by inlining at least one concrete OpenAPI edit or validation action (e.g., a Spectral lint command and a sample fix loop) rather than deferring entirely to the reference.

Replace the generic 'Execute appropriate checks' step with a concrete validation checkpoint and an explicit validate-fix-retry feedback loop, especially since the skill covers contract validation and breaking-change checks.

Tighten the Constraints section, which repeats Maven command invocations across MANDATORY/VERIFY rules and could be consolidated to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, never explaining what OpenAPI is, and uses efficient bullet-style coverage; every section earns its place. Minor editorial cruft ('Part of cursor-rules-java project') is negligible.

3 / 3

Actionability

Concrete executable commands are present (./mvnw compile, ./mvnw clean install -pl skills-generator, ./mvnw clean verify), but the core task guidance ('Implement or refactor artifacts following the reference patterns') is abstract and delegated rather than executable here.

2 / 3

Workflow Clarity

A 4-step sequence exists with a verification step, but step 4 ('Execute appropriate checks') is generic rather than a concrete checkpoint, and there is no explicit validate-fix-retry feedback loop, leaving checkpoints implicit.

2 / 3

Progressive Disclosure

A clear overview with well-organized sections points to a single one-level-deep, real reference file (references/701-technologies-openapi.md), with content appropriately split and easy navigation.

3 / 3

Total

10

/

12

Passed

Description

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.

The description is comprehensive and well-structured, covering concrete capabilities, natural trigger terms, both what and when, and a distinctive framework-agnostic niche. No meaningful weaknesses for the description rubric.

DimensionReasoningScore

Specificity

Enumerates many concrete capabilities (spec structure, paths and operations, reusable schemas, security schemes, examples, contract validation via Spectral, breaking-change awareness, codegen handoffs), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both 'what' (enumerated OpenAPI guidance capabilities) and 'when' ('This should trigger for requests such as...'), matching the anchor for explicit triggers on both.

3 / 3

Trigger Term Quality

Provides explicit natural trigger phrases ('Review an OpenAPI', 'Improve an OpenAPI', 'Improve API contract', 'Improve API schema design') that users would actually say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Frames a clear niche as framework-agnostic OpenAPI 3.x contract guidance and explicitly excludes Spring Boot, Quarkus, and Micronaut, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.