Name: paperform
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

paperform

PaperForm integration. Manage Forms. Use when the user wants to interact with PaperForm data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/paperform/SKILL.md

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 delivers strong, executable Membrane CLI guidance with a well-validated connection workflow. Trimming the marketing intro and either populating 'Popular actions' or moving detailed reference material into bundle files would push it higher.

Suggestions

Cut the marketing-style opening paragraph ('Paperform is a versatile online form builder…') and the 'so you can focus on the integration logic rather than auth plumbing' editorial; lead directly with what the skill does.

Populate the 'Popular actions' section with a few concrete example actions (e.g. list forms, get submissions) instead of just restating the discovery command.

Fix the 'Step 2' references by either adding an explicit Step 2 header or rewording to 'skip to Searching for actions' so the workflow numbering is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete command blocks, but the opening marketing paragraph ('versatile online form builder that allows users to create visually appealing forms…') and editorial filler ('so you can focus on the integration logic rather than auth plumbing') explain things Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests with a clear flags table; the 'Popular actions' section is hollow, listing only a discovery command instead of actual popular actions.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state polling and a feedback loop (re-poll after the user completes the action), but 'Step 2' is referenced without a corresponding Step 2 header, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	No bundle files are present, so all content lives in one well-sectioned SKILL.md with no nested references and a single official-docs link; organization is good, though detailed proxy flags and connection-state tables could justify a separate reference file.	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 compact and includes an explicit 'Use when' trigger, but it is thin on concrete capabilities and natural trigger terms. Expanding it with specific actions and common user phrases would lift the weaker dimensions.

Suggestions

Replace the generic 'Manage Forms' with concrete actions, e.g. 'Create and update forms, list and filter submissions, manage folders.'

Broaden trigger terms to natural phrases users say, e.g. 'Use when the user wants to create forms, review submissions, or manage PaperForm surveys.'

Keep the explicit 'Use when' clause but make it enumerate concrete situations (forms, submissions, folders) rather than the vague 'interact with PaperForm data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('PaperForm integration') but the only action offered is the generic 'Manage Forms', which is minimal and lacks concrete operations like create form, view submissions, or manage folders.	2 / 5
Completeness	It answers both 'what' ('PaperForm integration. Manage Forms.') and 'when' ('Use when the user wants to interact with PaperForm data.'), but the trigger clause stays generic rather than enumerating concrete situations.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ('PaperForm', 'Forms', 'interact with PaperForm data') but misses common natural variations a user might say such as 'submissions', 'surveys', or 'form builder'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific PaperForm app gives it a clear niche with low conflict risk, though the generic 'Forms'/'data' triggers leave minor overlap potential with other form-builder skills.	4 / 5
	Total	13 / 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/paperform/SKILL.md
Commit: f484c82

Reviewed: 5 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.