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.
76
66%
Does it follow best practices?
Impact
92%
1.43xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/freshservice-automation/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly identifies its domain (Freshservice ITSM via Rube MCP/Composio) and lists specific concrete actions. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The specificity and distinctiveness are excellent due to the named products and enumerated capabilities.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Freshservice, IT service management tickets, or Composio/Rube MCP integrations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create/update tickets, bulk operations, service requests, and outbound emails. Also mentions searching tools for schemas, which is a concrete procedural step. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Freshservice ITSM tasks with specific actions listed), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain terms. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Freshservice', 'ITSM', 'tickets', 'service requests', 'bulk operations', 'outbound emails', 'Composio', 'Rube MCP'. These cover the domain well and match what users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product names 'Freshservice' and 'Rube MCP (Composio)'. This is a clear niche that is very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent but verbose Freshservice automation skill that provides good structural organization and covers the key workflows comprehensively. Its main weaknesses are redundant content (status/priority codes and pitfalls repeated multiple times), lack of executable examples showing actual MCP tool invocations, and missing validation/feedback loops for bulk and destructive operations. Tightening the content by deduplicating reference information and adding concrete call examples would significantly improve it.
Suggestions
Add concrete, executable MCP call examples showing actual input JSON for at least one workflow (e.g., creating a ticket) with expected response structure.
Deduplicate status/priority codes and pitfalls — keep them in the reference tables only and remove inline repetitions from individual workflow sections.
Add explicit validation/verification steps to the bulk update workflow (e.g., 'After bulk update, call FRESHSERVICE_GET_TICKET on a sample ticket to verify changes applied') to address the missing feedback loop.
Consider extracting the detailed parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but contains significant redundancy. Status/priority codes are repeated in individual workflow sections AND in the Common Patterns reference tables. Pitfalls are listed per-workflow AND again in a consolidated 'Known Pitfalls' section with overlapping content. The quick reference table at the end is useful but some of its information is redundant with the workflow sections. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and numeric codes, which is good. However, it lacks executable code examples — the only quasi-example is a numbered list for date range filtering that isn't actual code. There are no concrete MCP call examples showing exact input/output JSON structures, which would make this much more actionable. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps and prerequisite identification (e.g., bulk update requires listing first). However, there are no validation checkpoints or feedback loops — for bulk operations especially, there's no guidance on verifying results, handling partial failures beyond a mention that 'others may still succeed,' or retry strategies for rate limiting. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and sections, but it's a monolithic document at ~180 lines with no bundle files to offload detail into. The reference tables, detailed pitfalls, and per-workflow parameter documentation could be split into separate reference files. The single external link to Composio toolkit docs is appropriate but insufficient for progressive disclosure. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.