CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-workflow

Build, run, and visualize multi-step AI generation workflows. The AI architect translates natural language descriptions into connected node graphs — chain image generation, video creation, enhancement, and editing into automated pipelines.

Quality

71%

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 ./library/workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A largely executable, well-sectioned skill with concrete commands and a sensible step protocol. Weaknesses are duplicated command blocks, no post-execution verification loop, and bundled scripts that are named but never shown how to be called.

Suggestions

Consolidate the duplicated discover/create/execute blocks — keep one canonical CLI Reference and have the protocol steps reference it instead of repeating full commands.

Add a post-run verification step to the protocol (e.g., "6. Verify: `muapi workflow status <run_id>`; if a node failed, fix inputs and re-execute") to create a real feedback loop.

Make the bundled scripts actionable: give their path and flag usage (e.g., `./scripts/generate-workflow.sh --prompt "..." --workflow-id <id>`), or move the CLI/MCP reference tables into a references/ file.

DimensionReasoningScore

Conciseness

The body is command-driven and mostly lean, but the same commands repeat across sections: `muapi workflow discover` appears in Core Operations, Agent Guided Discovery, Step 4, and CLI Reference; `create`/`execute` also appear three times each. This matches "mostly efficient but includes some... could be tightened" rather than the minor-trim level of 4, since whole duplicate blocks could be collapsed.

3 / 5

Actionability

Nearly everything is copy-paste-ready bash with the `--input "node1.prompt=..."` format shown, and the "CRITICAL RULE" about reading the API Inputs table is concretely actionable. Not a 5: the five bundled scripts in ./scripts/ are named in Core Operations but never invoked — the body shows `muapi workflow create "..."` while `generate-workflow.sh` actually requires `--prompt`, so a reader cannot run the scripts as documented; `pip install /path/to/muapi-cli` also embeds an unresolved placeholder.

4 / 5

Workflow Clarity

The Building-a-Workflow protocol is a clearly numbered 5-step sequence with inspection before execution, and the guided-discovery flow includes confirmation checkpoints and the never-invent-inputs rule. Not a 5: after `execute` there is no explicit verify-recover step (checking `workflow status`, handling a failed node, retrieving outputs is left only to the CLI Reference); not a 3 because the sequence and most checkpoints are explicit.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, and bundle scripts do exist, but references are not clearly signaled: scripts are named bare ("generate-workflow.sh") with no path or invocation example, and the full CLI Reference and MCP tool table sit inline in a ~190-line body where a references/ split would fit. This matches "some structure but could be better organized; references present but not clearly signaled".

3 / 5

Total

14

/

20

Passed

Description

66%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 strong, concrete description with good trigger vocabulary and a distinct AI-media-generation niche. Its main defect is the missing 'when to use' clause, which caps completeness and weakens skill-selection behavior.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to chain or automate muapi.ai generation steps (image, video, audio, enhancement, editing) into a multi-step pipeline."

Add natural synonyms users actually say, such as "generate images/videos", "text-to-video", or "AI content pipeline".

Mention the discover/edit of existing workflows so the description covers the full capability set shown in the body.

DimensionReasoningScore

Specificity

"Build, run, and visualize multi-step AI generation workflows" and "chain image generation, video creation, enhancement, and editing into automated pipelines" list several concrete actions with named node types. Not a 5 because capabilities like discovering/editing existing workflows (prominent in the body) are absent from the description; not a 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The "what" is clear and concrete (build/run/visualize chained generation workflows), but there is no "Use when..." clause or equivalent trigger guidance — nothing tells Claude when to invoke this skill. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases users would say are present: "AI generation workflows", "image generation", "video creation", "enhancement", "editing", "automated pipelines". Not a 5 because common variations users actually say ("generate images/videos", "text-to-video", "AI pipeline", "content generation") are missing.

4 / 5

Distinctiveness Conflict Risk

"multi-step AI generation workflows" with "connected node graphs" of image/video/enhancement/editing pins a fairly distinct niche. Not a 5 because generic words like "workflows" and "automated pipelines" could overlap with general automation/orchestration skills.

4 / 5

Total

15

/

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

library/workflow/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.