Name: encharge
Rating: 60 (1 reviews)
Author: membranedev

encharge

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

Quality

70%

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/encharge/SKILL.md

Quality

Content

68%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 complete CLI commands and a clear connection/polling workflow, but it is weakened by background prose Claude already knows and by the absence of validation steps before destructive action runs.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive action runs (e.g. 'For delete/archive actions, confirm the target person id or re-fetch it first').

Trim the opening Encharge overview paragraph and the auth-plumbing rationale to assumed knowledge.

Consider moving the 15-row 'Popular actions' table and proxy flag reference into a references/ file surfaced as a one-level link from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable commands, but the opening paragraph explaining what Encharge is and prose like 'so you can focus on the integration logic rather than auth plumbing' restate concepts Claude already knows and could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every step (install, login, connection ensure/get, action list, action run, request) plus a table of concrete action keys with flags and JSON usage.	5 / 5
Workflow Clarity	The connect/poll loop is well sequenced with explicit state handling (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but the skill exposes destructive actions (archive person, delete webhook, delete field) with no validation or verification checkpoint before running them, which caps the score per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly labeled sections, and no bundle files exist to mis-navigate; the sizeable inline 'Popular actions' and proxy-flag tables could optionally live in a reference file, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

71%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 clearly identifies a specific product niche and lists concrete managed entities with an explicit 'Use when' trigger. It is held back from top marks by a single generic action verb and a thin, broad trigger clause lacking synonyms.

Suggestions

Replace the single verb 'Manage' with several varied concrete actions (e.g. 'Create, update, tag, and archive Persons; search segments; manage webhooks').

Expand the trigger clause with natural variations, e.g. 'Use when the user wants to sync contacts, send broadcasts, manage email flows, or interact with Encharge data.'

Add the file extension or API surface terms users may reference (e.g. 'Encharge API', 'encharge.io').

Dimension	Reasoning	Score
Specificity	Names the Encharge domain and lists several concrete managed entity types ('Persons, Organizations, Deals, Pipelines, Activities, Notes and more'), but the single generic verb 'Manage' keeps it just shy of fully comprehensive, varied actions.	4 / 5
Completeness	It answers both 'what' (Encharge integration managing listed entities) and 'when' ('Use when the user wants to interact with Encharge data'), but the 'when' clause is a single broad trigger that could be more explicit or specific.	4 / 5
Trigger Term Quality	The product name 'Encharge' and the natural phrase 'interact with Encharge data' are present, but it lacks common synonyms or variations a user might say (e.g. 'marketing automation', 'email', 'contacts').	3 / 5
Distinctiveness Conflict Risk	Naming a specific SaaS product ('Encharge') carves out a clear niche with distinct triggers and minimal overlap risk with other skills.	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/encharge/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.