Name: data247
Rating: 52.8 (1 reviews)
Author: membranedev

data247

Data247 integration. Manage Organizations, Activities, Notes, Files, Pipelines, Users and more. Use when the user wants to interact with Data247 data.

Quality

59%

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

Quality

Content

56%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 delivers executable, well-sequenced CLI guidance with a clear connection state machine, which is its main strength. It is weighed down by a bloated 85-item overview list, missing post-action validation, and an unlabeled "Step 2" reference that breaks the otherwise clear workflow.

Suggestions

Remove or collapse the ~85-item "Data247 Overview" bullet list, especially the redundant "X Template" entries, to reclaim token budget; keep only entities the agent actually acts on.

Fix the "Skip to Step 2" / "1b" numbering so steps are labeled consistently (1a/1b/2) and the referenced Step 2 exists.

Add an explicit verify/validate checkpoint after running an action (e.g. check the `output` field and error states) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose primarily because of the ~85-item "Data247 Overview" bullet list (entities plus duplicated "X Template" variants) that is heavy padding, alongside minor over-explanation of auth plumbing; the command sections themselves are reasonably efficient.	2 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) and a flag table, but examples use placeholders like <actionId> and CONNECTION_ID and the popular-actions table gives keys without full runnable run examples.	4 / 5
Workflow Clarity	There is a clear install → authenticate → ensure connection → poll/handle state → search → run → proxy sequence with state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry loop, though "Skip to Step 2" references an unlabeled step and post-action verification is absent.	4 / 5
Progressive Disclosure	Section headers give it some structure, but with no bundle files all content is inlined in one ~227-line file and the large entity list is content that should be separated or trimmed, so organization is only partial with no signaled references.	3 / 5
	Total	13 / 20 Passed

Description

62%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 brand-specific and includes an explicit "Use when" trigger, covering both what and when. It is held back by a single generic verb ("Manage"), a vague "and more", and a generic trigger phrase rather than concrete natural-language triggers.

Suggestions

Replace the generic verb "Manage" with concrete Data247 actions users request, e.g. "Look up phone and email contacts, verify emails, append phone numbers, reverse-lookup callers".

Drop "and more" or replace it with the actual remaining capabilities so coverage is explicit.

Tighten the "Use when" clause with natural triggers, e.g. "Use when the user wants to look up, verify, or enrich contact data via Data247".

Dimension	Reasoning	Score
Specificity	It names the domain and enumerates many concrete entities ("Manage Organizations, Activities, Notes, Files, Pipelines, Users"), but the single generic verb "Manage" plus "and more" leaves the actual actions unspecified rather than comprehensive.	3 / 5
Completeness	It explicitly answers both what ("Manage Organizations, Activities, Notes, Files, Pipelines, Users...") and when ("Use when the user wants to interact with Data247 data"), but the when clause is generic rather than concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	The brand keyword "Data247" and trigger clause "Use when the user wants to interact with Data247 data" are present, but the verb "interact with" is generic and natural variations users would say (look up, verify, enrich, append) are missing.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named service "Data247" gives it a clear niche with minimal conflict risk, but the surrounding "interact with...data" phrasing is generic enough to keep it just below the most distinct anchor.	4 / 5
	Total	14 / 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/data247/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.