Name: apiflash
Rating: 58.4 (1 reviews)
Author: membranedev

apiflash

ApiFlash integration. Manage Organizations, Pipelines, Projects, Users, Filters. Use when the user wants to interact with ApiFlash data.

Quality

67%

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/apiflash/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 delivers strong executable CLI commands and a well-structured connection state machine with feedback loops, but it carries a marketing intro and prose padding that dilute token efficiency, and a couple of structural references are unresolved.

Suggestions

Remove the opening marketing paragraph and the 'so you can focus on the integration logic' aside; Claude does not need ApiFlash's business positioning.

Fix the 'Skip to Step 2' reference by labeling the Searching-for-actions section as Step 2, and add an explicit validation step after `membrane action run` (check the `output` field for errors).

Fill the empty Description cells in the Popular actions table (e.g. capture-screenshot: 'Capture a full-page screenshot of a URL').

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening marketing paragraph ("Developers and businesses use it to automate website previews..."), the "so you can focus on the integration logic rather than auth plumbing" aside, and prose best-practices add unnecessary explanation Claude does not need, matching 'mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	Concrete copy-paste commands (npm install, membrane login, connection ensure, action run, request) with a full proxy flag table provide mostly executable guidance, but placeholders like CONNECTION_ID and empty Description cells in the Popular actions table leave minor gaps, fitting 'concrete code or commands with minor gaps.'	4 / 5
Workflow Clarity	The connect step has a clear state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a poll-again feedback loop, giving a clear sequence with most checkpoints, but the 'Skip to Step 2' reference points to no labeled Step 2 and there is no explicit success verification after running an action, so it is not a 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single document is well-organized with clear section headers (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) for easy navigation, matching 'good structure; most content appropriately placed; minor organization gaps'; not a 5 because the Popular-actions table and proxy flag reference are inlined rather than split out.	4 / 5
	Total	15 / 20 Passed

Description

67%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 clearly names the integration and its resources and includes a 'Use when' trigger, but the trigger is product-name-based rather than task-based, omitting natural screenshot/capture phrasing users would actually say.

Suggestions

Add task-oriented trigger terms users naturally say, e.g. 'Use when the user wants to capture a screenshot of a website, generate a thumbnail, or monitor website changes.'

Replace the single generic verb 'Manage' with distinct concrete actions (e.g. 'Capture screenshots, check quota, manage organizations and projects') to lift specificity.

Tie the 'when' clause to concrete ApiFlash tasks (screenshots/quota) rather than the vague 'interact with ApiFlash data'.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Projects, Users, Filters" lists several concrete resource types to act on, matching the 'lists several specific actions; minor gaps' anchor; not a 5 because a single generic verb 'Manage' covers all of them rather than distinct verbs.	4 / 5
Completeness	It states both what ("ApiFlash integration. Manage Organizations, Pipelines, Projects, Users, Filters") and when ("Use when the user wants to interact with ApiFlash data"), but the 'when' trigger is generic rather than concrete, fitting the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The product name "ApiFlash" and "interact with ApiFlash data" are present, but natural user phrasing like "screenshot", "capture website", or "thumbnail" is missing, matching 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "ApiFlash" gives a clear niche with minimal conflict risk, though generic Membrane resource names (Organizations, Pipelines, Users) create minor overlap with sibling Membrane skills, matching 'mostly distinct; minor overlap risk.'	4 / 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/apiflash/SKILL.md
Commit: f484c82

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