Name: callpage
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

callpage

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

Quality

64%

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/callpage/SKILL.md

Quality

Content

71%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 highly actionable with concrete, executable Membrane CLI commands and a clear connection workflow including polling and error-recovery feedback loops. It is somewhat verbose in its intro and keeps all reference material inline rather than progressively disclosed into separate files.

Suggestions

Trim the marketing-style opening paragraph and the empty Overview bullet list to focus on integration guidance Claude does not already know.

Move the Popular actions and proxy-flag reference tables into a separate references file linked one level deep from SKILL.md to improve progressive disclosure.

Fix the loose step numbering (e.g. an explicit 'Step 2' heading) so the 'skip to Step 2' instruction resolves to a clear anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples and tables, but includes some unnecessary padding such as the marketing-style intro paragraph ('aiming to generate more leads and sales') and the near-empty Overview bullet list.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request proxy) with real flags and JSON output examples.	5 / 5
Workflow Clarity	The connect-then-poll sequence is clear with explicit feedback loops (poll until non-BUILDING, re-poll after client action, error-state handling), but the 'skip to Step 2' reference and '1b' labeling introduce a minor numbering gap.	4 / 5
Progressive Disclosure	Sections are clearly headed and well ordered, but no bundle files exist and all reference material (the Popular actions table and proxy flag reference) is inlined rather than split into one-level-deep referenced files.	3 / 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 clearly names the CallPage domain and includes an explicit 'Use when' trigger, answering both what and when. Its main weakness is generic, non-concrete action language that under-specifies what the skill actually does.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete CallPage actions such as 'initiate callbacks, create and manage widgets, and manage users and call history'.

Broaden trigger terms with natural user phrases and synonyms, e.g. 'Use when the user wants to manage CallPage widgets, callbacks, users, or call history.'

Tighten the 'what' clause to mirror the specific capabilities surfaced in the body's Popular actions table.

Dimension	Reasoning	Score
Specificity	Names the CallPage domain but the listed actions ('Manage data, records, and automate workflows') are generic and not concrete; it lacks specifics like initiate callbacks or create widgets.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with CallPage data'), though the 'what' is somewhat generic.	4 / 5
Trigger Term Quality	'CallPage' and 'CallPage data' are relevant keywords a user would naturally say, but coverage is thin with no synonyms or variations beyond the brand name plus generic data/records/workflows.	3 / 5
Distinctiveness Conflict Risk	The CallPage brand name gives it a clear, distinct niche with minimal conflict risk, but the generic 'manage data, records, automate workflows' phrasing carries minor overlap with other data 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/callpage/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.