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

Blog Docs Log in Get started

getscreenshot

GetScreenshot integration. Manage Screenshots. Use when the user wants to interact with GetScreenshot data.

Quality

68%

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

Quality

Content

75%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 highly actionable with copy-paste-ready commands, a concrete connection-state workflow with a retry loop, and clean section structure. Its main weaknesses are a padded introductory paragraph explaining concepts Claude can infer and a dangling "Step 2" cross-reference.

Suggestions

Trim the introductory paragraph that explains what GetScreenshot is and who uses it; Claude can infer the product purpose, so lead with the integration mechanics.

Fix the dangling "skip to Step 2" reference by either labeling the next section as Step 2 or rewording to "skip to Searching for actions".

Consider moving the popular-actions table and proxy flag reference into a separate reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the intro paragraph explains what GetScreenshot is ("a tool that allows users to capture screenshots… used by developers, QA testers, and designers") and includes filler like "Use action names and parameters as needed", fitting the score-3 anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a concrete popular-actions table and a flags table, covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	Clear sequenced flow (install → login → ensure connection → wait for READY → search → run/proxy) with explicit state handling and a retry/poll feedback loop, but the dangling "skip to Step 2" reference with no labeled Step 2 is a minor clarity gap, matching the score-4 anchor.	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clearly labeled sections and no bundle files; structure is good and navigable, though the inlined popular-actions table and proxy flag reference are bulk content that could live in separate files, fitting the score-4 anchor.	4 / 5
	Total	16 / 20 Passed

Description

61%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 states both capability and trigger context and is well-differentiated via the named product, but its action verbs are generic and the trigger phrasing lacks concrete, varied keywords. Tightening "Manage Screenshots" into specific verbs (capture, take, export) and expanding trigger synonyms would raise the score.

Suggestions

Replace generic verbs with concrete actions, e.g. "Capture, take, and export screenshots of web pages" instead of "Manage Screenshots".

Expand the trigger clause with natural user phrases and synonyms, e.g. "Use when the user wants to take a screenshot, capture a web page, or generate a PDF/image of a site."

Keep the GetScreenshot product anchor but pair it with the concrete actions so the what/when are both specific.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Screenshots" and "interact with GetScreenshot data" — it names the domain but the verbs ("Manage", "interact with") are generic rather than concrete actions like "capture" or "extract", matching the score-2 anchor.	2 / 5
Completeness	Both "what" ("GetScreenshot integration. Manage Screenshots.") and "when" ("Use when the user wants to interact with GetScreenshot data.") are present, but the "when" trigger is generic rather than a concrete trigger phrase, matching the score-4 anchor.	4 / 5
Trigger Term Quality	Includes the natural domain keywords "Screenshots" and "GetScreenshot" that users would say, but misses common variations/synonyms (capture, web page, image of a page) and any file extensions, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The description is anchored to the specific named product "GetScreenshot", giving it a clear niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 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/getscreenshot/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.