Name: impression
Rating: 53.6 (1 reviews)
Author: membranedev

impression

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

Quality

60%

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

Quality

Content

57%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 contains genuinely actionable Membrane CLI commands and a solid connection-polling workflow, but it is undermined by junk content (a refusal artifact and mismatched Optimizely/overview material), inconsistent step numbering, and a lack of validation checkpoints for mutating actions. It is also monolithic with no progressive disclosure to reference files.

Suggestions

Remove the broken refusal sentence ("I'm sorry, but I cannot fulfill that request..."), the mismatched Optimizely docs link, and the inconsistent "Impression Overview" tree that does not match the signature-workflow content.

Add an explicit validation/verification checkpoint after running mutating actions (e.g., re-query the created signature request or check its status) and fix the broken step numbering so "Step 1"/"Step 2" are labeled consistently.

Move the Popular actions catalog and proxy flag reference tables into separate reference files (e.g., ACTIONS.md, PROXY.md) and link them from SKILL.md to enable progressive disclosure and reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The core Membrane CLI guidance is mostly lean, but the body wastes tokens on a broken refusal sentence ("I'm sorry, but I cannot fulfill that request..."), an irrelevant Optimizely docs link, and a mismatched "Impression Overview" tree, so it includes unnecessary content that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands across install, login, connection ensure, polling, action list/run, and proxy, plus a Popular actions table with real keys; minor gaps are unfilled placeholders (CONNECTION_ID, <actionId>, <id>) and no full end-to-end worked example.	4 / 5
Workflow Clarity	A rough sequence exists with good feedback loops for connection polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the numbering is inconsistent ("skip to Step 2" with no Step 1) and running mutating actions (create signature request/workflow, send notification) has no validation/verification checkpoint, which caps this at 3.	3 / 5
Progressive Disclosure	No bundle/reference files exist and the body is a monolithic >50-line SKILL.md with content that could live in separate files (the Popular actions catalog, proxy flag reference table) inlined; section headers give some structure but there are no one-level-deep references to deeper material.	3 / 5
	Total	13 / 20 Passed

Description

62%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 competent: it names a clear product niche with a concrete entity list and an explicit Use-when trigger. Its main weaknesses are a single generic action verb plus the vague "and more," and a circular trigger phrase that lacks natural synonyms.

Suggestions

Replace the single generic verb "Manage" with concrete actions per entity (e.g., create, update, search, archive) and drop the vague "and more" to sharpen specificity.

Add natural trigger phrases and synonyms users would actually say (e.g., "Impression CRM," "Impression records," specific entity names like Deals or Leads) instead of the circular "interact with Impression data."

Tighten the Use-when clause to reference concrete intents (e.g., creating deals, tracking leads, logging activities) to lift completeness and distinctiveness toward 5.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete entities ("Persons, Organizations, Deals, Leads, Projects, Activities") but applies only one generic verb ("Manage ... and more"), so it names the domain and some coverage without comprehensive concrete actions.	3 / 5
Completeness	Both a clear "what" ("Manage Persons, Organizations, Deals, Leads, Projects, Activities") and an explicit "when" ("Use when the user wants to interact with Impression data") are present, though the "when" could be more specific.	4 / 5
Trigger Term Quality	"Impression" is the key keyword and a Use-when clause exists ("Use when the user wants to interact with Impression data"), but the trigger phrasing is circular and lacks natural synonyms or variations users would say.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a named product ("Impression integration", "interact with Impression data") gives it a mostly-distinct niche with only minor overlap risk, though the generic "interact with data" phrasing is not maximally distinct.	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/impression/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.