Name: kosli
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kosli

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

Quality

62%

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/kosli/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 a practical, command-driven integration guide with strong actionability and a clear connection-state workflow. Its weaknesses are mild prose padding and a couple of structural/numbering inconsistencies rather than substantive gaps.

Suggestions

Trim padding such as the Kosli definition sentence, the 'so you can focus on the integration logic' aside, and the duplicated action-list command in 'Popular actions'.

Fix the dangling 'Step 2' reference by labeling the corresponding section, and renumber the '1b' subsection consistently.

Either populate 'Popular actions' with a few real example Kosli actions or remove the section to avoid promising content it doesn't deliver.

Dimension	Reasoning	Score
Conciseness	The body is largely command-focused and efficient, but includes unnecessary prose such as the Kosli intro sentence, 'Membrane handles authentication… so you can focus on the integration logic', a repeated action-list command, and 'This will burn less tokens and make communication more secure' that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxy requests with a flag table, but placeholders (CONNECTION_ID, actionId) and a 'Popular actions' section that only reprints the discovery command leave minor gaps.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll sequence with an explicit state-feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling, but a dangling 'Step 2' reference and an oddly numbered '1b' subsection introduce minor gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized with clear section headers (Overview, Working with Kosli, Install, Authentication, Connecting, Searching, Proxy, Best practices) and needs no external references for a CLI guide, but minor organization issues like the 'Popular actions' stub and '1b' heading prevent a top score.	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 names a clear niche and includes an explicit 'Use when…' trigger, satisfying the completeness baseline. Its main weakness is generic, non-concrete capability language ('Manage data, records, and automate workflows') that under-specifies what the skill actually does.

Suggestions

Replace generic verbs with concrete Kosli capabilities, e.g. 'Query Kosli environments, attestations, artifacts, and flows; run reports and automate compliance workflows.'

Expand the trigger phrase with natural user phrasings, e.g. 'Use when the user wants to query Kosli environments, attestations, artifacts, or deployment compliance evidence.'

Dimension	Reasoning	Score
Specificity	The domain is named ('Kosli integration') but the listed actions — 'Manage data, records, and automate workflows' — are generic buzzwords rather than concrete capabilities, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It states both what it does ('Kosli integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Kosli data.'), but the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The product name 'Kosli' appears with the trigger phrase 'Use when the user wants to interact with Kosli data', giving some relevant keywords, but it lacks common variations or synonyms for a niche tool.	3 / 5
Distinctiveness Conflict Risk	'Kosli integration' is a clear, narrow niche tied to a specific named product, making it mostly distinct with only minor overlap risk, though the generic action verbs slightly weaken full distinctiveness.	4 / 5
	Total	13 / 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/kosli/SKILL.md
Commit: f484c82

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