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

Blog Docs Log in Get started

callrail

CallRail integration. Manage Companies. Use when the user wants to interact with CallRail 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/callrail/SKILL.md

Quality

Content

75%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 a well-structured, actionable guide to driving CallRail through the Membrane CLI, with concrete commands and a clear connection workflow including error-recovery checkpoints. It is held back from the top band by a padded marketing intro, placeholder-dependent examples, and the absence of any split-out reference files for the sizable actions table.

Suggestions

Trim the marketing intro paragraph ("optimize their campaigns and improve ROI") to a one-line factual description of CallRail.

Add a concrete worked example that substitutes real-looking values for CONNECTION_ID and actionId so the run/proxy commands are copy-paste ready.

Move the 20-row Popular actions table into a references/actions.md file and link to it from the body to improve progressive disclosure and reduce inline token weight.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven content that assumes Claude's competence, with only minor over-explanation (the marketing-flavored intro paragraph about optimizing campaigns/ROI); fits the efficient-with-minor-trimming anchor and is below 5 due to that padded intro.	4 / 5
Actionability	Provides concrete, executable commands (install, login, connection ensure, action run, request) plus a popular-actions table and proxy flag reference, matching mostly-executable guidance with minor gaps; below 5 because several examples require substituting placeholders (CONNECTION_ID, QUERY, actionId).	4 / 5
Workflow Clarity	A clear install→login→connect→search→run sequence exists with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-and-recover feedback loop for the connection step, matching the clear-sequence-with-most-checkpoints anchor; below 5 because the search→run path lacks its own validation checkpoint.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers with no nested or buried references and a one-level external docs link; fits the good-structure anchor, though the 20-row popular-actions table could arguably live in a reference file, keeping it below 5.	4 / 5
	Total	16 / 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 is third-person, includes both a what and a use-when clause, and targets a clearly distinct product niche. Its main weakness is thin action coverage (only "Manage Companies") and limited trigger-term variety, leaving it solid but not exemplary.

Suggestions

Expand the what with 2-3 more concrete actions the skill supports (e.g., list calls, send text messages, manage tracking numbers) to lift specificity and completeness.

Add natural trigger variations users might say (e.g., "call tracking", "lead attribution", "form submissions") to broaden trigger-term coverage.

Make the use-when clause more specific about the data users typically want (calls, companies, trackers) rather than the generic "interact with CallRail data".

Dimension	Reasoning	Score
Specificity	Names the domain ("CallRail") and one concrete action ("Manage Companies"), matching the anchor for 1-2 concrete actions without comprehensive coverage; it is above score 2 because a specific entity/action is named, but below 4 which requires several specific actions.	3 / 5
Completeness	Explicitly states both what ("CallRail integration. Manage Companies.") and when ("Use when the user wants to interact with CallRail data."), matching the anchor where both are present but the when could be more specific; below 5 because the what is not comprehensive (only Companies, though the skill does more).	4 / 5
Trigger Term Quality	Relevant keywords ("CallRail", "Companies", "CallRail data") appear, but coverage is thin with no synonyms or variations beyond the product name, fitting the anchor for some relevant keywords missing common variations; below 4 which expects broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	"CallRail integration" is a clear named-product niche with a distinct trigger ("interact with CallRail data") and minor overlap risk, matching the mostly-distinct anchor; below 5 because "Manage Companies" could overlap with generic CRM-style skills.	4 / 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/callrail/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.