Name: dialmycalls
Rating: 63.2 (1 reviews)
Author: membranedev

dialmycalls

DialMyCalls integration. Manage Accounts, Contacts, Recordings, Shortcodes, Keywords, Broadcasts. Use when the user wants to interact with DialMyCalls data.

Quality

75%

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/dialmycalls/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.

A highly actionable, well-structured CLI integration guide with copy-paste commands and a genuine connection-state feedback loop. Its main weaknesses are the lack of verification steps around destructive/batch data operations and a large inline action table that could be split into a reference file.

Suggestions

Add explicit validation/verification after destructive or batch operations, e.g. re-fetch a contact after `delete-contact` or confirm a broadcast's status after `create-call-broadcast` before declaring success.

Label the workflow steps explicitly ("Step 1", "Step 2: Search and run actions") so the "skip to Step 2" references resolve to real headings.

Move the 20-row Popular actions table into a references/ file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with little concept-explanation Claude already knows; only minor prose could be trimmed (e.g. the overview sentence at line 17 and implementation-detail aside at line 78), matching anchor 4 rather than the tighter anchor 5.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case — `membrane login`, `membrane connection ensure`, `connection get --wait`, `action list --intent`, `action run --input`, and `membrane request` with a full proxy-flag table — fully executable and covering the main workflows.	5 / 5
Workflow Clarity	The connect workflow has a real feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, check error fields), but the destructive/batch data operations (create broadcasts to many recipients, delete contacts) lack explicit verification steps, and the referenced "Step 2" is never labeled as such, so per the batch/destructive cap it cannot exceed anchor 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but it is well-sectioned with clear headers and one-level navigation (no nested references); the only gap is that the 20-row Popular actions table could live in a reference file, leaving it at anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A solid description that explicitly covers both what and when and is anchored to a distinct product niche, but its action verb is generic and its trigger phrasing lacks concrete synonyms. Tightening the verb list and adding natural trigger terms would push it toward the top anchor.

Suggestions

Replace the single generic verb "Manage" with a few concrete actions, e.g. "List, create, update, and delete Accounts, Contacts, Recordings, Shortcodes, Keywords, and Broadcasts".

Make the "Use when" clause enumerate concrete triggers, e.g. "Use when the user wants to send voice/SMS broadcasts, manage contacts, or retrieve recordings in DialMyCalls".

Add natural synonyms users say (e.g. "mass notification", "voice broadcast", "SMS blast") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the DialMyCalls domain and lists six concrete entities ("Accounts, Contacts, Recordings, Shortcodes, Keywords, Broadcasts"), but covers them with a single generic verb ("Manage") rather than enumerating several distinct concrete actions, so it sits at the 3-4 boundary closer to anchor 3.	3 / 5
Completeness	Both halves are explicit: "Manage Accounts, Contacts..." states what it does and "Use when the user wants to interact with DialMyCalls data" states when, but the "when" clause is generic ("interact with DialMyCalls data") rather than listing concrete triggers, matching anchor 4 rather than anchor 5.	4 / 5
Trigger Term Quality	The product name "DialMyCalls" plus natural entity nouns ("Contacts", "Broadcasts", "Recordings", "Keywords") give good keyword coverage a user would actually say, though common synonyms (SMS, voice broadcast, mass notification, text blast) are missing, keeping it just below anchor 5.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ("DialMyCalls") with a product-scoped trigger ("interact with DialMyCalls data"), giving it a clear 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/dialmycalls/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.