CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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/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

67%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.

A well-structured, largely actionable reference for the HelpDesk toolkit: concrete tool names, parameters, defaults, and a setup sequence with verification checkpoints. Its main weaknesses are redundancy — pitfalls repeated across workflow sections, 'Known Pitfalls', and the Quick Reference table — and a filler 'When to Use' section that adds no information.

Suggestions

Consolidate the per-workflow 'Pitfalls' with the 'Known Pitfalls' section into one place to eliminate duplicated cursor-pagination, silo, and parameter details.

Delete or rewrite the filler 'When to Use' closing section ('This skill is applicable to execute the workflow or actions described in the overview.') so every line carries information.

Drop the Quick Reference table or keep it as the sole summary, removing the third repetition of tool/parameter listings.

DimensionReasoningScore

Conciseness

Parameter documentation is factual and mostly efficient, but pitfalls are stated twice (cursor-pagination details appear in workflow 1's Pitfalls and again under 'Known Pitfalls'), the Quick Reference table re-lists the same tools a third time, and the 'When to Use' section is pure filler ('This skill is applicable to execute the workflow or actions described in the overview'). This is more than 'minor instances that could be trimmed' (anchor 4), so it sits at anchor 3: could be meaningfully tightened.

3 / 5

Actionability

Concrete tool slugs (HELPDESK_LIST_TICKETS), exact parameter names with defaults and ranges (silo values, sortBy options, pageSize 1-100), a numbered setup sequence, and a step-by-step browsing pattern give mostly executable guidance. Minor gaps — no example request/response payloads — keep it below anchor 5; it is well above anchor 3's pseudocode level.

4 / 5

Workflow Clarity

Setup has explicit checkpoints ('Verify Rube MCP is available', 'Confirm connection status shows ACTIVE before running any workflows') and error recovery ('If connection is not ACTIVE, follow the returned auth link'), and each workflow includes 'When to use', tool sequence, and pitfalls. Operations are read-only, so the missing-validation cap does not apply; the only gap is absence of output-validation steps, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with no bundle directories and no nested references; sections are well-organized with a navigable Quick Reference table, and at ~170 lines the inline parameter detail is reasonable for a single-purpose skill. Minor organization gaps (duplicated pitfall content that would be consolidated before any split) place it at anchor 4.

4 / 5

Total

15

/

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.

A specific, well-targeted description that names four concrete HelpDesk actions and the integration mechanism, with good natural trigger keywords. Its main weakness is the complete absence of a 'when to use this skill' trigger clause, which leaves a user's request like 'show me my open tickets' without explicit trigger coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions HelpDesk tickets, saved views, canned replies, or custom fields, or wants to browse/archive support tickets.'

Align action verbs with the toolkit's actual read-only capabilities ('list tickets, views, canned responses, and custom fields') to avoid over-claiming 'manage'/'configure' operations.

Include common synonyms such as 'support tickets', 'replies', or 'templates' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names four concrete actions ('list tickets, manage views, use canned responses, and configure custom fields') with a clear integration path ('via Rube MCP (Composio)'). Not 5 because 'manage views' and 'configure custom fields' are vague relative to the read-only listing operations the body actually documents; well above anchor 3's 1-2 concrete actions.

4 / 5

Completeness

The 'what' is clear (automate HelpDesk tasks via Rube MCP with four named actions), but there is no 'Use when...' clause or equivalent trigger guidance — the closing sentence 'Always search tools first for current schemas' is a behavioral instruction, not a when-to-use trigger. Per the rubric guideline, the missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'HelpDesk', 'tickets', 'canned responses', 'custom fields', 'views' — terms a support user would plausibly say. A few natural variations are missing (e.g., 'support tickets', 'replies', 'templates'), keeping it below the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

Distinct niche anchored by 'HelpDesk', 'Rube MCP (Composio)', and 'canned responses'; unlikely to trigger for unrelated skills. Minor overlap risk with other generic ticketing or customer-support skills keeps it at anchor 4 rather than 5.

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/helpdesk-automation/SKILL.md

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.