CtrlK
BlogDocsLog inGet started
Tessl Logo

trueconf

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/trueconf/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.

The body is well-structured and highly actionable with concrete Membrane CLI commands and a clear connection workflow including state checkpoints. Minor improvements would tighten redundant sections and add validation guidance for action and proxy runs.

Suggestions

Merge the redundant 'Searching for actions' and 'Popular actions' sections into a single action-discovery section to reduce token cost.

Add a brief validation or dry-run note before destructive action runs or proxy POST/PUT/DELETE requests.

Move the proxy flag reference table into a separate reference file and link to it, keeping the body as a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but includes minor over-explanation such as the introductory TrueConf overview and the Membrane benefit pitch that could be trimmed.

4 / 5

Actionability

Provides many concrete executable commands (install, login, connection ensure/get, action list/run, request) plus a flag table, but placeholders require substitution and the 'Searching for actions' and 'Popular actions' sections overlap.

4 / 5

Workflow Clarity

Clear install→auth→connect→poll→search→run sequence with state-validation checkpoints and a feedback loop after CLIENT_ACTION_REQUIRED, though no validation is specified after action or proxy runs.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers, but at ~140 lines with no bundle files some content (the proxy flag table, redundant action-list sections) could be split into a reference.

4 / 5

Total

16

/

20

Passed

Description

62%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 establishes a clear product niche and includes an explicit 'Use when' trigger, but its action verbs are generic and its trigger terms lack the breadth of natural keywords a user would say.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Schedule and join conferences, manage participants and groups, list and download recordings'.

Expand the 'Use when' clause with natural trigger phrases users actually say, such as 'meetings, webinars, recordings, or TrueConf server management'.

Mention the core entities (Conference, Participant, User, Server, Group, Recording) so the description signals the skill's true scope.

DimensionReasoningScore

Specificity

Names the TrueConf domain plus actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete like 'fills forms' or 'converts pages'.

3 / 5

Completeness

Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with TrueConf data') are present, though the trigger is generic.

4 / 5

Trigger Term Quality

Only the product name 'TrueConf' and 'interact with TrueConf data' appear as triggers; the actual entity terms (meetings, recordings, participants) and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Naming the specific TrueConf product gives a clear niche with minimal conflict risk, but the generic action verbs leave minor overlap with other integration skills.

4 / 5

Total

14

/

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.