Name: datananas
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

datananas

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

Quality

66%

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

Quality

Content

67%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 actionable and well-structured with a clear connection state-machine workflow, but it carries some redundant padding, a dangling step reference, and an empty Popular actions section that limit conciseness and workflow clarity.

Suggestions

Remove the duplicate "Popular actions" section or populate it with concrete example actions (e.g. create prospect, start sequence) instead of restating the discovery command.

Fix the dangling "skip to Step 2" reference by labeling the subsequent sections as numbered steps or replacing it with an explicit section link.

Trim padding such as the "auth plumbing" aside and the ungrammatical "Agent Types" sentence, and add a brief verification step after running actions or destructive proxy calls.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but includes avoidable padding such as a duplicate "Popular actions" section that restates the action-list command, the "auth plumbing" aside, and an ungrammatical "Agent Types" line, matching the anchor for mostly efficient content that could be tightened.	3 / 5
Actionability	It provides concrete copy-paste commands across install, login, connection ensure/get, action list/run, and a proxy flags table covering the common cases, with a minor gap that the "Popular actions" heading lists no actual actions and only restates discovery.	4 / 5
Workflow Clarity	The connect -> wait -> handle-state workflow is clearly sequenced with an explicit feedback loop (poll again after the user completes the action), but "skip to Step 2" is a dangling reference with no labeled Step 2, and there is no output verification for run/proxy calls, fitting anchor 4 rather than 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear, well-labeled sections with no broken references, though the dense inline connection state-machine could be split into a reference file, matching anchor 4 for good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

66%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 covers both what and when with a clearly distinct product niche, but its capability actions are generic and it relies on a single trigger keyword without synonyms or variations.

Suggestions

Replace generic verbs with concrete Datananas actions, e.g. "Create and manage prospects, build email sequences, and trigger outreach campaigns" instead of "Manage data, records, and automate workflows".

Add more natural trigger phrases and synonyms, e.g. "Use when the user wants to work with Datananas prospects, email sequences, or sales outreach."

Use third-person action verbs consistently and keep the when clause tied to specific Datananas objects users mention.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a few actions, but the actions are generic rather than concrete (e.g. "manage data"), matching the anchor for domain + 1-2 actions that are not comprehensive.	3 / 5
Completeness	It explicitly answers both what ("Datananas integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Datananas data."), but the when clause is a single generic trigger rather than comprehensive concrete triggers, so it sits at anchor 4 not 5.	4 / 5
Trigger Term Quality	The only natural keyword is "Datananas" / "Datananas data"; it is the phrase a user would say but no synonyms or variations are provided, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Datananas with a product-specific trigger ("interact with Datananas data") gives a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/datananas/SKILL.md
Commit: f484c82

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