Name: salesblink
Rating: 63.2 (1 reviews)
Author: membranedev

salesblink

SalesBlink integration. Manage Organizations, Pipelines, Projects, Users, Filters. Use when the user wants to interact with SalesBlink data.

Quality

75%

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

Quality

Content

72%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 skill body is highly actionable with concrete commands and a well-instrumented connection workflow, but it keeps everything inline in one file and omits validation for potentially destructive action/proxy operations. Tightening the intro and adding verification guidance would raise the weakest dimensions.

Suggestions

Add a verification/confirmation step before running or proxying destructive operations (e.g., inspect outputSchema, confirm before DELETE/batch outreach, check the response status field).

Move the proxy flag table and detailed clientAction state handling into a references file (e.g., CONNECTION_STATES.md, PROXY_REFERENCE.md) and link to them from the body to improve progressive disclosure.

Trim the SalesBlink marketing intro and de-duplicate the action-list command shown in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and reference material, but the introductory paragraph explaining what SalesBlink is and the near-duplicate action-list commands in 'Searching for actions' vs 'Popular actions' could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for the full lifecycle (install, login, connection ensure/get, action list, action run with JSON input, proxy with flag table), covering the common cases with only necessary placeholders.	5 / 5
Workflow Clarity	The connection sequence has strong feedback loops (poll --wait, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state handling, re-poll after action), but action execution and proxy requests — which can perform destructive or batch sales operations — lack any validation or verification step, triggering the destructive/batch cap.	3 / 5
Progressive Disclosure	The content is a single ~140-line file with no bundle references, inlining material (proxy options table, connection state machine) that could live in a separate reference; sections are well-organized but nothing is split out and the under-50-line exception does not apply.	3 / 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 cleanly answers both what the skill does and when to use it, anchored to a clearly distinct named application. It is slightly generic in its single-verb action framing and single trigger phrase, keeping it just below the top anchor.

Suggestions

Vary the verbs to reflect distinct concrete actions (e.g., 'Create and manage Organizations, Pipelines, Projects, Users, and Filters') for fuller specificity.

Expand the trigger phrase with concrete user intents, e.g. 'Use when the user wants to manage SalesBlink organizations, pipelines, projects, users, or filters.'

Dimension	Reasoning	Score
Specificity	Names the SalesBlink domain plus five concrete entities (Organizations, Pipelines, Projects, Users, Filters), but applies a single verb ('Manage') across them rather than listing multiple distinct actions, leaving a minor coverage gap.	4 / 5
Completeness	Both 'what' (Manage Organizations, Pipelines, Projects, Users, Filters) and 'when' (Use when the user wants to interact with SalesBlink data) are stated explicitly, but the trigger is a single generic phrase rather than the concrete multi-trigger phrasing of the top anchor.	4 / 5
Trigger Term Quality	The app name 'SalesBlink' and entity names provide good keyword coverage with the natural trigger 'Use when the user wants to interact with SalesBlink data', though common task-specific phrasings ('create a sequence', 'add a prospect') are missing.	4 / 5
Distinctiveness Conflict Risk	'SalesBlink integration' names a specific third-party app, giving it a clear niche with distinct triggers and minimal risk of overlapping with unrelated skills.	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/salesblink/SKILL.md
Commit: f484c82

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