Name: appsignal
Rating: 60.8 (1 reviews)
Author: membranedev

appsignal

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

Quality

71%

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

Quality

Content

81%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 copy-paste-ready Membrane CLI commands and a well-sequenced, validated connection workflow, and it is mostly token-efficient. Its main weaknesses are minor verbosity in the intro/best-practices rationale and a few inlined reference-style blocks that could be split out.

Suggestions

Trim the opening 'AppSignal is a performance monitoring tool...' paragraph and the Membrane rationale, since Claude already knows these concepts.

Move the proxy flag table and agent-type list into a references file to keep the top-level overview leaner.

Add an explicit validation/checkpoint note to the action-search and action-run steps (e.g. inspect inputSchema/outputSchema before running) to match the connection workflow's rigor.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable CLI snippets and a flag table; minor padding (the AppSignal 'what it is' intro paragraph and the Membrane rationale restated in Best practices) could be trimmed, fitting the 'efficient with minor over-explanation' anchor.	4 / 5
Actionability	Commands are copy-paste ready and cover the common cases (install, login, connection ensure/get, action list/run, request proxy) with concrete flags and JSON examples, matching the 'fully executable, copy-paste ready, common cases covered' anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state checks and error feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but other flows (searching actions, running actions) lack explicit checkpoints, fitting 'clear sequence with most checkpoints, minor validation gaps'.	4 / 5
Progressive Disclosure	As a single self-contained file with no bundle, content is well organized into headed sections (Overview, Connecting, Searching actions, Popular actions, Proxy, Best practices); it earns 4 rather than 5 because some reference-like material (the flag table, agent-type list) is inlined where a separate reference could reduce top-level tokens.	4 / 5
	Total	17 / 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 covers both what the skill does and when to use it with a clear named-tool trigger, but its action verbs are generic and it lacks the natural synonyms (errors, performance, incidents) a user would actually say. It is solid but leaves distinctiveness and specificity under-served.

Suggestions

Replace generic verbs with AppSignal-specific actions, e.g. 'Investigate incidents, triage errors, and analyze performance issues in AppSignal.'

Add natural trigger keywords users say, such as 'AppSignal errors', 'incidents', 'performance issues', or 'N+1 queries'.

Tighten the 'Use when' clause to concrete intents, e.g. 'Use when the user wants to investigate AppSignal incidents, errors, or performance problems.'

Dimension	Reasoning	Score
Specificity	Names the AppSignal domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete capabilities, matching the 'domain plus 1-2 actions, not comprehensive' anchor.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with AppSignal data'), with the trigger explicit but somewhat generic, matching the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	'AppSignal' and 'interact with AppSignal data' are relevant natural keywords, but common synonyms or variations (e.g. 'errors', 'performance monitoring', 'incidents') are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named AppSignal tool and 'interact with AppSignal data' trigger form a mostly distinct niche with only minor overlap risk against a generic data-management skill.	4 / 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/appsignal/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.