Name: pulsetic
Rating: 56.8 (1 reviews)
Author: membranedev

pulsetic

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

Quality

65%

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/pulsetic/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 body is a well-structured, actionable CLI guide with concrete commands and a solid connection-state feedback loop. Its main weaknesses are minor verbosity (a marketing sentence and repeated command examples), a slightly fragmented step numbering, and inlined reference material that could be split out.

Suggestions

Remove the marketing sentence about who uses Pulsetic ('It's used by developers, IT professionals, and business owners...') and de-duplicate the `membrane action list` command that appears in both 'Searching for actions' and 'Popular actions'.

Fix the step numbering: resolve the dangling 'skip to Step 2' reference and label the sections after the connection flow (e.g., 'Step 2: Discover and run actions') so the end-to-end sequence is explicit.

Consider moving the proxy flags table and the detailed clientAction state map into a separate reference file, keeping SKILL.md as a lean overview with one-level-deep, clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples, but includes unnecessary padding such as 'It's used by developers, IT professionals, and business owners to ensure their online services are always available and performing optimally' and near-duplicate `membrane action list` invocations in both 'Searching for actions' and 'Popular actions'. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' (anchor 3), below anchor 4 which requires only minor trimmable instances.	3 / 5
Actionability	The skill provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action run with JSON input, request with a full flags table). This matches anchor 4 ('mostly executable guidance; concrete code or commands with minor gaps'); it does not reach anchor 5 because the end-to-end flow from connection id to a concrete action invocation is shown in fragments rather than one fully-wired example covering a common case.	4 / 5
Workflow Clarity	The connection flow has a clear feedback loop — poll until READY, branch on CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, then re-poll — matching anchor 4's 'clear sequence with most checkpoints present'. It does not reach anchor 5 because step numbering is fragmented (a dangling 'skip to Step 2' reference and a '1b' subsection with no labeled Step 2), leaving the overall sequence slightly implicit.	4 / 5
Progressive Disclosure	The skill is a single file (no references/scripts/assets bundle) organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), matching anchor 4's 'good structure; most content appropriately placed'. It does not reach anchor 5 because at ~140 lines some reference material (the proxy flags table, the detailed clientAction state map) is inlined rather than split out, and there is minor repetition across sections.	4 / 5
	Total	15 / 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 has an explicit what-and-when structure tied to a named product, but its action verb is generic ('Manage') and its trigger phrase ('interact with Pulsetic data') lacks natural, specific keywords. It is functional but could be sharper and more trigger-rich.

Suggestions

Replace the single generic verb 'Manage' with multiple distinct concrete actions (e.g., 'Create and update monitors, view checks, manage notification groups and users') so capabilities are specific rather than implied.

Tighten the trigger clause with concrete natural phrases a user would say, e.g. 'Use when the user wants to check website uptime, review monitor status, or manage Pulsetic monitors, checks, and notification groups.'

Reconcile the entity list with the actual product: the body describes Pulsetic as a website-monitoring tool (Monitors, Checks, Notification Groups, Users), yet the description lists CRM entities (Leads, Persons, Organizations, Deals, Projects, Pipelines) that do not match, which muddies distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain and a concrete list of entities ('Manage Leads, Persons, Organizations, Deals, Projects, Pipelines and more'), but the only action verb is the generic 'Manage', so coverage is not comprehensive. It sits above anchor 2 (which names only a domain) because multiple concrete entities are listed, but below anchor 4 (which lists several distinct specific actions).	3 / 5
Completeness	Both 'what' ('Pulsetic integration. Manage ...') and an explicit 'when' ('Use when the user wants to interact with Pulsetic data') are present, matching anchor 4. It does not reach anchor 5 because the 'when' clause is a single generic trigger rather than concrete multiple trigger phrases.	4 / 5
Trigger Term Quality	Entity terms (Leads, Persons, Organizations, Deals, Projects, Pipelines) appear, but the trigger phrase 'Use when the user wants to interact with Pulsetic data' is generic and lacks natural synonyms or variations a user would actually say. It is not anchor 2 (only generic keywords) because several relevant domain terms are present, but misses the natural phrasing breadth of anchor 4.	3 / 5
Distinctiveness Conflict Risk	Pulsetic is a named product, giving a clear niche and low conflict risk, matching the 'mostly distinct; minor overlap risk' of anchor 4. It does not reach anchor 5 because the trigger phrasing 'interact with Pulsetic data' is broad and the listed entity terms (Leads, Deals, Pipelines) are generic enough to overlap with CRM-style skills.	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/pulsetic/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.