Name: enigma
Rating: 68 (1 reviews)
Author: membranedev

enigma

Enigma integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with Enigma data.

Quality

68%

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

Quality

Content

75%Weight 20%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, mostly executable integration guide with a genuine polling feedback loop, but is held back by a missing Step 2, stray noise text, and a lack of progressive disclosure for the longer reference-style tables.

Suggestions

Resolve the dangling "skip to Step 2" reference by either adding a numbered Step 2 section or rewriting to point at the real next action.

Remove the noise line "Official docs: I am sorry, but 'Enigma' is too ambiguous..." which adds no actionable value.

Move the full clientAction field schema and the proxy flag table into a references file (e.g. REFERENCES.md) and keep SKILL.md a lean overview, enabling a higher progressive-disclosure score.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with heavy use of executable code blocks and tables, with only minor over-explanation (the "focus on integration logic rather than auth plumbing" aside, the repeated clientAction field enumeration, and the stray "Official docs: I am sorry..." line).	4 / 5
Actionability	Concrete, runnable `membrane` commands appear throughout (login, connection ensure, action run, request) with flags shown, but action IDs are left as placeholders and the Popular actions table gives Keys without example runnable ids.	4 / 5
Workflow Clarity	The install → auth → connect → poll-for-READY → search → run sequence is clear and includes a state-polling feedback loop, but "skip to Step 2" references a missing section and numbering is inconsistent ("1b"), with no output validation before proceeding.	4 / 5
Progressive Disclosure	No bundle directories exist and the file makes no references; it is a single well-organized file with clear headers and tables, but at ~160 lines some inline material (the full clientAction schema, proxy flag table) could be split into reference files to keep the overview leaner.	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 20%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 cleanly states a domain and entity list with an explicit Use-when clause, but relies on the single verb "Manage" and a generic trigger phrase rather than distinct concrete actions and natural keywords. Distinctiveness is solid thanks to the brand anchor and named entities.

Suggestions

Replace the single verb "Manage" with distinct concrete operations per entity (e.g., "Create and search Deals, screen Customers, look up Businesses by ID").

Expand the Use-when clause with concrete trigger phrases users would naturally say (e.g., "Use when the user wants to match a business, screen a customer, or run a KYB check").

Drop the open-ended "and more" or replace it with a bounded list so the trigger is less likely to fire for unrelated skills.

Dimension	Reasoning	Score
Specificity	"Manage Deals, Persons, Organizations, Leads, Projects, Activities" names the domain and many entity types, but collapses all actions into the single generic verb "Manage" rather than listing distinct concrete operations.	3 / 5
Completeness	It explicitly answers both what ("Enigma integration... Manage Deals, Persons, Organizations...") and when ("Use when the user wants to interact with Enigma data"), though the when-clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural trigger is the brand name "Enigma" inside "Use when the user wants to interact with Enigma data"; common variations and synonyms users would actually say are missing.	3 / 5
Distinctiveness Conflict Risk	Anchoring on the "Enigma" brand plus a specific entity list carves a recognizable niche with only minor overlap risk against generic CRM/sales skills, though "and more" broadens the scope.	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/enigma/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.