CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

72

1.43x
Quality

68%

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

57%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-structured, actionable, and grounded in specific tool schemas and pitfalls rather than generalities. Its main gaps are duplicated reference material inflating token cost, missing pre-validation for the batch bulk-update workflow, and the absence of reference files to keep SKILL.md lean.

Suggestions

Consolidate the status/priority/source code tables into a single section and remove their repetition across workflow pitfalls and Known Pitfalls.

Add a validation step before bulk updates — e.g. verify the listed ticket IDs and intended field changes with FRESHSERVICE_GET_TICKET before calling FRESHSERVICE_BULK_UPDATE_TICKETS.

Move the detailed per-workflow parameter listings into a references/ file (e.g. references/tools.md), keeping SKILL.md as an overview with the Quick Reference table.

DimensionReasoningScore

Conciseness

The body is dense and free of concept over-explanation, but numeric status/priority code guidance appears three times (workflow pitfalls, Common Patterns tables, Known Pitfalls) and pagination details repeat, so it could be tightened.

3 / 5

Actionability

Concrete tool slugs, typed parameter lists with enums and ranges, and per-workflow pitfalls give mostly executable guidance, though a sample tool call payload would close the remaining gap.

4 / 5

Workflow Clarity

Numbered tool sequences and setup checkpoints (e.g. 'Confirm connection status shows ACTIVE') are present, but bulk update — a batch operation — has no pre-execution validation of the collected ticket IDs, only post-hoc response checking, capping this at 3.

3 / 5

Progressive Disclosure

Headers and a Quick Reference table give structure, but ~210 lines of per-workflow API parameter reference are inlined in SKILL.md with no reference files to offload detail, matching the 'API reference that could be in a separate file' anchor.

3 / 5

Total

13

/

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 domain-distinct, naming the target product, integration path, and four concrete operations. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and slightly limits discoverability.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user mentions Freshservice, ITSM tickets, service catalog requests, or helpdesk automation.'

Add list/search ticket operations to the capability list so coverage matches the actual workflows in the skill body.

Include common synonyms such as 'helpdesk' or 'IT support tickets' to broaden natural trigger matching.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'create/update tickets, bulk operations, service requests, and outbound emails' — but misses list/search ticket operations, leaving a minor coverage gap.

4 / 5

Completeness

The 'what' is explicit (automate Freshservice ITSM tasks via Rube MCP with named operations) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'Freshservice', 'tickets', 'service requests', and 'outbound emails' match what users would say, though common synonyms such as 'helpdesk' or 'IT support' are absent.

4 / 5

Distinctiveness Conflict Risk

The product-specific pairing of 'Freshservice' with 'Rube MCP (Composio)' carves a clear niche, though generic terms like 'tickets' and 'ITSM' leave minor overlap risk with other ticketing 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.

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

davepoon/buildwithclaude

Path

plugins/all-skills/skills/freshservice-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.