Name: comeet
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

comeet

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

Quality

66%

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/comeet/SKILL.md

Quality

Content

67%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 actionable and well-structured with executable CLI guidance and a clear connection workflow, but it carries unnecessary product-description padding and lacks explicit validation checkpoints for destructive/batch action runs.

Suggestions

Trim the opening marketing paragraph about what Comeet is and who uses it; assume Claude knows the platform or link to the docs instead.

Add an explicit validation/verify step before running destructive or batch actions (e.g., dry-run or confirm-affected-records guidance).

Resolve the CONNECTION_ID placeholder by showing where to obtain it from the connection ensure/get output earlier in the flow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the opening paragraph ('Comeet is a collaborative recruiting platform...') and product-marketing language about recruiters and HR professionals pad content Claude does not need.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands for install, login, connection, action listing/running, and proxy requests, with a flags table; minor gaps remain around the CONNECTION_ID placeholder resolution.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling, though explicit verify-before-commit steps for destructive or batch action runs are only lightly addressed.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working with Comeet, Popular actions, Best practices) with no nested references and all content appropriately in a single file; no bundle files exist to split further.	4 / 5
	Total	15 / 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 cleanly names a distinct niche and includes both a 'what' and 'use when' clause, but the actions and trigger terms are generic rather than reflecting Comeet-specific recruiting vocabulary.

Suggestions

Replace generic verbs with Comeet-specific actions, e.g. 'Manage candidates, job postings, and tasks; track applicants through the hiring pipeline.'

Add natural recruiter trigger terms such as 'candidates', 'job postings', 'applicants', or 'hiring workflow'.

Tighten the 'when' clause to concrete scenarios, e.g. 'Use when the user wants to manage Comeet candidates, jobs, or recruiting tasks.'

Dimension	Reasoning	Score
Specificity	Names the Comeet domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Comeet operations like candidate tracking or job posting.	3 / 5
Completeness	Provides a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Comeet data'), though the trigger clause is somewhat generic.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Comeet integration', 'Comeet data', 'records') but misses the natural phrases recruiters actually say, such as 'candidates', 'job postings', 'applicants', or 'hiring'.	3 / 5
Distinctiveness Conflict Risk	Names a specific niche platform (Comeet) with distinct triggers, making conflict with other skills unlikely.	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/comeet/SKILL.md
Commit: f484c82

Reviewed: 4 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.