CtrlK
BlogDocsLog inGet started
Tessl Logo

comodo

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/comodo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, executable integration guide with a well-sequenced connection workflow and feedback loop. It is held back from top marks by placeholder-laden examples, slight redundancy between sections, and some brief non-essential preamble.

DimensionReasoningScore

Conciseness

The body is command-driven and lean with flag tables and runnable commands, with only minor over-explanation such as the opening "Comodo offers a range of cybersecurity products" preamble, fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

It provides concrete copy-paste commands for install, auth, connect, search, run, and proxy with a full flag table, but placeholders like CONNECTION_ID, actionId, and QUERY require substitution, matching the mostly-executable-with-minor-gaps anchor.

4 / 5

Workflow Clarity

The connection workflow is clearly sequenced with explicit state checkpoints and a feedback loop (poll for READY, handle CLIENT_ACTION_REQUIRED then re-poll), but the action-running half is less sequenced, matching the clear-sequence-most-checkpoints anchor.

4 / 5

Progressive Disclosure

The single-file skill is organized into well-labeled sections with no broken or nested references, though reference-like detail (the proxy flag table) is inlined and Popular actions overlaps Searching for actions, fitting the good-structure-minor-gaps anchor.

4 / 5

Total

16

/

20

Passed

Description

62%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 has a clear what/when structure with a distinct product anchor, but its action verbs are generic and its trigger terms lack synonyms. It is solid but not exemplary, sitting just above midpoint.

Suggestions

Replace generic verbs with concrete Comodo actions (e.g., "scan endpoints, manage firewall policies, review threat alerts") to lift specificity.

Expand the trigger clause with natural user phrases and synonyms (e.g., "Use when the user wants to check Comodo alerts, manage security policies, or pull Comodo reports").

Tie the trigger explicitly to Comodo's cybersecurity domain so it cannot be confused with a generic data-management skill.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Comodo domain and a few actions, but the verbs are generic rather than concrete and comprehensive, matching the anchor for naming domain plus 1-2 actions.

3 / 5

Completeness

It states both a clear "what" (Comodo integration; manage data, records, workflows) and an explicit "Use when the user wants to interact with Comodo data" trigger, but the when-clause is generic rather than concrete, matching the both-present-but-could-be-more-specific anchor.

4 / 5

Trigger Term Quality

Terms like "Comodo", "data", "records", and "workflows" are present but common synonyms and variations are missing, fitting the anchor for some relevant keywords without full coverage.

3 / 5

Distinctiveness Conflict Risk

The Comodo product name gives a clear niche and Comodo-scoped trigger with low conflict risk, though the generic action verbs create minor overlap risk, matching the mostly-distinct anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.