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

justcall

JustCall integration. Manage Persons, Organizations, Leads, Activities, Notes, Files and more. Use when the user wants to interact with JustCall 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/justcall/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 skill is highly actionable with concrete CLI commands and a solid connection workflow, but it is held back by scattered explanatory padding and a complete absence of validation guidance for destructive operations. Structure and progressive disclosure are good for a single-file CLI-wrapper skill.

Suggestions

Trim over-explanation: drop the JustCall marketing intro and phrases like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection".

Add a validation/confirmation checkpoint before destructive or irreversible actions, e.g. verify a contact exists (get-contact) and confirm with the user before running delete-contact, and dry-check recipients before send-sms.

Provide one fully-worked action-run example with realistic parameter values (not just placeholders) so the run-actions section is copy-paste complete.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational with lean command blocks and tables, but it retains several unnecessary explanations (the JustCall intro paragraph, "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") that could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands are given for every stage (install, login, connection ensure/get, action list/run, request) plus a popular-actions table; placeholders like CONNECTION_ID and the lack of a fully-worked action run with real parameters are minor gaps.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with a state-machine and poll/retry feedback loops, but destructive and outward-facing operations (delete-contact, send-sms, proxy DELETE/POST) are presented with no validation or verification step, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body is organized into clear, logically ordered sections with no nested/deep references; the 15-row popular-actions table is a defensible inline quick-reference, leaving only minor organization gaps rather than content that clearly belongs in a separate file.	4 / 5
	Total	14 / 20 Passed

Description

67%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 product-specific and covers both what and when, but its trigger terms and entity list lean generic and do not surface the phone-system actions (calls, SMS, contacts) users would naturally mention. It sits comfortably above the midpoint but short of a strong, trigger-rich description.

Suggestions

Replace the generic "Persons, Organizations, Leads, Activities, Notes, Files" list with JustCall-specific capabilities users actually request, e.g. "make and manage calls, send SMS, look up contacts and phone numbers".

Strengthen the trigger clause with concrete phrases: "Use when the user wants to make or log calls, send SMS, or manage JustCall contacts and phone numbers."

Add the natural synonyms/file-context terms users say (calls, texts/SMS, contacts, phone numbers) so the description triggers on real user language.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Leads, Activities, Notes, Files and more" enumerates several concrete managed entities, but the single generic verb "Manage" and the trailing "and more" leave minor coverage gaps rather than reaching comprehensive multi-action coverage.	4 / 5
Completeness	Both "what" (JustCall integration managing listed entities) and "when" (an explicit "Use when..." clause) are present; the "when" is explicit but generic rather than listing concrete trigger phrases, so it does not reach a 5.	4 / 5
Trigger Term Quality	The description names the JustCall brand and includes a "Use when the user wants to interact with JustCall data" trigger, but it omits the natural phone-system terms users would actually say (calls, SMS, contacts, phone numbers) in favor of generic CRM entity names.	3 / 5
Distinctiveness Conflict Risk	The named product "JustCall" gives the skill a clear, distinct niche with low conflict risk, but the generic "Persons, Organizations, Leads" enumeration creates minor overlap with general CRM/contact skills rather than a fully distinctive 5.	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/justcall/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.