Name: saleslens
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

saleslens

SalesLens integration. Manage Organizations, Users. Use when the user wants to interact with SalesLens data.

Quality

61%

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

Quality

Content

60%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 a largely actionable CLI reference with a strong connection-state validation loop, but it is marred by a marketing-fluff intro and a stray 'I am sorry, I cannot provide...' apology that waste tokens. Workflow sequencing is clear though step numbering is inconsistent.

Suggestions

Remove the marketing paragraph and the 'Official docs: I am sorry...' apology line; if no public docs URL exists, omit the line entirely.

Fix the broken step numbering: define explicit Step 1 / Step 2 labels or remove the dangling 'skip to Step 2' and '1b' references.

De-duplicate the action-list command between 'Searching for actions' and 'Popular actions' to tighten organization.

Dimension	Reasoning	Score
Conciseness	Quotes "SalesLens is a sales analytics platform that helps sales teams track performance..." (marketing fluff Claude does not need), "Official docs: I am sorry, I cannot provide the API documentation URL..." (a uniquely wasteful apology line), and "so you can focus on the integration logic rather than auth plumbing" — several unnecessary padded sections in an otherwise lean command reference.	2 / 5
Actionability	Quotes concrete copy-paste commands like `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://saleslens.io/" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --json`, plus a flags table — mostly executable with minor gaps from placeholders (CONNECTION_ID, QUERY, <code>).	4 / 5
Workflow Clarity	Quotes the connection-state polling loop with explicit checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and 'poll again' recovery guidance, giving a clear sequence with most checkpoints present; the broken step labeling ('Step 2' referenced without a defined Step 1, '1b' without '1a') is a minor gap.	4 / 5
Progressive Disclosure	The body is a single self-contained file with clear section headers (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no nested references; structure is good with minor organization gaps like the 'Popular actions' section repeating the action-list command from 'Searching for actions'.	4 / 5
	Total	14 / 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 answers both 'what' and 'when' and benefits from a named, distinct app, but relies on a generic 'Manage' verb and a vague 'interact with SalesLens data' trigger. It is solid but lacks concrete action verbs and specific user-facing trigger phrases.

Suggestions

Replace the generic 'Manage' with concrete action verbs (e.g., 'list, create, update, and delete Organizations and Users').

Expand the 'Use when...' clause with concrete natural-language triggers (e.g., 'Use when the user wants to manage SalesLens organizations, add or update users, or query opportunity data').

Include commonly used synonyms/extensions in the trigger (e.g., 'SalesLens accounts, contacts, opportunities').

Dimension	Reasoning	Score
Specificity	Quotes "Manage Organizations, Users" — it names the domain (SalesLens) and enumerates two specific managed entities, which is more concrete than the level-2 'Processes PDF files', though the verb 'Manage' itself is generic with no concrete sub-actions enumerated.	3 / 5
Completeness	Quotes "Manage Organizations, Users" (what) and "Use when the user wants to interact with SalesLens data" (when) — both are present, but the 'when' clause is somewhat generic rather than listing concrete trigger phrases, matching the anchor where 'when' could be more explicit.	4 / 5
Trigger Term Quality	Quotes "Organizations, Users" and "interact with SalesLens data" — relevant domain keywords are present, but the trigger phrasing is generic and missing common synonyms/variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	Quotes "SalesLens" — the named specific app gives it a clear niche with low conflict risk, but the generic 'Manage Organizations, Users' actions could overlap with other CRM-style skills absent the SalesLens name, so it is mostly distinct with minor overlap risk.	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/saleslens/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.