Name: callfire
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

callfire

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

Quality

66%

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/callfire/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 content is highly actionable with complete executable commands and a well-validated connection workflow including error-recovery loops. It loses points mainly on a trimmable platform-introduction paragraph and the absence of validation guidance for the destructive/batch actions it exposes.

Suggestions

Trim the opening CallFire overview paragraph and chatty asides ('so you can focus on the integration logic', 'This is the fastest way') to assume Claude's familiarity and save tokens.

Add a brief validation/confirmation checkpoint before destructive or batch actions (e.g. 'Before send-texts or delete-contact, confirm the target contact list/IDs and expected recipient count with the user').

Consider moving the 20-row popular-actions table to a references/actions.md file and keeping a short representative subset inline, with a clearly signaled one-level-deep link.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but the opening CallFire platform explainer ('cloud-based platform that provides SMS marketing, voice broadcasting...') and a few chatty sentences ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') are trimmable over-explanation.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, polling, action list/run with --input JSON, proxy requests) plus a concrete popular-actions table with real keys and a proxy flag reference table.	5 / 5
Workflow Clarity	The connection workflow is a clearly sequenced process with explicit validation checkpoints and feedback loops (poll until not BUILDING, re-poll after CLIENT_ACTION_REQUIRED, inspect error on CONFIGURATION_ERROR), but destructive/batch actions like send-texts and delete-contact lack explicit pre-execution validation guidance.	4 / 5
Progressive Disclosure	The body is well-organized with clear headers, tables, and code blocks and contains no nested or broken references (no bundle files exist), though the sizable inline popular-actions table could arguably live in a separate reference file and no one-level-deep references are signaled.	4 / 5
	Total	16 / 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 pairs a what-statement with an explicit Use-when trigger and is anchored by a distinctive brand keyword. Its main weakness is generic, non-concrete action language that undersells CallFire's specific SMS, voice broadcast, and call-tracking capabilities.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete CallFire actions, e.g. 'Send SMS/text broadcasts, run voice broadcast campaigns, track calls, and manage contacts and contact lists.'

Expand the trigger clause with feature-level keywords users actually say, e.g. 'Use when the user wants to send texts or voice broadcasts, track calls, or manage CallFire contacts and numbers.'

Add common synonyms/extensions (e.g. SMS, MMS, IVR, DNC) so the description matches a wider range of natural user requests.

Dimension	Reasoning	Score
Specificity	The description names the CallFire domain but the actions are generic and abstract ('Manage data, records, and automate workflows') rather than concrete operations like sending texts or broadcasting calls.	2 / 5
Completeness	Both a 'what' (CallFire integration managing data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with CallFire data') are present, though the what is vague and the when could be more specific.	4 / 5
Trigger Term Quality	It surfaces the natural brand keyword 'CallFire' that users would say, but offers only generic surrounding terms ('data', 'records', 'workflows') with no synonyms or feature-specific triggers.	3 / 5
Distinctiveness Conflict Risk	The 'CallFire' brand name is a distinct niche trigger with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing introduces minor overlap with other integration 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/callfire/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.