CtrlK
BlogDocsLog inGet started
Tessl Logo

speechace

Speechace integration. Manage data, records, and automate workflows. Use when the user wants to interact with Speechace data.

57

Quality

66%

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/speechace/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 a focused, mostly executable guide to driving Speechace through the Membrane CLI, with concrete commands and clear connection/polling workflow. It is lean and well-structured, with only minor verbosity and a slightly inconsistent step-labelling.

DimensionReasoningScore

Conciseness

Mostly lean with executable commands and a focused flag table; minor padding in the 'Best practices' section and the somewhat redundant 'Popular actions' intro could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready membrane CLI commands for install, login, connection ensure, polling, action list/run, and proxy requests with a concrete flag reference table covering common cases.

5 / 5

Workflow Clarity

Clear sequence from install -> auth -> connection ensure -> poll for READY -> search actions -> run, with polling feedback loops for BUILDING/CLIENT_ACTION_REQUIRED states; minor validation gaps and the step numbering is slightly inconsistent ('Step 2' referenced without a clear Step 1/2 header).

4 / 5

Progressive Disclosure

Well-organized sections (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no external bundle files needed; the inline flag table and action schemas are appropriately placed rather than buried, though some reference-like detail (full clientAction schema) is inlined.

4 / 5

Total

17

/

20

Passed

Description

50%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 names a specific platform and includes an explicit 'Use when' trigger, but its actions are generic ('manage data, records, automate workflows') rather than Speechace-specific. Trigger terms are thin, missing natural keywords like 'pronunciation' or 'speech assessment'.

Suggestions

Replace generic actions with Speechace-specific ones, e.g. 'Score pronunciation, run speech assessments, and retrieve recording data'.

Expand the trigger clause with natural user phrasings: 'Use when the user wants to assess pronunciation, get speech scores, or interact with Speechace recordings'.

Add domain keywords like 'pronunciation', 'speech assessment', and 'scoring' so the description surfaces for natural user requests.

DimensionReasoningScore

Specificity

Names the domain (Speechace) but actions are generic ('Manage data, records, and automate workflows') with no concrete Speechace-specific actions like pronunciation scoring or assessment.

2 / 5

Completeness

Has a 'what' (manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Speechace data'), though both are somewhat generic.

4 / 5

Trigger Term Quality

'Speechace' is the only natural keyword; 'interact with Speechace data' is generic and missing common user phrasings like 'pronunciation', 'speech assessment', or 'scoring'.

2 / 5

Distinctiveness Conflict Risk

'Speechace' names a specific platform giving it a clear niche and low conflict risk, though the generic 'manage data' phrasing leaves minor overlap with other data skills.

4 / 5

Total

12

/

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.

Validation15 / 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
membranedev/application-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.