Name: elmahio
Rating: 55.2 (1 reviews)
Author: membranedev

elmahio

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

Quality

63%

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

Quality

Content

68%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 well-structured and highly actionable with concrete, executable Membrane CLI commands and a clear connection workflow with feedback loops, though it introduces destructive actions without validation guidance and carries minor verbosity in the intro.

Suggestions

Add a validation/confirmation checkpoint before destructive actions, e.g. 'Before running delete-* actions, confirm the target ID with the user and verify it exists via the corresponding get-* action.'

Trim the introductory Elmah.io marketing paragraph ('cloud-based error logging and monitoring service... real-time insights into application health') since Claude already understands the domain.

Consider moving the Popular actions table into a references/actions.md file and linking to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the introductory description of what Elmah.io is.	4 / 5
Actionability	Quotes provide copy-paste-ready commands (e.g. 'membrane connection ensure "https://elmah.io" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json') with flags and JSON examples; minor gaps are the unsubstituted placeholders (CONNECTION_ID, <actionId>).	4 / 5
Workflow Clarity	The connection setup flow is well-sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and re-poll feedback, but the skill surfaces destructive actions (delete-deployment, delete-message, delete-log) with no validation or verification guidance, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The body is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices) and is self-contained with no nested references; the minor gap is the bulky 17-row Popular actions table that could live in a separate reference file.	4 / 5
	Total	15 / 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 correctly names the target app and includes both a what and a when clause, but its capability language is generic ('manage data, records, and automate workflows') and it omits the concrete Elmah.io-specific terms (errors, logs, uptime) users would naturally say.

Suggestions

Replace generic actions with Elmah.io-specific capabilities, e.g. 'Log and monitor application errors, manage logs, deployments, and uptime checks.'

Expand the trigger clause with concrete user phrases: 'Use when the user wants to view or fix application errors, search error logs, or manage Elmah.io logs and deployments.'

Add file/term synonyms users say naturally, such as 'error monitoring' and 'exception logging', to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Elmah.io domain but the actions are generic ('manage data', 'records', 'automate workflows') rather than concrete Elmah.io capabilities like error logging, logs, or uptime checks.	2 / 5
Completeness	Both 'what' ('Elmah.io integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with Elmah.io data.') are explicitly present, though the trigger clause is generic rather than concrete.	4 / 5
Trigger Term Quality	Quotes 'Elmah.io' and 'interact with Elmah.io data' provide the natural app-name keyword, but common terms users would actually say for this service ('errors', 'logs', 'error monitoring', 'uptime checks') are missing.	3 / 5
Distinctiveness Conflict Risk	Quotes 'Elmah.io integration' name a specific app, giving a clear niche with minimal conflict risk; only minor overlap risk comes from the generic 'manage data, records, and automate workflows' phrasing.	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/elmahio/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.