Name: commonpaper
Rating: 59.2 (1 reviews)
Author: membranedev

commonpaper

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

Quality

68%

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/commonpaper/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 is actionable with strong executable CLI examples and a clear connection-state workflow. It loses points for a padded introductory paragraph, an undefined "Step 2" reference, and the absence of validation guidance before running mutating actions.

Suggestions

Trim the introductory marketing paragraph and the bare-noun overview bullets; assume Claude knows what a contract platform is and only state what is non-obvious about the Common Paper/Membrane integration.

Define or relabel the missing "Step 2" (e.g., rename to "Searching for and running actions") so the "skip to Step 2" checkpoint has a clear target.

Add a validation/check step before mutating actions (e.g., dry-run or confirm destructive/batch operations) to satisfy the workflow-clarity feedback-loop guidance for batch operations.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ("Common Paper is a standardized contract platform that streamlines legal processes...Think of it as a library of pre-approved legal templates") and the bare-noun overview bullets explain context Claude already knows and could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands (login, connection ensure, action list/run, request) with a full proxy-options flag table cover the common cases; minor runtime placeholders like CONNECTION_ID and QUERY are legitimate substitutions.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/error) and polling checkpoints, but "Step 2" is referenced without being defined and there is no validation step before running actions.	4 / 5
Progressive Disclosure	Single ~140-line file with clear section headers and no bundle files; well-organized, though the proxy options table and action-schema details are inlined rather than split into references.	4 / 5
	Total	15 / 20 Passed

Description

70%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 third-person, concise, and clearly answers both what and when with a brand-specific trigger. It would benefit from more contract-specific action language and natural synonyms to sharpen specificity and trigger coverage.

Suggestions

Replace generic verbs with Common Paper-specific actions, e.g. "Create, negotiate, and manage contracts from Common Paper templates."

Add natural trigger synonyms like "contracts", "legal templates", or "agreements" so users who mention those terms surface this skill.

Make the when clause more specific, e.g. "Use when the user wants to create or manage Common Paper contracts, counterparties, or workspaces."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Common Paper domain plus a couple of concrete actions, but the actions are generic and not comprehensive (no mention of contracts, templates, or counterparties).	3 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Common Paper data") are present; the when clause could be more specific about contract-related triggers.	4 / 5
Trigger Term Quality	"Common Paper" and "Common Paper data" plus "data", "records", "workflows" give good keyword coverage, though synonyms and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The "Common Paper" brand name carves a clear niche with distinct triggers, but the generic "manage data, records" phrasing leaves minor overlap risk with other data-management skills.	4 / 5
	Total	15 / 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/commonpaper/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.