CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-platform

Setup and utility scripts for muapi.ai — configure API keys, test connectivity, and poll for async generation results

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./core/platform/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is token-efficient and immediately actionable in form — a clean script table plus copy-paste commands. Its weaknesses are implicit rather than explicit workflow sequencing and the fact that the referenced script files are missing from the bundle.

Suggestions

Include the actual setup.sh and check-result.sh in a scripts/ directory (or reference their real location) so the documented commands are executable.

State the setup sequence explicitly (add key, then test; poll only after submitting a generation) and what to do when the key test fails.

Document polling behavior briefly — expected wait, retry cadence, and what --once returns on incomplete results.

DimensionReasoningScore

Conciseness

The body is a lean script table, a copy-paste quick start, and a one-line requirements list — no padding and no explanation of concepts Claude already knows. This matches the 'every token earns its place' anchor rather than 4, since there is no over-explanation to trim.

5 / 5

Actionability

Concrete, fully specified commands like `bash setup.sh --add-key "YOUR_MUAPI_KEY"` cover the common cases, but the referenced scripts do not exist in the bundle (no scripts/ directory), so the commands are not executable as written. Anchor 4 ('mostly executable with minor gaps') rather than 5 for this reason.

4 / 5

Workflow Clarity

The quick start implies a sensible order (add key, show config, test, then poll) and `setup.sh --test` serves as a checkpoint, but the sequence is implicit and there is no guidance for failure cases (invalid key, polling never completes). This is 'clear sequence with most checkpoints; minor validation gaps', not 5, which would require explicit validation/error-recovery steps.

4 / 5

Progressive Disclosure

A short (<50 lines), well-organized single-file body with scripts clearly signaled in a table would normally merit 5 under the simple-skill exception, but the two referenced script files (setup.sh, check-result.sh) are absent from the bundle, leaving the primary navigation references broken. Anchor 4 ('good structure, minor organization gaps') rather than 3, since the structure and signaling themselves are clear.

4 / 5

Total

17

/

20

Passed

Description

70%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.

A concise, third-person description with a clear 'what' anchored to a specific platform. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and weakens discoverability.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when working with the muapi.ai API, setting up MUAPI keys, or checking async generation results.'

Include a few natural trigger variations such as 'check generation status' or 'retrieve result' to broaden keyword coverage.

Mention showing saved configuration, since that capability appears in the skill body but not in the description.

DimensionReasoningScore

Specificity

"configure API keys, test connectivity, and poll for async generation results" names three concrete actions in the muapi.ai domain, matching the 'several specific actions with minor gaps' anchor. It falls short of 5 only because coverage is not comprehensive (e.g., showing config or retrieving results without polling is only implied).

4 / 5

Completeness

The 'what' is clearly stated (configure API keys, test connectivity, poll for async results) but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not 4 because 'when' is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "muapi.ai", "API key", "test connectivity", "poll", "async generation results" — but common variations like "check status", "retrieve result", or "request status" are missing. This fits the 'good keyword coverage; a few natural terms missing' anchor, not 5 (no synonyms/extensions) and not 3 (coverage goes beyond 'some relevant keywords').

4 / 5

Distinctiveness Conflict Risk

"Setup and utility scripts for muapi.ai" names a specific platform, giving the skill a clear niche with distinct triggers and minimal conflict risk with generic setup or polling skills. Not 4, since no overlap with closely related skills is apparent.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

core/platform/SKILL.md

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.