Name: karbon
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

karbon

Karbon integration. Manage Organizations, Contacts, Workflows, Templates, Users, Roles. Use when the user wants to interact with Karbon data.

Quality

66%

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/karbon/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 actionable and well-structured, with executable membrane commands and a clear connection-to-action workflow including state validation. It loses points mainly on conciseness due to an unnecessary marketing intro and editorial asides.

Suggestions

Trim the opening "Karbon is a practice management platform…" paragraph and the "so you can focus on the integration logic" editorial to one neutral sentence or remove it entirely.

Fill in the empty Description column in the Popular actions table, or drop the column, so the table is self-contained.

Fix the step labeling so the referenced "Step 2" has a matching heading and the lone "1b" section is renumbered into the documented sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete command blocks, but the opening marketing paragraph ("Karbon is a practice management platform… streamline their operations and improve efficiency") and the editorial "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation Claude does not need.	3 / 5
Actionability	Copy-paste-ready commands are given throughout (npm install, membrane login, connection ensure, action list/run, request) with JSON input examples; the only gap is the empty Description column in the Popular actions table.	4 / 5
Workflow Clarity	A clear install → authenticate → connection ensure → poll-for-ready → search → run → proxy sequence exists with a state-check feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and "poll again"), though the referenced "Step 2" is never labeled and one section is oddly numbered "1b".	4 / 5
Progressive Disclosure	No bundle files exist; the single-file body is well-organized into clearly headed sections with operational content appropriately inline, though the detailed connection-state machine and 17-row action table could optionally be split out.	4 / 5
	Total	15 / 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.

A solid description that names the Karbon product, lists the manageable entities, and includes an explicit "Use when" trigger. It is distinctive and complete, though the action verbs are generic and keyword coverage is limited to the product name.

Suggestions

Replace the generic verb "Manage" with concrete operations (e.g., "Create, list, and update Organizations, Contacts, Workflows…") to raise specificity.

Broaden trigger keywords beyond the product name to natural user phrases like "Karbon contacts", "Karbon workflows", or "Karbon work items".

Make the "Use when" clause enumerate a few concrete intents (e.g., managing clients, tracking work items, assigning tasks) instead of the broad "interact with Karbon data".

Dimension	Reasoning	Score
Specificity	Names the domain plus six concrete entities ("Manage Organizations, Contacts, Workflows, Templates, Users, Roles") but the verb "Manage" is generic and no create/list/update distinction is given, so coverage is not comprehensive.	3 / 5
Completeness	It states both the "what" (manage Organizations, Contacts, Workflows, etc.) and an explicit "Use when the user wants to interact with Karbon data" trigger, but the trigger could be more specific about concrete tasks.	4 / 5
Trigger Term Quality	The only natural keyword is "Karbon" (in "interact with Karbon data"); there are no synonyms, task phrases, or variations a user might say beyond the product name.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product (Karbon) with a distinct trigger phrase gives it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/karbon/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.