CtrlK
BlogDocsLog inGet started
Tessl Logo

pdffiller

PdfFiller integration. Manage Accounts. Use when the user wants to interact with PdfFiller data.

61

Quality

72%

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

Quality

Content

82%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 a lean, highly actionable integration guide built around concrete Membrane CLI commands, with a well-validated connection workflow and clear section organization. Minor redundancy and a slightly padded intro are the only weaknesses.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, with only minor over-explanation such as the introductory paragraph describing what PdfFiller is and the redundant 'Popular actions' section repeating the action-list command — efficient with minor trim opportunities rather than padded.

4 / 5

Actionability

It provides copy-paste-ready, executable commands with real flags throughout — install, login, connection ensure/get --wait, action list/run with --input JSON, and the proxy request flags table — covering the common cases end to end.

5 / 5

Workflow Clarity

The connection sub-flow is a clear sequence with explicit validation (state checks) and a feedback loop (poll → handle CLIENT_ACTION_REQUIRED → poll again), but the macro connect→discover→run flow is sectioned rather than numbered and the 'Skip to Step 2' forward reference is unlabeled, leaving minor gaps.

4 / 5

Progressive Disclosure

No bundle files exist and the content is a single well-organized SKILL.md with clear section headers; structure is good with minor organization gaps (the entity list and proxy flags are reasonable inline, the redundant Popular actions section could be consolidated).

4 / 5

Total

17

/

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 has an explicit Use-when trigger and names a distinct product, but its what is thin and misses PdfFiller's core PDF-editing capabilities, leaving it generic in places. Trigger coverage is adequate but lacks the natural synonyms users would actually say.

Suggestions

Replace the vague 'Manage Accounts' with concrete core actions, e.g. 'Fill, edit, and manage PDF documents and forms in PdfFiller'.

Expand the Use-when clause with natural trigger terms users say, e.g. 'Use when the user wants to fill, edit, or manage PDFs/PDF forms in PdfFiller'.

Add common synonyms and file extensions (.pdf, PDF forms) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("PdfFiller integration") plus one concrete-ish action ("Manage Accounts"), but the core PDF-editing capabilities are absent, so coverage is not comprehensive — matching the anchor for 1-2 concrete actions rather than the minimal/generic 2.

3 / 5

Completeness

It answers both: a (thin) what ("PdfFiller integration. Manage Accounts.") and an explicit when ("Use when the user wants to interact with PdfFiller data"); the when is explicit so it clears the 3-cap, but the what is vague so it does not reach 5.

4 / 5

Trigger Term Quality

"PdfFiller" and the trigger phrase "interact with PdfFiller data" give some relevant keywords, but common natural variations users would say (fill PDF, PDF forms, edit PDF, .pdf) are missing, fitting the 3 anchor.

3 / 5

Distinctiveness Conflict Risk

Naming a specific third-party product (PdfFiller) gives a clear, distinct niche with low conflict risk, but the generic "Manage Accounts" phrasing introduces minor overlap with general account-management skills, keeping it just below 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.