CtrlK
BlogDocsLog inGet started
Tessl Logo

create-imessage-mockup

Render pixel-accurate iMessage screenshot mockups (DM or group) from a thread JSON. Supports minimal, with-keyboard, and full iPhone 15 Pro frame variants. Outputs HTML + PNG.

64

Quality

80%

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 ./skills/ads/packs/video-ad-formats/create-imessage-mockup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 with a well-sequenced, validated workflow and clear file navigation. The main weakness is token efficiency from restating the same tail/visual rules across multiple sections.

Suggestions

Consolidate the bubble-tail and tail/avatar rules into one section and cross-reference it from 'Quality Checks' and 'Failure Modes' instead of restating them.

Move the detailed CSS pseudo-element paint-order pitfalls into a dedicated reference file and summarize them in SKILL.md to improve both conciseness and progressive disclosure.

Provide the referenced bundle files (render.js, generate.js, templates/, examples/) or note that they ship alongside the skill, so the navigation links resolve to real artifacts.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining basics Claude already knows, but the bubble-tail behavior and tail/avatar rules are restated across 'Purpose', 'Implementation pitfalls', 'Quality Checks', and 'Failure Modes', so it could be tightened to reduce repetition.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready — a concrete thread-JSON schema, real CLI invocations, a flag table, setup commands, and a Files table — covering the common cases with complete code/commands.

5 / 5

Workflow Clarity

The Workflow section gives a clear sequence with an explicit verify-then-fix-then-re-render feedback loop, reinforced by the 'Quality Checks' checklist and the 'tests/run-all.sh' review step, matching the explicit-validation anchor.

5 / 5

Progressive Disclosure

Sectioning is clear and the Files table signals one-level-deep references (render.js, templates/*, examples/*, tests/*), but no bundle files are actually present on disk and the lengthy 'Implementation pitfalls' detail is inlined rather than split into a reference file.

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.

The description is specific and clearly distinct, but it omits any 'when to use' trigger guidance, which is the main gap. Adding an explicit 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when you need a fake or convincing iMessage screenshot for an ad, social post, or video scene.'

Include natural synonyms a user might say — 'fake iMessage', 'iPhone text message', 'message conversation screenshot' — to broaden trigger coverage.

Clarify the input expectation ('from a thread JSON') in user-facing terms so the trigger is not jargon-only.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Render pixel-accurate iMessage screenshot mockups (DM or group) from a thread JSON', 'Supports minimal, with-keyboard, and full iPhone 15 Pro frame variants', 'Outputs HTML + PNG' — with only minor coverage gaps versus the comprehensive-action anchor at 5.

4 / 5

Completeness

The 'what' is clear ('Render pixel-accurate iMessage screenshot mockups ... Outputs HTML + PNG') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains natural terms a user would say such as 'iMessage screenshot mockups', 'DM or group', and 'iPhone 15 Pro frame', giving good keyword coverage, though common synonyms like 'fake text message' or 'iPhone conversation' are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — iMessage screenshot mockups from thread JSON with specific frame variants — that is unlikely to trigger for the wrong skill, matching the minimal-conflict-risk anchor.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gooseworks-ai/goose-skills
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.