Name: esputnik
Rating: 62.4 (1 reviews)
Author: membranedev

esputnik

ESputnik integration. Manage Contacts, Templates, Campaigns, Events, Reports. Use when the user wants to interact with ESputnik data.

Quality

73%

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

Quality

Content

68%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 highly actionable with concrete Membrane commands and a solid connection-setup workflow, but it is padded with unnecessary marketing prose and lacks validation guidance for destructive and batch contact/email operations.

Suggestions

Remove the opening marketing-automation paragraph and trim explanatory padding ('so you can focus on the integration logic rather than auth plumbing') to assume Claude's competence and save tokens.

Add an explicit validation/confirmation checkpoint before destructive or batch actions (e.g., 'Before running delete-contact or batch send-email/send-sms, confirm the target contact IDs and count with the user, and verify the result via get-message-status or get-contact').

Consider moving the full Popular actions table into a references/actions.md file and keeping only the top few inline, so the SKILL.md overview stays lean while the full catalog is one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands and tables, but the opening marketing paragraph ('marketing automation platform designed to help businesses... nurture leads, engage customers') and phrases like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude does not need and could be trimmed.	3 / 5
Actionability	Provides copy-paste ready, fully executable commands throughout (install, login, connection ensure, action list/run, request) plus a Popular actions table with concrete action keys, covering the common integration cases.	5 / 5
Workflow Clarity	The connection setup flow is well-sequenced with state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-until-ready feedback loop, but destructive and batch operations exposed via 'Delete Contact' and batch 'Send Email/SMS' have no validation or confirmation step, capping the score per the destructive/batch rule.	3 / 5
Progressive Disclosure	Well-organized with clear section headers (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no bundle files to navigate; the 16-row Popular actions table is borderline content that could be externalized, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

78%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 concise, uses third person, and clearly states both capabilities and an explicit trigger clause, with a distinct platform-specific niche. Main gap is the generic 'Manage' verb and the broad 'interact with ESputnik data' trigger phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain plus several entities ('Manage Contacts, Templates, Campaigns, Events, Reports') giving broad coverage, but the single generic verb 'Manage' keeps it just short of comprehensive concrete actions.	4 / 5
Completeness	Provides a clear 'what' ('ESputnik integration. Manage Contacts, Templates, Campaigns, Events, Reports.') and an explicit 'when' clause ('Use when the user wants to interact with ESputnik data.'), though the trigger could be more specific than 'interact with ESputnik data'.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('Contacts', 'Campaigns', 'Templates', 'Reports') alongside 'ESputnik', but lacks synonyms or variants, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Explicitly names the specific platform 'ESputnik' in both the what and the when, giving it a clear niche with distinct, platform-specific triggers and minimal conflict risk.	5 / 5
	Total	17 / 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/esputnik/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.