Name: keysender
Rating: 55.2 (1 reviews)
Author: membranedev

keysender

Keysender integration. Manage data, records, and automate workflows. Use when the user wants to interact with Keysender data.

Quality

62%

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/keysender/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 content is actionable and well-structured with a clear state-machine workflow for connecting and running actions, but it opens with marketing padding and has a few dangling "Step 2" references that break the step numbering. Trimming the fluff and fixing the step labels would lift conciseness and workflow clarity.

Suggestions

Cut the marketing intro ("stand out from digital noise...", "focus on the integration logic rather than auth plumbing") to purely functional context.

Fix the dangling step references: either label "Step 1"/"Step 2" sections or rewrite "Skip to Step 2" as "Skip to Searching for actions."

Add a brief note validating action results (e.g., checking the `output`/`error` field) before treating a run as successful, since running actions can be batch/destructive.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete command blocks, but the marketing intro ("stand out from digital noise and build stronger relationships") and editorializing ("so you can focus on the integration logic rather than auth plumbing") add unnecessary padding.	3 / 5
Actionability	It provides copy-paste ready commands for login, connection ensure, action list/run, and proxy requests with flags documented in a table, matching the score-4 anchor of mostly executable guidance with minor gaps (e.g., CONNECTION_ID/QUERY placeholders).	4 / 5
Workflow Clarity	The connect→poll→search→run sequence has real validation checkpoints via state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, fitting the score-4 anchor despite minor numbering gaps like dangling "Skip to Step 2" references.	4 / 5
Progressive Disclosure	With no bundle files, all content lives in one well-organized SKILL.md with clear sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices), matching the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

57%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 covers both what and when with a distinct brand trigger, but its action verbs are generic rather than concrete. Tightening "Manage data, records, and automate workflows" into specific capabilities would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Keysender capabilities such as creating campaigns, sending personalized direct mail, and retrieving delivery/audit records.

Expand the trigger clause to include natural user phrases like "when the user mentions Keysender, direct mail campaigns, or sending gifts."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Keysender domain but the actions are generic rather than concrete, matching the score-2 anchor of minimal/generic actions.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Keysender data"), matching the score-4 anchor where both are present though the "when" could be more specific.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Keysender data" offers the brand keyword and "data" but misses common synonyms or task variations, fitting the score-3 anchor of partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The "Keysender" brand name gives a clear niche with minimal conflict risk, though the generic action verbs leave minor overlap with broad data skills, fitting the score-4 anchor.	4 / 5
	Total	13 / 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/keysender/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.