Name: littledata
Rating: 56.8 (1 reviews)
Author: membranedev

littledata

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

Quality

65%

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/littledata/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 body is a strong, command-heavy integration guide with clear auth/connection workflows and validation feedback loops, held back by some marketing padding, inconsistent CLI invocation forms, and a couple of dangling step references.

Suggestions

Trim the marketing opener and the empty "Littledata Overview" bullet list to tighten token efficiency.

Standardize on one invocation form (membrane vs npx @membranehq/cli) and add one fully-worked example with realistic substituted values.

Fix the dangling "Step 2" reference and relabel the "1b" substep so the connection sequence reads as a coherent numbered flow.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes padding such as the marketing-style opener ("Littledata automatically fixes data discrepancies...") and the bare "Littledata Overview" bullet list (Connection/Metrics/Report) that adds no actionable value, plus a repeated action-list command across sections.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (membrane login, connection ensure, action run, request) with a full proxy-flag options table, but relies on unsubstituted placeholders (CONNECTION_ID, QUERY, <actionId>) and mixes `membrane` vs `npx @membranehq/cli` invocations without a worked end-to-end example.	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state-checking feedback loops (poll until READY, branch on CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but references to a "Step 2" that is never labeled and a lone "1b" substep introduce minor sequencing gaps.	4 / 5
Progressive Disclosure	Content is organized into clear, single-level sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested or dead references, though some inline detail like the clientAction object spec and the proxy flag table could live in separate reference files.	4 / 5
	Total	15 / 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 answers both what and when and is anchored to a distinct product name, but its actions are generic and its trigger terms omit the Shopify/Google Analytics/ecommerce vocabulary users would actually say.

Suggestions

Replace generic verbs with concrete Littledata capabilities (e.g., fix Shopify data discrepancies, sync marketing attribution to Google Analytics).

Expand the "Use when..." clause to include natural trigger terms like Shopify, Google Analytics, ecommerce, and marketing attribution.

Add file-extension or product synonyms where applicable so the description surfaces on the phrases users naturally say.

Dimension	Reasoning	Score
Specificity	Names the domain ("Littledata integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic verbs rather than concrete capabilities like the PDF examples, so it sits at the 1-2 concrete actions level rather than comprehensive.	3 / 5
Completeness	Both "what" (Littledata integration managing data/records/workflows) and "when" ("Use when the user wants to interact with Littledata data") are present, but the "when" clause is generic rather than listing concrete trigger phrases, matching the anchor where "when" could be more explicit.	4 / 5
Trigger Term Quality	It includes "Littledata" and the trigger phrase "Use when the user wants to interact with Littledata data", but misses the natural synonyms a user would actually say (Shopify, Google Analytics, ecommerce, marketing attribution) that the body reveals as the real use case.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the specific named product "Littledata" gives it a clear niche with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing carries minor overlap risk with other data-oriented integrations.	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/littledata/SKILL.md
Commit: f484c82

Reviewed: 6 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.