Name: pageclip
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

pageclip

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

Quality

61%

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/pageclip/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 delivers executable Membrane CLI commands with a sensible connection workflow and good structure, but it is padded with removable prose and lacks validation checkpoints around action execution and proxy requests. Trimming the boilerplate and adding verification guidance for destructive operations would lift the score.

Suggestions

Remove the Pageclip intro paragraph and 'auth plumbing' explanation; assume Claude knows the domain and focus on commands.

Add a validation/verification checkpoint before running actions or issuing proxy mutations (e.g., inspect outputSchema first, confirm destructive HTTP methods with the user).

Label the post-connection section as 'Step 2' (or drop the 'skip to Step 2' reference) and deduplicate the 'Popular actions' section against the action-search command.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven but includes removable prose such as the Pageclip intro paragraph, the 'auth plumbing' explanation, a redundant 'Popular actions' section that repeats the search command, and the vague Overview filler ('Use action names and parameters as needed').	3 / 5
Actionability	Concrete, copy-pasteable commands are provided throughout (install, login, connection ensure, action list/run, request with a flags table), but placeholders like <agentType> and CONNECTION_ID plus the lack of worked action examples leave minor gaps.	4 / 5
Workflow Clarity	The connection flow has a clear state-checking feedback loop (READY / CLIENT_ACTION_REQUIRED with re-polling), but the action-run and proxy steps lack validation/verification for potentially destructive operations (DELETE is listed with no caution) and the referenced 'Step 2' is not labeled, so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	The skill is a self-contained, well-sectioned overview with no bundle files and no nested references, but minor redundancy (the 'Popular actions' section repeats the search command) and the thin Overview list keep it just below a fully clean 5.	4 / 5
	Total	14 / 20 Passed

Description

61%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 answers both what and when and is anchored by a distinctive brand trigger, but its capability language is generic and the trigger phrasing is narrow. Tightening the verbs to concrete Pageclip operations and broadening the trigger terms would raise it.

Suggestions

Replace generic verbs with concrete Pageclip operations, e.g. 'Collect form submissions, query site records, and automate Pageclip workflows.'

Broaden the trigger clause to include natural user phrases such as 'contact forms', 'survey responses', or 'form data from static sites'.

Mention the underlying mechanics briefly (e.g. 'via the Membrane CLI') only if it aids activation, otherwise keep focus on user-facing tasks.

Dimension	Reasoning	Score
Specificity	Phrases like 'Manage data, records, and automate workflows' name the Pageclip domain but the actions are generic ('manage data', 'manage records') rather than concrete operations such as collecting form submissions or viewing site records.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Pageclip data') are present, but the 'when' trigger is generic and the 'what' could be more specific, so it sits above the missing-trigger cap of 3 but below a fully explicit 5.	4 / 5
Trigger Term Quality	The description includes the distinctive keyword 'Pageclip' plus 'data' and 'records', comparable to 'Works with PDF files', but lacks common variations, synonyms, or concrete trigger phrases a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	The Pageclip brand name is a distinctive niche trigger ('Pageclip integration', 'interact with Pageclip data') making it unlikely to activate for unrelated skills.	5 / 5
	Total	14 / 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/pageclip/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.