Name: draftable
Rating: 48 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

draftable

Draftable integration. Manage Documents. Use when the user wants to interact with Draftable data.

Quality

51%

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

Quality

Content

61%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 concrete, command-driven integration guide with good connection-state handling and useful reference tables. Its main weaknesses are some padding, a thin Overview section, and the absence of validation guidance around destructive/batch actions.

Suggestions

Add a validation/verification checkpoint before destructive actions (e.g. confirm a comparison id via get-comparison before running delete-comparison) to lift workflow clarity above the destructive-operation cap.

Trim the intro paragraph about who uses Draftable and the near-empty Draftable Overview section to improve token efficiency.

Provide one fully concrete end-to-end worked example (real actionId and a sample --input payload) so the action-run guidance is unambiguously copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The command reference, connection-state handling, and tables are efficient, but the intro paragraph about legal/financial professionals and the near-empty "Draftable Overview" section are unnecessary padding that could be trimmed, matching the mostly-efficient-with-some-over-explanation anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy requests plus a concrete flags table, but the action-run examples rely on placeholders like <actionId> and '{"key": "value"}' rather than a fully concrete worked example, a minor gap.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with state polling and a CLIENT_ACTION_REQUIRED feedback loop, but destructive/batch operations listed in the Popular actions table (delete-comparison, list-comparisons at 300/page) lack validation steps, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	With no bundle files present, the ~130-line body is well organized into clearly headed sections covering each phase, but everything is inlined with no one-level-deep references and the sparse Overview section is a minor organization gap, landing it just below a 5.	4 / 5
	Total	14 / 20 Passed

Description

41%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 names a distinctive target app and includes a Use-when clause, but the stated capability ("Manage Documents") is generic and it omits the central concept of document comparison. Adding concrete verbs like "compare" and richer trigger phrases would materially improve it.

Suggestions

Replace the vague "Manage Documents" with concrete capabilities, e.g. "Compare documents and highlight differences between versions; create, list, and delete comparisons; export comparisons to PDF."

Add natural trigger phrases users actually say, e.g. "Use when the user wants to compare two documents, diff contract versions, or export a Draftable comparison."

Mention file types/extensions where relevant (e.g. PDF export) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description only offers the generic action "Manage Documents" after naming the Draftable domain, which is minimal/generic like the anchor "Processes PDF files" rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	Both a "what" ("Draftable integration. Manage Documents.") and a "when" ("Use when the user wants to interact with Draftable data.") are present, but the what is vague and the when lacks concrete trigger phrases, so it does not reach the explicit/specific bar of a 4.	3 / 5
Trigger Term Quality	It surfaces the brand keyword "Draftable" and the generic term "Documents" but omits the core natural phrases a user would say ("compare documents", "comparison", "diff"), and the trigger phrasing "interact with Draftable data" is unnatural, matching the one-or-two-generic-keywords anchor.	2 / 5
Distinctiveness Conflict Risk	Naming the specific app "Draftable" gives it a clear, mostly-distinct niche with only minor overlap risk from the generic "Manage Documents" phrasing, though the lack of concrete action triggers keeps it just short of a 5.	4 / 5
	Total	11 / 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/draftable/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.