Name: kickserv
Rating: 62.4 (1 reviews)
Author: membranedev

kickserv

Kickserv integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kickserv data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/kickserv/SKILL.md

Quality

Content

82%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 highly actionable with executable Membrane CLI commands and a reasonably clear connection workflow supported by polling and state checks. Main weaknesses are minor conciseness padding and slightly incoherent step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven guidance with only minor padding (e.g., the opening field-service-management paragraph), so it sits above the 3 anchor but below a 5 because that background and a few explanatory asides could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure, action list/run, request proxy) plus a concrete flag-options table covering the common cases; fits the top anchor.	5 / 5
Workflow Clarity	The connect flow has a clear sequence with polling-based checkpoints and state feedback (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the dangling "skip to Step 2" reference and inconsistent 1b/Step-2 numbering leave minor gaps; not a 5 because the step labeling is not fully coherent.	4 / 5
Progressive Disclosure	The single self-contained SKILL.md is well-organized with clear section headers and no nested references; above a 3 for structure, below a 5 because some inline material (clientAction detail, proxy flag table) is sizable and could be split into reference files.	4 / 5
	Total	17 / 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 product-specific and answers both what and when, giving it strong distinctiveness and decent completeness. It is held back by generic action language and limited trigger-term variation.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Kickserv actions like "create jobs, dispatch technicians, generate invoices, and manage customers".

Broaden the trigger with natural synonyms, e.g. "Use when the user wants to schedule jobs, manage customers, or work with Kickserv data."

Mention key Kickserv entities (jobs, invoices, estimates, contacts) in the description to improve specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Kickserv domain with a couple of generic actions, but the actions are not concrete enough to reach the "several specific actions" band; above a 2 because it lists more than one action, below a 4 because none are truly specific.	3 / 5
Completeness	It states both what ("Kickserv integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Kickserv data"), but the when clause is somewhat narrow and could be more explicit; not a 5 because the trigger lacks concrete, varied trigger phrases.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Kickserv data" offers the natural product name but lacks common variations or synonyms, matching the "some relevant keywords but missing common variations" anchor; not a 4 because no broader phrasings are covered.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Kickserv gives it a clear niche with a distinct trigger and minimal conflict risk with other skills; fits the top anchor better than the 4, which is for skills with minor overlap risk.	5 / 5
	Total	15 / 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/kickserv/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.