CtrlK
BlogDocsLog inGet started
Tessl Logo

onedesk

OneDesk integration. Manage Organizations. Use when the user wants to interact with OneDesk data.

53

Quality

60%

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

Quality

Content

63%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 solid, command-heavy integration guide with genuinely good connection-state feedback handling, but it carries minor redundancy and broken step cross-references that hurt navigation. Actionability is strong; conciseness and progressive disclosure have clear room to improve.

Suggestions

Remove the marketing sentence ('This helps streamline workflows and improve customer satisfaction') and delete or merge the redundant 'Popular actions' section that restates `action list`.

Fix the step numbering: either add explicit 'Step 1'/'Step 2' headers or drop the 'skip to Step 2' and '1b' references so cross-links resolve.

Add brief error-handling guidance to the action-run and proxy sections (e.g., check the `output`/error fields and retry on auth-refresh failures) to round out the workflow's validation checkpoints.

DimensionReasoningScore

Conciseness

The body is mostly command-driven and efficient, but the marketing line ('This helps streamline workflows and improve customer satisfaction') and the 'Popular actions' section restating the already-shown `action list` command are unnecessary padding, fitting 'mostly efficient but includes some unnecessary explanation.'

3 / 5

Actionability

It provides concrete, copy-paste-ready commands for install, login, connect, search, run, and proxy plus a flags table, covering the common cases; the only gaps are placeholder-heavy commands and no full end-to-end worked example, so it sits at 'mostly executable guidance; minor gaps' rather than fully comprehensive.

4 / 5

Workflow Clarity

The connect-to-OneDesk flow has a clear sequence with a real feedback loop — explicit READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state handling and `--wait` polling — but the action-running and proxy sections lack corresponding error/verification guidance, keeping it just below the full validation+checklist bar of a 5.

4 / 5

Progressive Disclosure

Sections are reasonably organized and a single self-contained file is appropriate here, but cross-references are broken: 'skip to Step 2' points to no Step 2 header and '#### 1b' has no '1a', fitting 'could be better organized; references not clearly signaled.'

3 / 5

Total

14

/

20

Passed

Description

57%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 correctly names the OneDesk niche and includes an explicit 'Use when' trigger, but it is thin on concrete capabilities and natural trigger phrases. It reads as a minimal, slightly generic integration blurb rather than a precise capability+trigger statement.

Suggestions

Replace 'Manage Organizations' with the concrete data types the skill handles (e.g., 'manage support tickets, tasks, projects, customers, and time entries') to lift specificity.

Expand the trigger with natural user phrases: 'Use when the user wants to manage OneDesk support tickets, projects, tasks, or customer feedback.'

Keep the product name as the distinctiveness anchor but pair it with task-specific triggers to reduce the generic 'interact with data' phrasing.

DimensionReasoningScore

Specificity

The description names the domain ('OneDesk integration') but offers only one minimal, generic action ('Manage Organizations'), omitting the tickets, tasks, projects, and other entities the body actually covers — matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions of a 3.

2 / 5

Completeness

Both 'what' ('OneDesk integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with OneDesk data.') are present, but the 'when' is generic and the 'what' is thin, so it lands at 'both present; when could be more explicit or specific' rather than the concrete trigger phrases of a 5.

4 / 5

Trigger Term Quality

It includes relevant keywords ('OneDesk', 'Organizations', 'interact with OneDesk data') but misses the natural task phrases a user would say (support tickets, projects, tasks, customer feedback), fitting 'some relevant keywords but missing common variations or synonyms.'

3 / 5

Distinctiveness Conflict Risk

Naming the specific product 'OneDesk' gives it a clear niche with low overlap risk, but the generic trigger phrasing ('interact with OneDesk data') keeps it just below the crisp distinct-triggers bar of a 5.

4 / 5

Total

13

/

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.