Name: spotdraft
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

spotdraft

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

Quality

66%

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

Quality

Content

76%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 highly actionable and concisely written with strong command examples and a clear connection-readiness workflow. Its main weakness is the absence of validation/verification guidance for action runs, which caps workflow clarity, and a thin 'Popular actions' section that promises more than it delivers.

Suggestions

Add a validation/verification step for action runs, e.g. check the response for errors before reporting success and re-query to confirm destructive changes took effect.

Flesh out the 'Popular actions' section with a few concrete example actions (e.g. list/create/approve contracts) instead of only restating the discovery command.

Resolve or define the dangling 'Step 2' reference so the connection workflow navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven guidance, with only minor trimmable bits such as the Spotdraft overview sentence and the filler line 'Use action names and parameters as needed.'	4 / 5
Actionability	It provides copy-paste-ready, executable membrane CLI commands for install, auth, connection setup, action search/run, and proxy requests, covering the common cases with a concrete flag table.	5 / 5
Workflow Clarity	The connection-setup flow is well sequenced with state checks and a poll-after-action feedback loop, but running actions (which can be destructive/batch) lacks any validation or verification step, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	The body is well organized into clear headed sections with no nested references, but everything is inlined with no external reference files for the detailed clientAction and proxy material, leaving minor organization gaps.	4 / 5
	Total	16 / 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 is functional with an explicit trigger and a distinct named-app niche, but its capability wording is generic and lacks concrete Spotdraft-specific actions and natural trigger synonyms. Tightening the action list and adding contract/approval/template triggers would raise it.

Suggestions

Replace generic verbs with concrete Spotdraft actions, e.g. 'Create and approve contracts, manage templates and counterparties, and automate contract workflows.'

Add natural trigger synonyms users would say, such as 'contracts', 'approvals', 'templates', or 'counterparty', not just 'Spotdraft data'.

Keep the explicit 'Use when' clause but make the 'when' more specific, e.g. 'Use when the user wants to manage Spotdraft contracts, templates, or approvals.'

Dimension	Reasoning	Score
Specificity	The description names the Spotdraft domain but its actions ('Manage data, records, and automate workflows') are generic and minimal rather than concrete, matching the anchor for actions that are minimal or generic.	2 / 5
Completeness	It states both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Spotdraft data'), though the 'what' is generic which keeps it from a 5.	4 / 5
Trigger Term Quality	It includes the relevant keyword 'Spotdraft' and an explicit 'Use when' trigger, but misses common natural variations such as contracts, approvals, templates, or counterparty.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named Spotdraft platform gives it a clear niche with low conflict risk, but the generic 'interact with Spotdraft data' trigger leaves minor overlap risk versus other data-integration skills.	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/spotdraft/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.