CtrlK
BlogDocsLog inGet started
Tessl Logo

kotive

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

62

Quality

74%

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/kotive/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 body is highly actionable and well-sequenced with real validation feedback loops, with only minor conciseness and labeling gaps.

DimensionReasoningScore

Conciseness

The body is dominated by copy-paste commands and a structured state-handling block, but includes minor editorializing such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed, matching the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

Every section provides fully executable, copy-paste-ready commands (install, login, connection ensure, action list/run, proxy request with a flag table) covering the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The install→authenticate→connect→search→run/proxy sequence is clear with state-based polling and a re-poll feedback loop after CLIENT_ACTION_REQUIRED, but "skip to Step 2" references a Step 2 that is never labeled, leaving a minor sequencing gap per the clear-sequence-with-minor-gaps anchor.

4 / 5

Progressive Disclosure

The skill is a single well-organized file with clearly headed sections and no nested references; because it exceeds 50 lines the simple-skill exception does not apply, so it sits at the good-structure-with-minor-gaps anchor rather than the top anchor.

4 / 5

Total

17

/

20

Passed

Description

66%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 answers both what and when in third person and targets a distinct niche, but its capability list leans generic and its trigger-term coverage is narrow.

Suggestions

Replace generic verbs with concrete Kotive capabilities, e.g. "Create and manage workflows, forms, tasks, contacts, and files" instead of "Manage data, records, and automate workflows".

Broaden the trigger phrase to surface natural synonyms, e.g. "Use when the user wants to automate a business process, build a Kotive workflow, or manage Kotive forms, tasks, contacts, or records."

Tie the "when" clause more specifically to the actions listed so the trigger guidance reflects what the skill actually does.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Kotive domain plus three actions, but "manage data" and "manage records" are generic rather than concrete capabilities, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Both "what" (manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Kotive data") are present and explicit, but the "when" could be more specific about workflows/automation triggers, matching the anchor where the when-clause could be more explicit.

4 / 5

Trigger Term Quality

Natural terms present are limited to "Kotive", "data", and "workflows" via "Use when the user wants to interact with Kotive data"; common variations or synonyms (e.g. "automate", "business process", "forms") are missing, fitting the anchor with some relevant keywords but missing variations.

3 / 5

Distinctiveness Conflict Risk

"Kotive integration" targets a single named business-process platform with distinct triggers, giving it a clear niche and minimal risk of triggering for the wrong skill, matching the clear-niche anchor.

5 / 5

Total

15

/

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.