Name: scout-apm
Rating: 60 (1 reviews)
Author: membranedev

scout-apm

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

Quality

70%

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/scout-apm/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 highly actionable with executable commands and a clear state-driven connection workflow, but it carries some unnecessary concept explanation and a broken 'Step 2' cross-reference that slightly dent conciseness and workflow clarity.

Suggestions

Trim the introductory paragraph that defines what Scout APM is and the 'so you can focus on the integration logic' filler; Claude already knows APM concepts.

Fix the 'skip to Step 2' reference by adding an explicit '## Step 2: Search and run actions' header so the cross-reference resolves.

Add an explicit result-verification note after `membrane action run` (e.g. check the `output` field and handle non-2xx errors) to close the validation gap in the run-actions workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and operational guidance, but it opens by explaining what Scout APM is ('an application performance monitoring tool... provides insights into slow database queries, N+1 issues') and includes filler like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than a 4.	3 / 5
Actionability	The content is packed with copy-paste-ready, executable commands covering the common cases — install, login (incl. headless), connection ensure, polling, action list/run with JSON input, and proxy requests with a flag table — matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is a clear state-machine sequence (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with a polling feedback loop and error-field guidance, but the 'skip to Step 2' reference points to no actual Step 2 header and result verification after running actions is only implicit, so it sits at 'clear sequence with most checkpoints; minor validation gaps' rather than a 5.	4 / 5
Progressive Disclosure	The skill has no bundle files and is self-contained, with well-organized sections (Overview, Working with Scout APM, Install, Auth, Connecting, Searching, Popular actions, Best practices) and easy navigation; it scores 4 rather than 5 because it exceeds 50 lines with no overview-to-detail split and the 'Scout APM Overview' section is a thin unlabeled feature list rather than a real overview.	4 / 5
	Total	16 / 20 Passed

Description

66%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 with an explicit trigger and a clear product-specific niche, but the action verbs are generic and the trigger lacks synonyms or concrete scenario phrases.

Suggestions

Replace generic verbs ('manage data, records') with concrete Scout APM operations, e.g. 'inspect traces, slow queries, N+1 issues, endpoints, and errors'.

Expand the 'Use when' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to investigate slow requests, N+1 queries, or endpoint errors in Scout APM'.

Add file- or domain-level keywords (e.g. 'APM', 'performance monitoring', 'traces') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Scout APM integration') and several action areas ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations like 'extract' or 'fill', so it sits at the domain-plus-actions-but-not-comprehensive level rather than a 2 (purely minimal) or a 4 (specific concrete actions).	3 / 5
Completeness	Both halves are present — 'what' ('Manage data, records, and automate workflows') and an explicit 'when' clause ('Use when the user wants to interact with Scout APM data') — but the trigger is generic rather than pinpointing concrete scenarios, fitting the 'has both what and when; when could be more specific' anchor and avoiding the missing-trigger cap of 3.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Scout APM data' supplies the core keyword 'Scout APM', but it lacks natural synonyms or variations a user might say (e.g. 'performance monitoring', 'slow queries', 'traces', 'N+1'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Scout APM' is a specific named product, so the description carves a clear niche with a distinct trigger ('interact with Scout APM data') and minimal overlap risk with other skills.	5 / 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/scout-apm/SKILL.md
Commit: f484c82

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