Name: charisma
Rating: 60.8 (1 reviews)
Author: membranedev

charisma

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

Quality

71%

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

Quality

Content

81%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 content is highly actionable with executable CLI commands and a clear connection state machine, well-structured into navigable sections; it is held back only by a thin overview section and the absence of an explicit verification checkpoint before running actions.

Suggestions

Add an explicit validation step before running actions (e.g., confirm connection state is READY and verify the discovered action's inputSchema) to strengthen the workflow's error recovery.

Flesh out or remove the "Charisma Overview" placeholder (Story / Character / Character Template) so it either guides action selection or is dropped for conciseness.

Trim the explanatory Membrane/auth preamble in "Working with Charisma" since Claude can infer auth handling from the commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands and minimal padding, though the overview paragraph and a few explanatory sentences about Membrane/auth restate context Claude could infer.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands for install, login, connection, action discovery/execution, and proxy requests with concrete flags and example payloads covering the common cases.	5 / 5
Workflow Clarity	Clear sequence from install → authenticate → ensure connection → poll for READY → search/run actions, with state-based branching (READY, CLIENT_ACTION_REQUIRED, error states), but lacks an explicit validation/verification step before executing actions on a confirmed connection.	4 / 5
Progressive Disclosure	Well-organized into clearly signaled sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no bundle files needed; minor gaps such as the underdeveloped "Charisma Overview" placeholder section keep it just short of fully clean.	4 / 5
	Total	17 / 20 Passed

Description

61%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 brand-specific and includes an explicit "Use when..." trigger, but the action list is generic rather than reflecting Charisma's actual storytelling/character capabilities, leaving it somewhat interchangeable.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with Charisma-specific ones like "create characters, write dialogue, and build branching storylines".

Expand the trigger clause with natural user phrases such as "when the user mentions characters, dialogue, stories, or branching narratives".

Adopt third-person action verbs and concrete terms to lift specificity from generic data-management language.

Dimension	Reasoning	Score
Specificity	Names the domain (Charisma) and a few generic actions like "Manage data, records, and automate workflows" but these are broad and not tied to concrete Charisma-specific capabilities.	3 / 5
Completeness	Has a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Charisma data"), though the "when" is somewhat generic rather than enumerating concrete triggers.	4 / 5
Trigger Term Quality	"interact with Charisma data" surfaces the brand name and "data" as keywords, but common natural variations (characters, stories, dialogue, branching storylines) that users would actually say are missing.	3 / 5
Distinctiveness Conflict Risk	The brand-specific term "Charisma" gives it a clear niche with minimal conflict risk, though the generic "Manage data, records, and automate workflows" phrasing could overlap with other data-management skills.	4 / 5
	Total	14 / 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/charisma/SKILL.md
Commit: f484c82

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