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

inspector

Inspector integration. Manage data, records, and automate workflows. Use when the user wants to interact with Inspector 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/inspector/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 body is a highly actionable, well-structured CLI integration guide with a clear connection workflow and validation checkpoints. Its main weaknesses are padding (the product intro and unexplained overview bullets) and a clearly wrong 'Official docs' link to Apple Quartz 2D documentation that is unrelated to Inspector.

Suggestions

Remove or replace the 'Official docs' URL pointing to Apple Quartz 2D documentation — it is unrelated to Inspector and actively misleading.

Trim the introductory paragraph ('It's used by software engineers and DevOps teams...') and either explain the Overview bullets (Case, Finding, Template, User, Integration) or remove them, since bare unexplained terms add tokens without guidance.

Label the workflow steps consistently (the body references 'Step 2' and uses a '1b' sub-step without a corresponding labeled 'Step 1a'/'Step 2') so the connection-to-action sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the introductory paragraph explaining who uses Inspector, the unexplained Overview bullets, and an irrelevant Apple Quartz 2D 'Official docs' URL are unnecessary padding the skill could be tightened around.	3 / 5
Actionability	It provides copy-paste-ready commands with realistic flags and a concrete JSON-input example covering connection, authentication, action search/run, and proxy requests across the common cases.	5 / 5
Workflow Clarity	The connection flow is a clear state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling validation and a re-poll feedback loop after user action; minor gaps like the unlabeled 'Step 2' reference keep it just below a 5.	4 / 5
Progressive Disclosure	The content is organized into well-labeled sections (install, auth, connecting, searching, running, proxy, best practices) with no need for external bundle files; structure is good with only minor organization gaps.	4 / 5
	Total	16 / 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 provides an explicit 'Use when' trigger and is tied to a specific product, but its capability list is generic ('manage data, records, automate workflows') rather than concrete. It reads as a serviceable but somewhat vague integration summary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Inspector-specific actions such as 'view errors, track performance bottlenecks, manage cases and findings'.

Broaden the trigger phrase with natural synonyms users might say, e.g. 'Use when the user wants to monitor application errors, inspect performance, or query Inspector cases and findings.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Inspector integration') but the actions — 'Manage data, records, and automate workflows' — are generic and abstract rather than concrete, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It has both a 'what' (Inspector integration to manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Inspector data'), though both could be more specific.	4 / 5
Trigger Term Quality	It includes some relevant keywords (Inspector, data, records, workflows) in an explicit trigger phrase, but lacks common synonyms or variations users might naturally say.	3 / 5
Distinctiveness Conflict Risk	The trigger is tied to the named Inspector product, making it mostly distinct with minimal conflict risk, though it could overlap with related Membrane integration skills.	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/inspector/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.