CtrlK
BlogDocsLog inGet started
Tessl Logo

treblle

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

60

Quality

71%

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/treblle/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 body is an efficient, actionable guide with a notably strong connection-state workflow including explicit validation and recovery loops; its main weakness is that detail-heavy sections (connection states, proxy flags) are inlined rather than split into reference files.

Suggestions

Move the detailed clientAction sub-field breakdown and the proxy flag table into a separate references file, keeping SKILL.md as a concise overview with one-level-deep links.

Add at least one concrete Treblle-specific action example with realistic parameters in the 'Popular actions' section so the discovery→run loop is end-to-end copy-pasteable.

Trim the opening descriptive paragraph about what Treblle is and remove softening phrases like 'so you can focus on the integration logic rather than auth plumbing'.

DimensionReasoningScore

Conciseness

Largely lean with direct bash commands and a terse flag table, though the introductory 'Treblle is a platform that...' paragraph and a few softening phrases (e.g. 'so you can focus on integration logic') could be trimmed.

4 / 5

Actionability

Provides concrete, executable membrane CLI commands throughout with documented parameters, but relies on placeholders (CONNECTION_ID, <actionId>) and the 'Popular actions' section repeats discovery without a concrete Treblle-specific example.

4 / 5

Workflow Clarity

The connection setup is a clear state-machine sequence with explicit feedback loops: ensure, poll with --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after the user acts, then proceed.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and only one level of references, but at ~140 lines with detailed clientAction sub-fields and a full proxy flag table inlined, some content could be split into a separate reference file.

4 / 5

Total

17

/

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 is clear and trigger-oriented for the named Treblle integration, but its capabilities are stated generically and it lacks API-domain-specific trigger terms that would sharpen it.

Suggestions

Replace generic verbs with Treblle-specific capabilities, e.g. 'Monitor API performance, inspect requests and responses, and document endpoints' instead of 'Manage data, records, and automate workflows'.

Add API-domain trigger terms to the 'Use when' clause, such as 'API monitoring', 'API debugging', 'API performance insights', or 'API documentation'.

Mirror Treblle's domain hierarchy (Project/Endpoint/Request/Response) in the description so users searching for those concepts find the skill.

DimensionReasoningScore

Specificity

Names the Treblle domain plus a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic and no Treblle-specific capabilities (API monitoring, debugging, documentation) are enumerated.

3 / 5

Completeness

Answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Treblle data'), though the 'when' could be more specific with concrete API-related triggers.

4 / 5

Trigger Term Quality

Includes the natural keyword 'Treblle' and the phrase 'interact with Treblle data', but lacks common synonyms and API-domain trigger terms like 'API monitoring', 'API insights', or 'API documentation'.

3 / 5

Distinctiveness Conflict Risk

The named brand 'Treblle' gives it a clear niche with low conflict risk, but the generic verbs ('manage data, records, automate workflows') create minor overlap with other data/records 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.