Name: riddle-quiz-maker
Rating: 56.8 (1 reviews)
Author: membranedev

riddle-quiz-maker

Riddle Quiz Maker integration. Manage Quizs, Users, Categories. Use when the user wants to interact with Riddle Quiz Maker data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/riddle-quiz-maker/SKILL.md

Quality

Content

67%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 action-oriented with executable Membrane CLI commands and a well-handled connection state machine, but it is weakened by opening product-description fluff, an undefined "Step 2" reference, and a "Popular actions" section that does not actually list actions.

Suggestions

Trim the opening marketing/product-explanation paragraph and the "focus on integration logic rather than auth plumbing" fluff to respect the token budget.

Define the referenced "Step 2" (and renumber the connection sub-steps coherently) so the workflow sequence is unambiguous.

Populate the "Popular actions" section with actual named actions and example invocations, or remove the section if discovery is the only intended path.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padding such as "Riddle Quiz Maker is a tool that allows users to create and share riddle quizzes. It's likely used by educators, trainers..." and marketing fluff like "so you can focus on the integration logic rather than auth plumbing", fitting the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	Concrete, executable commands are given throughout (npm install, membrane login, connection ensure, action list/run, request with a flags table), but placeholders like CONNECTION_ID and the underdeveloped "Popular actions" section (which only repeats the discovery command without naming any actions) leave minor gaps, matching the "mostly executable guidance with minor gaps" anchor.	4 / 5
Workflow Clarity	The connection workflow has clear state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) with polling and a feedback loop (poll again after user action), but the flow references an undefined "Step 2" and uses an inconsistent "1b" label, fitting the "clear sequence with most checkpoints present; minor gaps" anchor.	4 / 5
Progressive Disclosure	The body is well-organized into clearly labeled sections with no nested or buried references, and no external bundle files are needed for a CLI-integration skill of this size; the only gap is the thin "Popular actions" section and absence of any deeper reference, matching the "good structure; most content appropriately placed; minor organization gaps" anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers both what and when in third person and names a specific product, but relies on a single generic verb ("Manage") and a vague "interact with data" trigger rather than concrete, varied trigger phrases.

Suggestions

Replace the generic verb "Manage" with specific concrete actions per entity (e.g., "Create and edit quizzes, manage users, organize categories").

Expand the "Use when" clause with concrete trigger phrases users would actually say (e.g., "Use when the user wants to create a riddle quiz, add or edit questions, manage quiz users, or organize quiz categories").

Add natural synonyms/variants of the trigger terms to broaden keyword coverage beyond the product name.

Dimension	Reasoning	Score
Specificity	The phrase "Manage Quizs, Users, Categories" names the domain and applies a concrete verb to three entities, but "Manage" is a single generic action verb so coverage is not comprehensive — matching the anchor that names the domain with 1-2 concrete actions but is incomplete.	3 / 5
Completeness	Both "what" ("Manage Quizs, Users, Categories") and "when" ("Use when the user wants to interact with Riddle Quiz Maker data") are explicitly present, but the "when" clause is generic rather than tied to concrete trigger phrases, matching the anchor where both exist yet "when" could be more specific.	4 / 5
Trigger Term Quality	Natural terms like "Riddle Quiz Maker", "Quizs", "Users", and "Categories" appear, but the trigger clause "interact with Riddle Quiz Maker data" is generic and common variations/synonyms are missing, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Riddle Quiz Maker" gives it a clear niche with low conflict risk, but the generic verbs ("Manage", "interact with data") leave minor overlap risk with related quiz/data skills, fitting the "mostly distinct; minor overlap risk" anchor.	4 / 5
	Total	14 / 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/riddle-quiz-maker/SKILL.md
Commit: f484c82

Reviewed: 5 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.