Name: kartra
Rating: 56.8 (1 reviews)
Author: membranedev

kartra

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/kartra/SKILL.md

Quality

Content

56%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 genuinely actionable with executable Membrane CLI commands and a useful popular-actions table, and the connection workflow has real validation and feedback loops. Its chief problems are token waste from the marketing intro and the long inlined entity list, and the absence of any progressive-disclosure structure.

Suggestions

Remove the marketing paragraph about what Kartra is and trim the ~100-item entity list (or move it to a references/entities.md file linked from the overview) to recover tokens.

Explicitly label 'Step 2' (searching/running actions) so the forward references in the connection section resolve.

Add a brief error-recovery note for `membrane action run` failures so the workflow's validation coverage is complete.

Dimension	Reasoning	Score
Conciseness	The marketing intro ('Kartra is an all-in-one marketing platform designed for entrepreneurs...') and the ~100-item inlined entity list (with duplicates such as Funnels appearing twice) are padded sections that consume tokens without adding actionable guidance.	2 / 5
Actionability	Concrete, copy-paste-ready CLI commands are given for install, login, connection, action search/run, and proxy, plus a popular-actions table with real keys; the only gaps are ID/intent placeholders that require substitution.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run sequence exists with state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the referenced 'Step 2' is not explicitly labeled and action-run error recovery is not addressed.	4 / 5
Progressive Disclosure	Section headings provide some structure, but the large entity enumeration is inlined content that could live in a separate reference file, and there are no external references or signaled navigation to deeper material.	3 / 5
	Total	13 / 20 Passed

Description

73%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 third-person, answers both what and when, and is clearly distinct via the unique 'Kartra' trigger. Its main weakness is a generic 'Manage ... and more' verb and a 'when' clause that does not surface the specific entity triggers it already names.

Suggestions

Replace the generic 'Manage ... and more' with two or three concrete verbs tied to the entities (e.g., 'Create and update Leads, manage Deals and Pipelines, assign Tags').

Expand the 'when' clause to list the natural trigger phrases (e.g., 'Use when the user mentions Kartra leads, deals, pipelines, tags, or subscriptions').

Drop 'and more' or replace it with the remaining entity categories so coverage reads as comprehensive rather than open-ended.

Dimension	Reasoning	Score
Specificity	Names the domain (Kartra) and lists six concrete entities (Persons, Organizations, Leads, Deals, Pipelines, Activities), but the only verb is the generic 'Manage ... and more', so the concrete actions are minimal rather than comprehensive.	3 / 5
Completeness	It answers both 'what' ('Manage Persons, Organizations, Leads, Deals, Pipelines, Activities') and 'when' ('Use when the user wants to interact with Kartra data'), but the 'when' clause is generic and does not enumerate the specific entity triggers.	4 / 5
Trigger Term Quality	Natural terms a user would say are present ('Kartra', 'Leads', 'Deals', 'Pipelines', 'Activities'), but common synonyms and variations of those entity names are missing, placing it just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	'Kartra' is a uniquely named marketing platform with a clear niche, so the trigger is highly distinct and conflict risk with other skills is minimal.	5 / 5
	Total	16 / 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/kartra/SKILL.md
Commit: f484c82

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