CtrlK
BlogDocsLog inGet started
Tessl Logo

kamonio

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

61

Quality

72%

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/kamonio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a strong, executable guide: concrete CLI commands throughout, a genuine polling feedback loop for connection state, and clean section structure. Its few weaknesses are minor prose padding, a dangling 'Step 2' reference, and slight section redundancy.

DimensionReasoningScore

Conciseness

The body is mostly lean, command-driven operational guidance with only minor over-explanation (the opening APM orientation paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing') that could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every common case — install, login, connection ensure, polling, action list/run, and proxy requests — plus a concrete flag table, covering the typical workflow comprehensively.

5 / 5

Workflow Clarity

The connection lifecycle is clearly sequenced with a real feedback loop (poll --wait until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the dangling 'skip to Step 2' reference and unbalanced '1b' numbering without a labeled Step 1a/2 are minor clarity gaps.

4 / 5

Progressive Disclosure

The single self-contained file is well organized with clear section headers and easy navigation, with no nested references; the only minor gap is redundancy between 'Searching for actions' and the thin 'Popular actions' section.

4 / 5

Total

17

/

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 correctly uses third-person voice and includes an explicit 'Use when' trigger, answering both what and when. Its main weakness is generic action language and missing APM-specific trigger terms that users would naturally say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete APM actions, e.g. 'Query traces, spans, and services, inspect dashboards, and automate monitoring workflows.'

Add natural trigger terms users actually say for an APM tool — 'monitoring', 'traces', 'spans', 'performance', 'APM' — to the 'Use when' clause.

Tighten the trigger to specific scenarios, e.g. 'Use when the user wants to query Kamon.io traces, spans, or service performance data.'

DimensionReasoningScore

Specificity

It names the domain ('Kamon.io integration') and lists actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete APM operations, so it stops at 'domain plus 1-2 actions, not comprehensive'.

3 / 5

Completeness

Both 'what' (Kamon.io integration that manages data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Kamon.io data') are present, but the 'when' could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

It includes the brand name and 'data', 'records', 'workflows', 'interact with Kamon.io data', but omits the natural terms a user would actually say for an APM tool (monitoring, traces, spans, performance, APM), missing common variations.

3 / 5

Distinctiveness Conflict Risk

The Kamon.io brand name gives it a clear, product-specific niche with low conflict risk, but the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap risk with other data/integration skills.

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.