CtrlK
BlogDocsLog inGet started
Tessl Logo

waiverfile

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

55

Quality

62%

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/waiverfile/SKILL.md
SKILL.md
Quality
Evals
Security

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 guide with concrete CLI commands and a clear connection state machine including feedback loops. It would benefit from trimming conversational padding and moving extended detail (e.g. the proxy flag table) into reference files.

Suggestions

Remove conversational filler such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection.' to improve token efficiency.

Consider moving the proxy request flag table and extended clientAction field descriptions into a separate reference file to keep SKILL.md a lean overview.

Add a brief validation step after running actions (e.g. checking the output/error fields) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes some unnecessary conversational padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection.'

3 / 5

Actionability

It provides concrete, executable commands (install, login, connection ensure, action run, request with a full flag table), with only minor placeholder gaps like <agentType> and CONNECTION_ID.

4 / 5

Workflow Clarity

The connection flow is a clearly sequenced state machine (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with explicit polling and a feedback loop after the user completes an action, leaving only minor validation gaps.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices) with no nested references, though no bundle files are used to offload detail.

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 is functional with a clear product name and an explicit 'Use when' clause, satisfying basic completeness and distinctiveness. It is weakened by generic, non-specific action language and limited natural trigger synonyms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete WaiverFile-specific actions such as 'create and send waivers, track signer statuses, and manage waiver templates'.

Expand trigger terms to include natural synonyms users would say, e.g. 'waivers', 'waiver signing', 'digital waivers', or 'waiver templates'.

Tighten the 'when' clause to reference concrete scenarios, e.g. 'Use when the user wants to create or send digital waivers, check signer status, or manage waiver templates.'

DimensionReasoningScore

Specificity

Names the domain (WaiverFile) but the listed actions are generic ('Manage data, records, and automate workflows') rather than concrete waiver-specific operations, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Both a 'what' ('WaiverFile integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with WaiverFile data.') are present, though the 'when' is generic and could be more specific.

4 / 5

Trigger Term Quality

'WaiverFile' and 'interact with WaiverFile data' are relevant keywords, but common natural variations (waivers, waiver signing, digital waivers) are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named product 'WaiverFile' gives it a clear niche with minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap with other data-management skills.

4 / 5

Total

13

/

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.