CtrlK
BlogDocsLog inGet started
Tessl Logo

kyvio

Kyvio integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Kyvio data.

61

Quality

73%

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/kyvio/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 body is highly actionable with concrete CLI commands and a well-sequenced connection workflow that includes state-based checkpoints. Its weaknesses are a marketing-flavored intro and minor structural gaps (dangling Step references, no progressive file split).

Suggestions

Trim the marketing-style opening paragraph ("Kyvio is an all-in-one platform...") to a one-line purpose statement; Claude does not need the entrepreneur/course-creator positioning.

Label the workflow steps explicitly (Step 1, Step 2) or remove the "skip to Step 2" references so the dangling pointers resolve.

Provide at least one fully concrete action example with real values instead of only <actionId>/CONNECTION_ID/QUERY placeholders to push actionability toward copy-paste-ready.

DimensionReasoningScore

Conciseness

The marketing-tone intro ("all-in-one platform designed for entrepreneurs and businesses to build and sell online courses...") and padded phrases ("so you can focus on the integration logic rather than auth plumbing", "burn less tokens") add explanation that could be tightened.

3 / 5

Actionability

Concrete, copy-paste-ready commands with flags appear throughout (membrane connection ensure, action list, action run --input), but examples rely on placeholders like <actionId> and CONNECTION_ID rather than fully filled-in concrete cases.

4 / 5

Workflow Clarity

There is a clear install→auth→connect→poll→search→run sequence with a state-machine checkpoint (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the "skip to Step 2" references point to a Step 2 that is never explicitly labeled, a minor gap.

4 / 5

Progressive Disclosure

It is a single, well-organized file with clear section headers and no nested references; at ~160 lines it exceeds the simple-skill threshold, and some inline tables (proxy flags, popular actions) could live in reference files, so it sits just below the 5 anchor.

4 / 5

Total

15

/

20

Passed

Description

78%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 is well-constructed: it names concrete managed entities, includes an explicit "Use when" trigger, and ties everything to a distinctive branded niche. The main weakness is the generic "interact with Kyvio data" trigger phrasing and the vague "and more" hedge.

DimensionReasoningScore

Specificity

"Manage Persons, Organizations, Deals, Leads, Projects, Activities" lists several concrete managed entities, but the trailing "and more" leaves minor coverage gaps, fitting the several-specific-actions anchor rather than comprehensive.

4 / 5

Completeness

It states both what ("Manage Persons, Organizations, Deals...") and when ("Use when the user wants to interact with Kyvio data"), but the trigger clause is somewhat generic rather than packed with concrete trigger phrases, so it sits below the 5 anchor.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with Kyvio data" plus domain terms (Persons, Deals, Leads, Projects, Activities) give good natural-keyword coverage, though a few common variations (courses, funnels, subscribers) are absent.

4 / 5

Distinctiveness Conflict Risk

"Kyvio" is a distinct branded niche with explicit Kyvio-only triggers, giving minimal overlap risk with other skills.

5 / 5

Total

17

/

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.