Name: zoho-bugtracker
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zoho-bugtracker

Zoho Bugtracker integration. Manage Projects. Use when the user wants to interact with Zoho Bugtracker data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zoho-bugtracker/SKILL.md

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 provides concrete, executable Membrane CLI commands and a clear connection workflow, but it is slightly padded and omits validation/confirmation steps for destructive actions like delete. Adding confirmation checkpoints before deletes and trimming filler prose would lift the weaker dimensions.

Suggestions

Add an explicit confirmation/validation checkpoint before destructive actions (e.g. 'Confirm the bug id with the user before running delete-bug, since deletion is irreversible').

Trim filler prose such as 'ensuring software quality' and rephrase 'This will burn less tokens' more concisely.

Move the large proxy-options and popular-actions tables into a separate reference file and link to it, improving progressive disclosure and conciseness.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with clean executable commands, but includes some padding ('ensuring software quality', 'This will burn less tokens') and explanatory prose that could be tightened.	3 / 5
Actionability	Concrete, executable bash commands with flags are provided for install, auth, connection, search, run, and proxy, with minor gaps such as placeholder action ids that the user must fill in.	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with polling states, but the destructive actions (delete-bug, delete-project, delete-milestone) and batch operations lack validation or confirmation checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear sections (install, auth, connection, searching, running, proxy, best practices) and no nested references, though all content is inline with no offloaded detail files.	4 / 5
	Total	14 / 20 Passed

Description

61%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 cleanly answers both what and when and is highly distinct, but it undersells the skill's capabilities with the single vague action 'Manage Projects' and lacks natural synonyms like 'bugs' or 'tickets'. Adding concrete actions and trigger synonyms would raise specificity and trigger-term quality.

Suggestions

Expand the action list beyond 'Manage Projects' to concrete operations such as 'list and create bugs, manage projects and milestones, view comments' to improve specificity.

Add natural trigger synonyms users would say, e.g. 'Use when the user wants to track bugs, tickets, or issues in Zoho Bugtracker.'

Consider listing the core entities (projects, bugs, milestones) in the description to convey coverage more concretely.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Zoho Bugtracker') but only lists one generic action ('Manage Projects'), which is minimal and not comprehensive of the bug-tracking capabilities. This sits below the midpoint of naming 1-2 concrete actions.	2 / 5
Completeness	It explicitly answers both 'what' (Zoho Bugtracker integration, Manage Projects) and 'when' ('Use when the user wants to interact with Zoho Bugtracker data'), though the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	'Zoho Bugtracker' is a relevant keyword and 'interact with Zoho Bugtracker data' is a reasonable trigger, but common natural variations like 'bugs', 'tickets', 'issues', or 'defects' that users would say are missing.	3 / 5
Distinctiveness Conflict Risk	'Zoho Bugtracker' is a clearly distinct niche with specific triggers, making conflict with other skills minimal.	5 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/zoho-bugtracker/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.