CtrlK
BlogDocsLog inGet started
Tessl Logo

helpdesk-automation

Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.

55

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/helpdesk-automation/SKILL.md

The canonical home for this skill is helpdesk-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 content is well-organized and gives clear, sequenced workflows with a validation checkpoint, but it lacks executable examples and repeats cursor-pagination guidance across three sections. Consolidating the duplication and adding a concrete tool-call example would notably improve it.

Suggestions

Consolidate the cursor-based pagination guidance into a single section and reference it from the workflow steps to remove triplicated content.

Add at least one concrete, executable example showing an actual tool call with parameter values (e.g., a representative RUBE_SEARCH_TOOLS / HELPDESK_LIST_TICKETS invocation) to lift actionability.

Remove or replace the generic 'When to Use' closing line with a meaningful, skill-specific usage summary.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-organized, but cursor-based pagination is explained in three separate places (section 1 pitfalls, Common Patterns, and Known Pitfalls), and the closing 'When to Use' line is vapid padding that adds no information.

3 / 5

Actionability

Tool slugs and key parameters with defaults are listed concretely, but there are no executable code or call examples; the 'patterns' are pseudocode numbered steps rather than copy-paste-ready invocations.

3 / 5

Workflow Clarity

The Setup section is a clear sequence with an explicit validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'), and the browsing pattern is well sequenced; since all operations are read-only, no destructive-validation cap applies.

4 / 5

Progressive Disclosure

The single file is well-structured into Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference with no nested or buried references, and no bundle files are needed; minor tightening of the duplicated sections would reach the top anchor.

4 / 5

Total

14

/

20

Passed

Description

66%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 specific and distinct, naming four concrete HelpDesk actions, but it omits an explicit usage-trigger clause and slightly over-claims write capabilities the skill does not have. Adding a "Use when..." clause would raise completeness and trigger discoverability.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when the user wants to browse or list HelpDesk support tickets, views, canned responses, or custom fields') to satisfy the completeness dimension.

Soften 'manage views' and 'configure custom fields' to reflect the read-only nature of the toolkit (e.g., 'list views' and 'inspect custom fields') to avoid over-claiming.

Include synonyms such as 'support tickets' to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

Lists four concrete actions ("list tickets, manage views, use canned responses, and configure custom fields") rather than vague language, but slightly over-claims since the body reveals these are read-only operations, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clearly stated, but there is no explicit "Use when..." trigger clause; the closing "Always search tools first for current schemas" is procedural guidance, not a usage trigger, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms a user might say ("HelpDesk tasks", "tickets", "canned responses", "custom fields"), but misses common synonyms like "support tickets" and has no file-extension-style triggers.

4 / 5

Distinctiveness Conflict Risk

The Composio HelpDesk toolkit via Rube MCP is a clear niche with distinct triggers, though "HelpDesk" alone is broad enough to risk minor overlap with other ticketing-related skills.

4 / 5

Total

15

/

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
administrakt0r/AI-Agents-Safe-Coding-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.