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

charlie

Charlie integration. Manage data, records, and automate workflows. Use when the user wants to interact with Charlie 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/charlie/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 content is a mostly executable, well-structured Membrane CLI guide with a clear connect-to-run workflow and validation feedback loop, but it is marred by an opening leaked-LLM paragraph and vague filler that hurt token efficiency.

Suggestions

Delete the leaked model output paragraph after the '# Charlie' heading and the filler line 'Use action names and parameters as needed.'

Replace the sparse 'Charlie Overview' bullet list (Meeting/Transcript/Contact) with the actual action names users will discover via `membrane action list`.

Add a final verification step after `membrane action run` (e.g., check the `output` field for expected shape or errors) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The bulk is a lean command reference, but the body opens with leaked model output ('I don't have enough information to do that. I'm a large language model...') and filler like 'Use action names and parameters as needed.' that are pure noise padding.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a complete proxy flag table, with only minor placeholder gaps (CONNECTION_ID, QUERY).	4 / 5
Workflow Clarity	The connect-then-run sequence is clearly ordered with a state-validation feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), though there is no final verification that a run action succeeded beyond reading the output.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is appropriately sectioned (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) for a CLI guide, with only a thin Overview section as a minor gap.	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 successfully pairs a 'what' with an explicit 'Use when...' trigger and anchors on the distinct Charlie niche, but its action verbs are generic rather than concrete and it misses natural synonym variations.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Charlie actions (e.g., 'List meetings and transcripts, fetch contacts, sync employee records').

Expand the trigger clause with natural phrasings users would say, e.g. 'Use when the user mentions Charlie, CharlieHR, meeting transcripts, or contact records.'

Dimension	Reasoning	Score
Specificity	Names the Charlie domain but the listed actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities, matching the 'names domain but actions minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Charlie data') are present; the 'when' is clear but could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant terms ('Charlie', 'Charlie data', 'records', 'workflows') and an explicit 'Use when the user wants to interact with Charlie data' trigger, but lacks common synonyms or variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	'Charlie integration' with a Charlie-specific trigger carves a clear niche with minimal conflict risk, though the generic 'data/records' terms leave minor overlap with other data skills.	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/charlie/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.