Tessl • The package manager for agent skills

SkillPublic

comet

Comet workflow entry. Use when the user invokes /comet or asks to use Comet without choosing Native or Classic; load Native or Classic from project configuration.

Quality

85%

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

Quality

Content

88%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.

An exemplary dispatcher skill: an executable CLI command with exhaustive, explicit failure handling and unambiguous delegation steps. The only notable issues are organizational — trailing paragraphs about the delegated workflow's context-reporting mechanics sit in the entry skill where they add tokens without aiding dispatch.

Dimension	Reasoning	Score
Conciseness	The body is imperative and terse with no explanations of known concepts, but the trailing context-manifest and application-reporting paragraphs describe the delegated workflow's behavior rather than the entry's dispatch task and could be trimmed. This is a minor instance of over-inclusion rather than the 'some unnecessary explanation' level of anchor 3.	4 / 5
Actionability	Guidance is fully executable: the copy-paste command `comet workflow resolve . --activate --json`, exact error signatures ("command not found", "ENOENT", nonzero exit, invalid JSON or fields), the exact schema string, exact skill names to load, and exact flags (`--expand-context "<id>"`, `--application "<application-id>" --outcome used-successfully\|ignored\|overridden\|corrected\|contributed-to-failure`) covering the common cases.	5 / 5
Workflow Clarity	A clear numbered 3-step sequence (run CLI, parse JSON, load the named Skill) with explicit validation at every failure mode: CLI missing -> stop and report incomplete installation; nonzero exit, unparseable config, or invalid JSON/fields -> preserve the original error and stop; schema whitelist (`comet.workflow-resolution.v1`) and skill-value whitelist. Stop-and-report is the correct terminal checkpoint for a router.	5 / 5
Progressive Disclosure	The skill is self-contained under 50 lines and delegates one level deep to clearly signaled skills (`/comet-native`, `/comet-classic`) loaded via the Skill tool. Minor gaps: the post-selection context-loading instructions arguably belong in the delegated skills rather than this entry, and the 13 bundled scripts in scripts/ are not navigable from the body (by design, since the body forbids invoking the internal bundle directly).	4 / 5
	Total	18 / 20 Passed

Description

73%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.

A concise, third-person dispatcher description with an explicit and well-disambiguated trigger clause. Its main weakness is a thin 'what': it describes the routing mechanics but not the underlying workflow capability, and keyword coverage stops just short of comprehensive.

Suggestions

Add one clause stating what the Comet workflow does once selected (e.g., what Native vs. Classic manage), so the 'what' conveys capability rather than only the dispatch mechanism.

Broaden trigger coverage with natural variations such as "Comet workflow" or "run/start Comet" to capture more phrasings users would actually say.

Name the concrete actions the entry performs (resolve project configuration, activate the workflow, load the selected Skill) instead of the single 'load Native or Classic' action.

Dimension	Reasoning	Score
Specificity	"Comet workflow entry" names the domain and "load Native or Classic from project configuration" is one concrete action, matching the '1-2 concrete actions, not comprehensive' anchor. It is not 4 because only the dispatch action is listed, and not 2 because the action stated is specific rather than generic.	3 / 5
Completeness	Both parts are explicit: what ("load Native or Classic from project configuration") and when ("Use when the user invokes /comet or asks to use Comet without choosing Native or Classic"). It is not 5 because the 'what' is purely mechanistic and never conveys what the Comet workflow actually accomplishes.	4 / 5
Trigger Term Quality	"invokes /comet", "asks to use Comet", "Native", and "Classic" are phrases a user would naturally say, giving good keyword coverage. A few natural variations (e.g., "Comet workflow", "run Comet") are missing, so it falls short of the comprehensive-synonym anchor 5.	4 / 5
Distinctiveness Conflict Risk	The description occupies a clear niche tied to the /comet command and explicitly disambiguates from sibling skills ("without choosing Native or Classic"), giving minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rpamis/comet
Path: assets/skills/comet/SKILL.md
Revision: 575ab0d

Reviewed: 9 days ago

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.

comet

Table of Contents

Is this your skill?