Name: eyepopai
Rating: 53.6 (1 reviews)
Author: membranedev

eyepopai

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

Quality

60%

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

Quality

Content

63%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 strongly actionable, executable guide with a clear connect-and-poll workflow and good error-state handling, though it carries minor padding and relies on a single monolithic file. Splitting the proxy/clientAction reference material into bundle files and trimming the marketing intro would improve both conciseness and progressive disclosure.

Suggestions

Move the proxy flag table and detailed clientAction object spec into a references/ file, linking from SKILL.md to enable one-level-deep progressive disclosure.

Trim the e-commerce/marketer intro paragraph and the filler line 'Use action names and parameters as needed.' to respect the token budget.

Name a few concrete popular EyePop.ai actions (e.g. create-video, add-subtitle) instead of only instructing the reader to discover them, and label the workflow steps consistently so 'Step 2' references resolve.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient executable commands, but the e-commerce/marketer intro paragraph and filler like 'Use action names and parameters as needed' add unnecessary explanation that could be trimmed, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connect, search, run, and proxy with a clear options table, but the 'Popular actions' section only instructs discovery without naming concrete actions and the overview tree is abstract, leaving minor gaps.	4 / 5
Workflow Clarity	The connect-to-ready flow is well sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a poll-until-ready feedback loop, but the 'skip to Step 2' reference points to an unlabeled step and numbering is slightly inconsistent.	4 / 5
Progressive Disclosure	Content is well sectioned but entirely monolithic in one ~140-line file with no bundle references; reference-like material (the proxy flag table and detailed clientAction object structure) is inlined rather than split into separate files.	3 / 5
	Total	14 / 20 Passed

Description

57%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 correctly pairs a 'what' with an explicit 'Use when...' trigger and is anchored by a distinctive brand name, but its action verbs are generic abstract categories rather than concrete capabilities. Tightening the action list to specific operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete EyePop.ai operations such as 'create product videos, manage projects, and add subtitles'.

Add natural synonyms and file/asset terms users would actually say (e.g. 'product videos, EyePop projects, subtitles') to broaden trigger coverage.

Keep the explicit 'Use when...' clause but make the trigger more specific to EyePop.ai tasks rather than the generic 'interact with EyePop.ai data'.

Dimension	Reasoning	Score
Specificity	The description names the domain (EyePop.ai) but the actions — 'Manage data, records, and automate workflows' — are generic abstract categories rather than concrete operations, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both 'what' (EyePop.ai integration; manage data/records/workflows) and an explicit 'when' clause ('Use when the user wants to interact with EyePop.ai data') are present; the 'what' is slightly generic so it sits just below the fully concrete top anchor.	4 / 5
Trigger Term Quality	It includes the natural brand term 'EyePop.ai' and the trigger phrase 'interact with EyePop.ai data', but the remaining keywords (data, records, workflows) are generic and lack common synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The EyePop.ai brand name anchors a clear niche with low conflict risk, but the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with other data-management skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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/eyepopai/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.