CtrlK
BlogDocsLog inGet started
Tessl Logo

craftmypdf

CraftMyPDF integration. Manage PDFDocuments, Users, Workspaces. Use when the user wants to interact with CraftMyPDF data.

59

Quality

68%

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

Quality

Content

75%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 comprehensive, copy-paste-ready Membrane CLI commands and a well-sequenced connection state machine with feedback loops. Its main weaknesses are a marketing-flavored intro that pads the token budget and a dangling 'Step 2' reference with no destructive-action validation guidance.

Suggestions

Trim the introductory marketing paragraph ('CraftMyPDF is a document automation platform that helps users generate PDFs ... used by businesses of all sizes') to a single purpose line, since Claude does not need the platform pitch.

Fix the dangling 'Step 2' reference by either labeling the workflow steps explicitly (Step 1: Connect, Step 2: Run actions) or removing the cross-reference.

Add a short validation checkpoint before destructive/batch actions (e.g. 'Before running delete-template, confirm the template ID with the user') to lift workflow clarity.

DimensionReasoningScore

Conciseness

Most of the body is efficient CLI guidance, but the opening marketing paragraph ('document automation platform that helps users generate PDFs ... used by businesses of all sizes') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need, matching the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

The body provides copy-paste-ready executable commands throughout (npm install, membrane login, connection ensure/get, action list/run, request) with concrete flags and a tables of action keys and proxy options, fully covering the common cases per the 5-anchor.

5 / 5

Workflow Clarity

The connect → poll-until-ready → handle clientAction states → search → run → proxy sequence is clear with a genuine feedback loop (poll state, act, re-poll), but the dangling 'skip to Step 2' reference (no Step 2 is defined) and the absence of validation guidance around destructive actions like delete-template leave minor gaps, fitting 4 over 5.

4 / 5

Progressive Disclosure

The skill is a single file with no bundle references, but it is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with content appropriately placed for a CLI integration guide, matching 'good structure; most content appropriately placed; minor organization gaps' rather than the over-50-line monolith penalty of 3.

4 / 5

Total

16

/

20

Passed

Description

62%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 concise, third-person, and includes an explicit 'Use when' trigger covering both what and when. It is held back by a single generic verb ('Manage') and somewhat generic trigger phrasing rather than comprehensive natural-language coverage.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, list, update, and delete PDFDocuments, manage Users and Workspaces'.

Broaden the trigger with natural phrasing and synonyms, e.g. 'Use when the user wants to generate PDFs, manage CraftMyPDF templates, or work with PDFDocuments, Users, or Workspaces'.

DimensionReasoningScore

Specificity

Names the domain (CraftMyPDF) and three concrete entities (PDFDocuments, Users, Workspaces), but 'Manage' is a single generic verb rather than multiple specific actions, so it lands at 'names domain and 1-2 concrete actions, not comprehensive' rather than the 4-anchor's 'several specific actions'.

3 / 5

Completeness

It states both what ('Manage PDFDocuments, Users, Workspaces') and when ('Use when the user wants to interact with CraftMyPDF data'), but the 'when' is generic and could be more specific, fitting the 4-anchor rather than the fully explicit 5-anchor.

4 / 5

Trigger Term Quality

It includes relevant keywords (CraftMyPDF, PDFDocuments, Users, Workspaces) and an explicit trigger, but misses common natural variations/synonyms a user might say, matching the 'some relevant keywords but missing common variations' anchor rather than the broader coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The CraftMyPDF brand name gives it a clear, distinct niche with minimal conflict risk, but the generic 'Manage ... PDFDocuments' has minor overlap with general PDF skills, placing it at 4 rather than the clearly-distinct 5.

4 / 5

Total

14

/

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.