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.

77

1.43x
Quality

69%

Does it follow best practices?

Impact

92%

1.43x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/freshservice-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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, actionable, and lean, giving a model what it needs to execute Freshservice workflows. The main weakness is the absence of explicit validation/verification checkpoints in the batch bulk-update workflow, which caps workflow clarity at 3.

Suggestions

Add an explicit verification step to the bulk-update workflow sequence, e.g. '3. Check the response for per-ticket results; retry or report any failures.'

De-duplicate the status/priority code tables and the 30-day default note so each appears in one canonical location.

Add one full example tool invocation per workflow (not just parameter lists) to lift actionability to copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly lean with tool sequences, parameter specs, and pitfalls; no padding with concepts Claude already knows, though status/priority codes and the 30-day default are repeated across workflow pitfalls, Common Patterns, and Known Pitfalls.

4 / 5

Actionability

Concrete tool names, parameter enums, and numeric code tables make workflows directly executable, with one worked parameter example for date filtering; minor gap is the lack of full copy-paste example invocations per workflow.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with [Required]/[Prerequisite] tags and setup checkpoints, but the bulk-update batch operation has no explicit verification checkpoint in its sequence (verification appears only as a pitfall note), capping workflow clarity at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

Well-organized into Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference with clear headers and easy navigation; no bundle files exist and the single-file structure is reasonable for this size, though some parameter detail could be split out.

4 / 5

Total

15

/

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 distinctive, naming a clear product niche and several concrete actions with natural trigger terms. Its main weakness is the missing explicit 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create, update, search, or bulk-manage Freshservice tickets, submit service requests, or send outbound ticket emails.'

Mention listing/searching tickets among the listed actions to close the coverage gap.

Include common synonyms like 'incident' or 'helpdesk ticket' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('create/update tickets, bulk operations, service requests, and outbound emails') plus the domain, but omits listing/searching tickets, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (automate Freshservice ITSM tasks with listed actions), but there is no 'Use when...' trigger clause; 'Always search tools first for current schemas' is operational guidance, not a when-to-use trigger, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('Freshservice', 'ITSM', 'tickets', 'service requests', 'outbound emails') that users would say, though common synonyms like 'incident' or 'helpdesk' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Freshservice ITSM via Rube MCP/Composio) with product-specific triggers and minimal overlap risk with other skills.

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
davepoon/buildwithclaude
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.