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

callingly

Callingly integration. Manage data, records, and automate workflows. Use when the user wants to interact with Callingly 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/callingly/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 content is a well-structured, highly actionable CLI integration guide with a strong connection workflow including feedback loops. Its main weaknesses are scattered marketing/padding prose and the absence of validation guidance for the destructive actions it exposes.

Suggestions

Trim marketing prose such as the sales-team/conversion-rate sentence and the 'auth plumbing' and 'burn less tokens' asides to improve token efficiency.

Add a validation or confirmation checkpoint before destructive actions like delete-lead and delete-webhook (e.g. verify the target ID via get-lead first).

Fix the dangling 'skip to Step 2' reference by labeling the subsequent section as Step 2 or rewording the pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but includes unnecessary padding such as the marketing line about sales teams improving conversion rates and phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'burn less tokens'.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection, action search/run, and proxy, plus a lookup table of action keys; placeholders like <agentType> and CONNECTION_ID require substitution, keeping it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state checkpoints and a feedback loop (poll until READY, re-poll after client action), but the 'skip to Step 2' reference is dangling and destructive actions (delete-lead, delete-webhook) lack validation steps.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections with no nested references, and the CLI itself serves as the detailed reference; the 20-row actions table is a reasonable inline discovery aid rather than a full API reference.	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 correctly names the platform and includes an explicit 'Use when' trigger, satisfying the basic completeness bar. However, both the capability list and the trigger phrasing are generic and lack the concrete, natural terms (calls, leads, SMS) that would make it distinctive and specific.

Suggestions

Replace generic actions with concrete Callingly capabilities, e.g. 'Make outbound calls, manage leads and teams, and send SMS to leads'.

Expand the trigger to natural user phrases, e.g. 'Use when the user wants to manage Callingly leads, make outbound calls, or send SMS to leads'.

Avoid the circular 'interact with Callingly data' phrasing in favor of specific triggering scenarios.

Dimension	Reasoning	Score
Specificity	Names the Callingly domain but the listed actions — 'Manage data, records, and automate workflows' — are generic rather than concrete platform-specific actions (e.g. make outbound calls, manage leads, send SMS).	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Callingly data') are present, though the 'when' is generic and somewhat circular.	4 / 5
Trigger Term Quality	The keyword 'Callingly' is relevant and a 'Use when' trigger is present, but it misses the natural phrases users would actually say such as 'leads', 'calls', 'outbound calling', or 'SMS'.	3 / 5
Distinctiveness Conflict Risk	The named app 'Callingly' gives it a clear niche with minimal conflict risk, though generic actions and trigger phrasing leave minor overlap risk with other sales/CRM 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/callingly/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.