CtrlK
BlogDocsLog inGet started
Tessl Logo

kilo-ssl

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

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/kilo-ssl/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is well-structured and highly actionable with concrete CLI commands and a clear connection workflow including feedback loops. Its main weakness is conciseness, owing to a speculative intro paragraph and minor padding.

Suggestions

Remove the hedged opening paragraph ('Kilo SSL likely provides... probably used by...') and the 'so you can focus on the integration logic' aside; these add tokens without actionable value.

Reconcile the membrane vs npx @membranehq/cli invocation style so commands are consistent and copy-paste-stable, and show how to resolve CONNECTION_ID from a prior command's output.

Merge or enrich the 'Popular actions' section so it is not redundant with 'Searching for actions', and add brief guidance for handling action-run errors and proxy failures.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the hedged opening ('likely provides', 'probably used by DevOps engineers') and a few padded lines ('so you can focus on the integration logic rather than auth plumbing') are unnecessary explanation Claude does not need.

3 / 5

Actionability

Provides concrete, executable commands throughout (login, connection ensure, action list/run, request) with copy-paste-ready blocks; minor gaps from the membrane vs npx inconsistency and unresolved CONNECTION_ID placeholders keep it just below 5.

4 / 5

Workflow Clarity

A clear install→authenticate→connect→search→run sequence is present with explicit connection-state checkpoints and a polling feedback loop for BUILDING/CLIENT_ACTION_REQUIRED; minor 'Step 2'/'1b' labeling gaps and absent action-level error handling keep it below 5.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the single file is organized into clear, well-labeled sections. It sits above the 'some structure' anchor but the thin, partly redundant 'Popular actions' section prevents a 5.

4 / 5

Total

15

/

20

Passed

Description

57%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 correctly pairs an explicit 'Use when' trigger with the Kilo SSL niche, but its capability list is generic rather than concrete. Specificity and trigger-term coverage are the main weaknesses.

Suggestions

Replace generic verbs with concrete Kilo SSL actions, e.g. 'Order and renew SSL certificates, manage domains and validations' instead of 'Manage data, records, and automate workflows'.

Add natural trigger synonyms and file/object terms users would say, such as 'SSL certificates', 'cert renewals', or 'certificate validation'.

Tighten the 'what' to list 2-3 specific capabilities so the description answers what it does concretely, not just at a high level.

DimensionReasoningScore

Specificity

Names the Kilo SSL domain but the actions ('Manage data, records, and automate workflows') are generic and not concrete, matching the 'names domain but actions minimal/generic' anchor rather than the concrete-action anchors at 3+.

2 / 5

Completeness

Both a 'what' (manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Kilo SSL data') are present; the trigger is explicit but the 'what' is generic, sitting between the 3 and 5 anchors.

4 / 5

Trigger Term Quality

The main natural term 'Kilo SSL' / 'Kilo SSL data' is present, but surrounding terms (data, records, workflows) are generic and common variations or synonyms are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Kilo SSL' is a specific named product giving a clear niche with distinct triggers, but the generic action verbs ('manage data, records, automate workflows') create minor overlap risk with other data-management skills.

4 / 5

Total

13

/

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.