Name: phoneburner
Rating: 62.4 (1 reviews)
Author: membranedev

phoneburner

PhoneBurner integration. Manage Persons, Users, Groups, Emails, Dispositions, Tags. Use when the user wants to interact with PhoneBurner data.

Quality

73%

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

Quality

Content

76%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 executable CLI commands and a well-structured connection state machine, but workflow clarity is held back by a broken "Step 2" reference and the absence of validation/verification steps around running actions that can modify PhoneBurner data.

Suggestions

Fix the dangling cross-reference: replace "skip to Step 2" with a concrete anchor (e.g. "skip to Searching for actions") or label the workflow steps consistently.

Add a verification checkpoint after running mutating actions, e.g. re-list or get the affected record to confirm the change before reporting success.

Trim the introductory marketing paragraph to a one-line description of what PhoneBurner is, since Claude already knows the domain.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples, but the opening marketing prose ("helps sales teams and call centers increase efficiency... used by sales professionals, real estate agents, and insurance agents") is background Claude does not need and could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end — install, login, connection ensure/get with --wait, action list/run with --input, and proxy requests with a full flag table — all executable as written.	5 / 5
Workflow Clarity	The connection sequence has good state-based checkpoints (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but the "skip to Step 2" cross-reference is dangling (no Step 2 is labeled) and the Running actions section shows no verification/validation before modifying PhoneBurner records, a validation gap that caps this dimension.	3 / 5
Progressive Disclosure	The single file is well-organized with clear section headers (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and needs no external references; minor gaps like the incomplete step numbering keep it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

71%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 identifies the PhoneBurner niche and pairs a concrete capability list with an explicit use-when clause, scoring well on distinctiveness and completeness. Its main weakness is trigger-term breadth, relying on the product name alone without natural synonyms a user might say.

Suggestions

Expand the trigger clause with natural synonyms, e.g. "Use when the user wants to interact with PhoneBurner data — contacts, dialing sessions, dispositions, or call records."

Replace the generic "Manage" with a couple of concrete verbs (create, update, list, tag) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Users, Groups, Emails, Dispositions, Tags" enumerates several concrete data objects the skill acts on, though the single generic verb "Manage" keeps it just below comprehensive distinct-action coverage.	4 / 5
Completeness	It states both a clear "what" (PhoneBurner integration managing those entities) and an explicit "when" ("Use when the user wants to interact with PhoneBurner data"), but the trigger clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural trigger keyword is the product name in "Use when the user wants to interact with PhoneBurner data"; common synonyms like dialer, calls, contacts, or power dialer are missing.	3 / 5
Distinctiveness Conflict Risk	The proper-noun product name "PhoneBurner" gives the skill a clear, distinct niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/phoneburner/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.