CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audiocreator-foleyix

Direct sound, write, optimize, or repair Foleyix prompts and create background music, songs with vocals and lyrics, podcasts, ambience, sound effects, game effects, narration, dialogue, and sound scenes. Keep audio types and limits aligned with the website; check tasks and quota, then download private WAV results when generation is requested.

Quality

77%

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/audiocreator-foleyix/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, highly actionable skill body with real executable commands, explicit validation checkpoints, and well-signaled one-level references. Its main weaknesses are repetition, inline policy/pricing detail that belongs in a reference file, and one bundled reference (examples.md) that is never linked from the body.

Suggestions

Deduplicate repeated guidance (mode-selection semantics stated twice; 'never create replacement tasks' stated three times) into single statements at first mention.

Move the pricing, promotion, refund, and file-retention policy in 'Time packs and file retention' into a reference file (e.g. capabilities.md or a new billing.md) and keep only the operationally relevant summary inline.

Link references/examples.md from the body where prompt examples would help (e.g. from the prompt-writing or workflow sections) so the bundled file is discoverable.

DimensionReasoningScore

Conciseness

Most content is product-specific operational fact Claude cannot know (quota arithmetic, request-ID semantics, splitting rules), but there is noticeable repetition — 'Mode selection labels the task and does not add directions' appears twice (lines 101 and 110) and 'never create replacement tasks' is stated three times (lines 112, 114, 127) — and dense policy detail (USD 9.90/29.90/79.90/199.90 pricing, refund and promotion semantics in 'Time packs and file retention') sits inline where a reference file would do. Not a 2 because there is no padding explaining concepts Claude already knows; not a 4 because the repetition and inline policy sections could meaningfully be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: 'node scripts/foleyix.mjs help / whoami / login --no-browser / quota --json', a complete 'generate --mode narration --prompt "..." --out ./welcome.wav --json' example, plus status, download, voices, and jobs invocations, alongside concrete tables mapping modes to required input. Score 5 per anchor: specific examples cover the common cases.

5 / 5

Workflow Clarity

The body opens with a routing section ('Choose the requested workflow') and each workflow is sequenced with explicit checkpoints: check 'quota' before generating, verify 'the result's status and absolute file path before calling it complete', and 'Stop on an unknown result, failure, insufficient balance/storage or a wait timeout'. Error-recovery feedback loops exist (retry with the same persistent request ID, resume with --request-id reusing completed parts), so the batch long-script workflow is not missing validation and the destructive/batch cap does not apply. Not a 5 because the full generation sequence is scattered across several sections rather than given as one ordered checklist, and listening verification is only conditionally encouraged ('when available').

4 / 5

Progressive Disclosure

References are one level deep, clearly signaled with markdown links, and each is scoped to a purpose (prompt-writing.md for prompts, cli.md for CLI details, direction.md for directing, capabilities.md for limits, speech.md / sound-design.md for content branches, audio-capabilities.json for the catalog) — all cited paths exist in references/. Not a 5 because references/examples.md is bundled but never linked from the body (a discoverability gap), and some content that belongs in a reference (pricing, refund and retention policy) is inlined in the main file.

4 / 5

Total

16

/

20

Passed

Description

71%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 that names many specific audio capabilities and natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding a trigger sentence would also sharpen distinctiveness against generic audio skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create or fix audio, music, songs, podcasts, sound effects, ambience, narration, or dialogue, or mentions Foleyix.'

Include common synonyms users might say, such as 'voiceover', 'text-to-speech', or 'SFX', to broaden natural trigger coverage.

Anchor the niche more firmly by naming the deliverable format (WAV audio files via the Foleyix service) early in the description.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("Direct sound, write, optimize, or repair Foleyix prompts", "create background music, songs with vocals and lyrics, podcasts, ambience, sound effects, game effects, narration, dialogue, and sound scenes", "check tasks and quota, then download private WAV results") with comprehensive coverage of the audio result types. Not a 4 because coverage of actions (create/repair/optimize/inspect/download) is comprehensive rather than having minor gaps.

5 / 5

Completeness

The 'what' is clear (prompt writing/repair plus creation of nine named audio types), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the only 'when' phrasing ("when generation is requested") scopes only the download step, not the skill overall. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3; it is not a 4 because 'when' is only weakly implied rather than present-but-imprecise.

3 / 5

Trigger Term Quality

Natural user terms are well covered: "background music", "songs with vocals and lyrics", "podcasts", "ambience", "sound effects", "game effects", "narration", "dialogue", "sound scenes". Not a 5 because common synonyms such as "voiceover", "text-to-speech", "SFX", or generic "audio" are missing, which users may say instead.

4 / 5

Distinctiveness Conflict Risk

The Foleyix branding plus the specific combination of audio-generation tasks carves a clear niche, but broad terms like "podcasts", "dialogue", and "background music" could overlap with other music/audio-generation skills. Mostly distinct with minor overlap risk against closely related skills, so it fits anchor 4 better than the minimal-conflict anchor 5.

4 / 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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

lvyinchao/foleyix-skill

Path

skills/audiocreator-foleyix/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.