CtrlK
BlogDocsLog inGet started
Tessl Logo

signpath

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

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/signpath/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, executable Membrane CLI commands and a clear install-to-run workflow including connection-state polling. It is somewhat verbose in places and monolithic, with reference material inlined that could be split into separate bundle files.

Suggestions

Trim contextual filler Claude already knows (e.g., the DocuSign/Adobe Sign comparison and the 'rather than auth plumbing' rationale).

Add a validation/verification checkpoint before running actions (e.g., confirm the resolved actionId and review its inputSchema before 'membrane action run'), since action runs can be destructive or batch.

Move the flags reference table and per-state clientAction detail into a separate reference file (e.g., references/proxy-reference.md) and link to it from the body to reduce inline bulk.

DimensionReasoningScore

Conciseness

Mostly efficient with tight CLI commands and a flags table, but padded lines like 'Think of it as a competitor to DocuSign or Adobe Sign' and 'so you can focus on the integration logic rather than auth plumbing' explain context Claude does not need.

3 / 5

Actionability

Concrete, copy-paste-ready commands throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://..." --json', 'membrane action run <actionId> --input ...') with a flags table, though actionIds remain placeholders.

4 / 5

Workflow Clarity

Clear sequence (install → login → connection ensure → poll state → search → run/proxy) with a polling feedback loop for connection state, but action execution itself lacks validation checkpoints for risky or batch operations.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized section headers, but ~157 lines including an API/flags reference table that could be split into separate files, and no bundle files exist to offload the reference material.

3 / 5

Total

14

/

20

Passed

Description

75%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 clearly names the domain and enumerates many concrete entity types, and includes an explicit 'Use when' trigger clause, making it solid and distinct. Its main weakness is the generic verb ('Manage') and vague trigger phrasing ('interact with SignPath data') rather than concrete user-facing trigger terms.

Suggestions

Replace the generic 'Manage' with specific verbs a user would say (e.g., 'Create, update, and search Leads, Persons, Organizations, Deals, Projects, and Pipelines').

Strengthen the 'Use when' clause with concrete trigger phrases such as 'Use when the user wants to create a signature request, send a document for signing, or query SignPath deals and pipelines.'

Drop the vague 'and more' so the scope reads as bounded rather than open-ended.

DimensionReasoningScore

Specificity

Quotes 'Manage Leads, Persons, Organizations, Deals, Projects, Pipelines and more' — many concrete entity types, but a single generic verb ('Manage') applied across them rather than multiple distinct actions, placing it just below comprehensive.

4 / 5

Completeness

Quotes both a clear 'what' ('Manage Leads, Persons...') and an explicit 'when' ('Use when the user wants to interact with SignPath data'), but the 'when' clause is generic rather than enumerating concrete trigger phrases, fitting the anchor where 'when' could be more explicit.

4 / 5

Trigger Term Quality

Strong domain keyword coverage ('SignPath', 'Leads, Persons, Organizations, Deals, Projects, Pipelines'), but the natural user trigger phrase is thin ('interact with SignPath data') and lacks common synonyms, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

'SignPath' plus a specific entity list carves a clear niche with minimal overlap risk, but the trailing 'and more' and generic 'interact with' phrasing introduce minor broadness that keeps it just below a 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.