Name: carbone
Rating: 55.2 (1 reviews)
Author: membranedev

carbone

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/carbone/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 a well-structured, actionable guide with concrete CLI commands and a clear connection workflow including state-polling checkpoints. Its main weaknesses are mild prose padding, a thin overview section, and a dangling 'Step 2' reference.

Suggestions

Trim explanatory filler ('so you can focus on the integration logic rather than auth plumbing') and remove or flesh out the empty 'Carbone Overview' bullet list.

Resolve the dangling 'Step 2' reference by either labeling the next section as 'Step 2' or rewording to 'skip to Running actions'.

Consider moving the popular-actions table and proxy flag reference into a separate references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and code, but includes some unnecessary prose ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and a thin, low-value 'Carbone Overview' bullet list.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flag tables, but uses placeholders like CONNECTION_ID and actionId that require substitution.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based checkpoints and a poll-until-READY feedback loop, but the document references a 'Step 2' that is not labeled as a heading, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Content is well-organized into clear headed sections in a single file with no nested references, though at ~160 lines some material (the popular-actions and proxy-flag tables) could arguably live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 and includes both a 'what' and a 'when' clause, but its action language is generic rather than naming Carbone-specific capabilities. Trigger coverage is adequate but thin on synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Carbone actions such as rendering documents from templates, uploading/downloading templates, and generating reports.

Expand the 'when' trigger with natural phrasings users would actually say, e.g. 'Use when the user wants to generate reports, render documents from templates, or convert JSON data into spreadsheets.'

Add file-format and synonym triggers (e.g. templates, .template, rendered reports) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the Carbone domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete Carbone capabilities like rendering documents or managing templates.	2 / 5
Completeness	Both 'what' (Carbone integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with Carbone data') are present, though the 'when' clause could be more specific.	4 / 5
Trigger Term Quality	Relevant keywords appear ('Carbone', 'data', 'records', 'workflows') with a natural 'Use when... interact with Carbone data' trigger, but common variations and synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The proper-noun trigger 'Carbone' gives it a clear niche with minimal conflict risk, though the surrounding action language ('manage data, records') is generic enough to allow minor overlap.	4 / 5
	Total	13 / 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/carbone/SKILL.md
Commit: f484c82

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