Name: apicurio-registry
Rating: 55.2 (1 reviews)
Author: membranedev

apicurio-registry

Apicurio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apicurio data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/apicurio-registry/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The content is highly actionable, packed with executable CLI commands and a well-structured connection workflow with state-based checkpoints. It is held back by some unnecessary explanatory prose and a lack of validation guidance around destructive proxy and action operations.

Suggestions

Trim background Claude already knows — the opening 'Apicurio Registry is a distributed data store...' paragraph and explanatory Membrane auth prose — to improve token efficiency.

Add a validation/verification step before destructive proxy calls (e.g. recommend a GET to preview, or confirm with the user before -X DELETE/PUT) so the destructive-operation workflow is not capped.

Consider moving the detailed clientAction state-handling and the proxy flag table into a reference file linked from the main flow to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude does not need — the opening paragraph defining what Apicurio Registry is and prose like 'Membrane handles authentication... so you can focus on the integration logic'.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, proxy with a full flag table) covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state checkpoints and a poll-again feedback loop, but the proxy and action-run workflows support destructive operations (DELETE/PUT, batch action runs) with no pre-flight validation, capping the score per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The single-file body is well-organized into logical sections (Overview, Working with Apicurio, Popular actions, Best practices) with no nested references and easy navigation; only minor content (the detailed state-handling and proxy flag table) could arguably live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 correctly answers both what and when with an explicit 'Use when' trigger and is distinct due to the Apicurio product name. Its main weakness is generic action language ('manage data, records, automate workflows') and missing domain-specific trigger terms like schemas, artifacts, and registry.

Suggestions

Replace generic verbs with concrete Apicurio actions, e.g. 'Register and version Avro/JSON Schema/Protobuf artifacts, search the registry, and manage artifact and global rules.'

Add domain trigger terms users actually say — 'schemas', 'artifacts', 'registry', 'Avro', 'Protobuf', 'JSON Schema' — alongside 'Apicurio'.

Tighten the 'when' clause to concrete triggers, e.g. 'Use when the user wants to register, search, or manage schemas and API artifacts in Apicurio Registry.'

Dimension	Reasoning	Score
Specificity	The domain (Apicurio) is named, but the actions are generic ('Manage data, records, and automate workflows') rather than concrete operations like registering schemas or searching artifacts, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Apicurio data'), though the what is generic and the when could be more specific.	4 / 5
Trigger Term Quality	'Apicurio' is a natural keyword users would say, but the description misses common variations and synonyms (schemas, artifacts, registry, Avro, Protobuf), placing it at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The Apicurio product name gives it a clear, distinct niche with minimal conflict risk, though the generic 'manage data/records/workflows' phrasing leaves minor overlap with broad data skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/apicurio-registry/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.