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.

59

Quality

69%

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.

The body is well-structured and actionable with clear setup checkpoints, but suffers from repeated explanations of cursor pagination and silo filtering across multiple sections that inflate the token budget.

Suggestions

Consolidate the cursor-pagination and silo-filtering guidance into a single section and reference it once instead of restating it in each workflow's Pitfalls, Common Patterns, and Known Pitfalls.

Trim the Quick Reference table or the per-workflow "Key parameters" where they merely duplicate content already covered, keeping each fact in exactly one place.

DimensionReasoningScore

Conciseness

Mostly efficient, but cursor pagination and silo filtering are each restated across three sections (the per-workflow Pitfalls, Common Patterns, and Known Pitfalls), which is unnecessary padding.

3 / 5

Actionability

Concrete tool slugs, parameters with documented defaults, and a quick-reference table give mostly executable guidance; as an MCP skill, absent code is justified, leaving only minor gaps.

4 / 5

Workflow Clarity

Setup has explicit checkpoints ("Confirm connection status shows ACTIVE before running any workflows") and the operations are read-only, so the destructive-cap does not apply; minor validation gaps remain.

4 / 5

Progressive Disclosure

No bundle files exist, so content lives in one cohesive, well-sectioned file with no nested references; minor organization gaps from cross-section repetition keep it at 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

71%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 mostly distinct, but it lacks an explicit "Use when…" trigger clause, which caps completeness. Trigger-term coverage is good but missing common synonyms.

Suggestions

Add a "Use when…" clause naming concrete user triggers, e.g. "Use when the user wants to browse or paginate support tickets, list saved views, or retrieve canned responses via HelpDesk."

Broaden trigger terms with natural synonyms such as "support tickets", "reply templates", and "ticket fields" so the skill surfaces for varied phrasings.

DimensionReasoningScore

Specificity

"list tickets, manage views, use canned responses, and configure custom fields" lists multiple concrete actions with comprehensive coverage of HelpDesk operations, matching the score-5 anchor.

5 / 5

Completeness

The description gives a clear "what" but no "Use when…" trigger clause; "Always search tools first for current schemas" is behavioral guidance, not a use-when trigger, so completeness caps at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms ("tickets", "canned responses", "custom fields") but omits common synonyms such as "support tickets" or "templates", fitting good-but-not-comprehensive coverage at score 4.

4 / 5

Distinctiveness Conflict Risk

Pinned to the Rube MCP / Composio niche, but the listed operations (tickets, views, responses) overlap generic ticketing skills, leaving minor conflict risk at score 4 rather than 5.

4 / 5

Total

16

/

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.