Name: peekdata
Rating: 60 (1 reviews)
Author: membranedev

peekdata

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/peekdata/SKILL.md

Quality

Content

78%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 highly actionable with copy-paste CLI commands and a well-sequenced connect-and-poll flow with validation checkpoints. Its weaknesses are a slightly padded intro, an undefined 'Step 2' reference, and no progressive disclosure via referenced files for a skill this size.

Suggestions

Trim the opening overview paragraph explaining what Peekdata is, since Claude can infer the platform's purpose from the actions.

Define or remove the dangling 'Step 2' reference, and explicitly number the action-discovery -> run -> inspect-output sequence.

Consider splitting the connection-state/clientAction reference and proxy flag table into a referenced file (e.g. REFERENCE.md) signaled from the body, to add one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with direct CLI commands and a flag table, but the opening paragraph explaining what Peekdata is ('a data analytics platform that helps businesses visualize...') and the redundant action-list command in 'Popular actions' are minor over-explanation that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout: install, login, connection ensure, action list/run with --input JSON, and a proxy-request flag table covering the common cases.	5 / 5
Workflow Clarity	The connect flow is sequenced with validation checkpoints (poll for state, handle clientAction, poll again, check error), but 'Step 2' is referenced yet never defined and the action-discovery flow is loosely ordered, leaving minor validation/sequencing gaps.	4 / 5
Progressive Disclosure	No bundle files exist and no external references are signaled; all content is inline under section headers for a non-trivial (~140 line) skill, which is some structure but lacks the file-splitting and navigation the rubric expects above this level.	3 / 5
	Total	16 / 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 names the domain, lists a few actions, and includes an explicit 'Use when' trigger, satisfying both what and when. It is held back by generic verbs and limited keyword/synonym coverage rather than Peekdata-specific terminology.

Suggestions

Replace generic verbs with Peekdata-specific actions, e.g. 'query datasets, build dashboards and charts, and automate Peekdata workflows'.

Expand trigger terms to include natural synonyms users say, such as dashboards, charts, datasets, visualize, and reporting.

Make the 'Use when' clause concrete with trigger phrases, e.g. 'Use when the user wants to query Peekdata datasets, build dashboards/charts, or automate Peekdata workflows'.

Dimension	Reasoning	Score
Specificity	Names the Peekdata domain plus three actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than the platform's specific operations (dashboards/charts/datasets), matching the anchor for 1-2 concrete actions that are not comprehensive.	3 / 5
Completeness	Provides a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Peekdata data' trigger; the 'when' is present but generic rather than concrete phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'Peekdata' plus 'data', 'records', and 'workflows', but is missing common user variations and synonyms like dashboards, charts, datasets, visualize, or reporting.	3 / 5
Distinctiveness Conflict Risk	The named 'Peekdata' niche is mostly distinct, though the generic 'Manage data, records, automate workflows' phrasing leaves minor overlap risk with other data-handling skills.	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/peekdata/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.