CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-instagram-post

Create a polished, on-brand Instagram post — square or portrait hero image with matching caption and hashtags.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/muapi-instagram-post/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, actionable body for a simple generative skill: concrete CLI commands, a curl fallback, and clean sectioning. The main gaps are the absence of a full example invocation for the primary CLI and no output-verification checkpoint.

Suggestions

Show one copy-paste-ready `muapi image generate` invocation with actual argument syntax instead of only naming the command and parameters.

Clarify the aside 'Use the plan if generating more than one variant' — it references a plan that is not defined anywhere in the skill.

Add a brief checkpoint after Phase A (e.g. confirm the image request succeeded via `muapi predict wait` before composing the caption).

DimensionReasoningScore

Conciseness

The body is efficient — an inputs table, two tight phases, and brief operational notes with no explanations of concepts Claude already knows. It is not a 5 due to minor trimmable content: the marketing-tone Note 'Prioritize scroll-stopping first impressions — the image must visually communicate the brief within 2 seconds' and the confusing aside 'Use the plan if generating more than one variant'.

4 / 5

Actionability

Mostly executable guidance: a concrete command ('Call `muapi image generate` (model=nano-banana-2, aspect_ratio=`{{format}}`)') plus a complete curl fallback with headers and a polling command. It is not a 5 because the primary CLI invocation is named but not shown as a copy-paste-ready example with full argument syntax, and the image-prompt step is guidance rather than a concrete worked example.

4 / 5

Workflow Clarity

Clear two-phase sequence with explicit ordering ('After the image is generated'), conditional branching (edit vs. generate), and failure-handling guidance (auth setup, polling). It is not a 5 because there are no explicit validation checkpoints (e.g. verifying the image generated successfully before composing the caption); the destructive/batch cap does not apply since this is a generative, single-output skill.

4 / 5

Progressive Disclosure

There are no bundle files and the body is ~50 lines with well-organized sections (Inputs, Steps, Notes, Trigger Keywords, agent notes), so the simple-skill exception applies and progressive disclosure scores 5 on well-organized sections alone. Nothing that belongs in a separate file is inlined.

5 / 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 specific, distinctive description with good natural trigger terms, but it omits any explicit 'Use when...' guidance, capping completeness. Adding a trigger clause would lift it to the quality of the reference examples.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user asks for an Instagram post, IG creative, or social media image with caption and hashtags.'

Drop soft filler like 'polished, on-brand' or replace it with a concrete capability (e.g. mention Reels 9:16 format support).

Add natural synonyms such as 'IG' or 'social media post' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names several concrete actions ('hero image', 'matching caption and hashtags') plus formats ('square or portrait'), fitting anchor 4. It is not a 5 because coverage is not comprehensive — variants like Reels/caption styling are absent and 'polished, on-brand' is soft filler rather than a concrete capability.

4 / 5

Completeness

The 'what' is clear (create a hero image with caption and hashtags) but there is no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

'Instagram post', 'caption', and 'hashtags' are natural phrases users would say, giving good keyword coverage (anchor 4). It is not a 5 because common variations like 'IG', 'Reels', or 'social media post' are missing; it is clearly above a 3 since multiple natural terms are present.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Instagram post creation) with distinct triggers ('Instagram', 'caption', 'hashtags') and minimal conflict risk with other skills. No neighboring anchor fits better — it is not merely 'mostly distinct' but squarely a distinct domain.

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

.opencode/skills/muapi-instagram-post/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.