Name: godial
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

godial

GoDial integration. Manage Leads, Users, Roles, Goals, Filters. Use when the user wants to interact with GoDial data.

Quality

76%

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/godial/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 body is a strong, actionable CLI integration guide with executable commands, clear state-driven connection workflow, and feedback loops. Its main weaknesses are light rhetorical padding and the absence of validation guidance for destructive actions.

Suggestions

Trim the opening GoDial product description and the "auth plumbing" aside to reduce token overhead.

Add a validation/safety note before destructive actions (remove-account, remove-member) such as confirming the target ID before running.

Consider moving the popular-actions and proxy-flag tables into a reference file to keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the opening product description of GoDial and "so you can focus on the integration logic rather than auth plumbing".	3 / 5
Actionability	Copy-paste-ready commands (login, connection ensure, action list/run, request) with flags and a popular-actions table provide fully executable, specific guidance covering the common cases.	5 / 5
Workflow Clarity	The connect→wait→search→run sequence is clearly laid out with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loops, though no validation guidance is given for destructive actions like remove-account.	4 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with no bundle files; content is organized into clear navigable sections, though the popular-actions and proxy-flag tables could arguably live in separate reference files.	4 / 5
	Total	16 / 20 Passed

Description

78%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 concise, names a distinct niche (GoDial), and includes an explicit Use-when clause covering both what and when. It is held back from a top score mainly by the generic trigger phrasing and the single-verb coverage of capabilities.

Suggestions

Vary the verbs to show distinct actions, e.g. "Create and manage Leads, Users, Roles, Goals, and Filters" rather than a single "Manage".

Sharpen the trigger clause with concrete phrases users say, e.g. "Use when the user wants to manage GoDial leads, agents, call logs, or dialer campaigns."

Add commonly used synonyms (calls, contacts, dialer, campaigns) to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Leads, Users, Roles, Goals, Filters" names the domain and several specific managed entities, though a single verb (Manage) covers them all rather than distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Both "what" (GoDial integration; manage Leads/Users/Roles/Goals/Filters) and "when" ("Use when the user wants to interact with GoDial data") are present and explicit, but the trigger clause is somewhat generic rather than listing concrete triggering phrases.	4 / 5
Trigger Term Quality	"GoDial" plus "Leads, Users, Roles, Goals, Filters" and "interact with GoDial data" give good keyword coverage of natural terms, but common phrasings like "dialer", "calls", or "contacts" are absent.	4 / 5
Distinctiveness Conflict Risk	"GoDial integration" carves out a clear niche with the distinctive "GoDial" trigger, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/godial/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.