CtrlK
BlogDocsLog inGet started
Tessl Logo

freshservice-automation

Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.

56

Quality

65%

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/freshservice-automation/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 highly actionable for an MCP tool-calling skill, but redundancy in the numeric code tables, a filler closing line, and the missing validation checkpoint on the batch bulk-update workflow hold back conciseness and workflow clarity.

Suggestions

Add an explicit verify step to the bulk-update sequence, e.g. '3. Check the response for per-ticket success/failure before considering the batch complete.'

Consolidate the status and priority numeric codes into the single Common Patterns reference table and reference it from the create/update workflows instead of repeating the mappings.

Replace the generic 'When to Use' line with concrete trigger conditions or remove it entirely to remove filler.

DimensionReasoningScore

Conciseness

Mostly efficient parameter/pitfall listings, but status and priority numeric codes are repeated across workflow 2, the Common Patterns tables, and Known Pitfalls, and the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview') is filler.

3 / 5

Actionability

Concrete tool slugs, exact parameter names with enum values, and a worked date-range example make the guidance largely executable; minor gap is the absence of full JSON argument examples showing a complete tool call.

4 / 5

Workflow Clarity

Workflows are sequenced with numbered tool steps and the setup includes an ACTIVE-status checkpoint, but the bulk-update batch workflow lacks an explicit verify-results checkpoint in its sequence, capping workflow clarity at 3 per the batch-operations guideline.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) and no nested references; the detailed per-tool parameter blocks could arguably live in a reference file, which keeps it just short of a 5.

4 / 5

Total

14

/

20

Passed

Description

70%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, clearly scoping a Freshservice ITSM automation niche, but it omits an explicit 'Use when...' trigger clause, leaving the 'when to use' half of completeness implicit.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to create, update, search, or bulk-manage Freshservice tickets, submit service requests, or send ticket notifications via email.'

Add 'incidents' or 'helpdesk' as natural synonyms a user might say alongside 'tickets' and 'service requests'.

Mention listing/searching tickets in the action list to round out capability coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'create/update tickets, bulk operations, service requests, and outbound emails' — naming the domain and multiple specific capabilities, with only minor coverage gaps (e.g. no mention of listing/searching).

4 / 5

Completeness

The 'what' is clear (automate Freshservice ITSM tasks via Rube MCP), but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural-keyword coverage including 'tickets', 'service requests', 'outbound emails', and 'Freshservice ITSM', though a few common variations a user might say (e.g. 'helpdesk', 'incidents') are absent.

4 / 5

Distinctiveness Conflict Risk

'Freshservice ITSM ... via Rube MCP (Composio)' carves a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.

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