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

Blog Docs Log in Get started

raygun

Raygun integration. Manage data, records, and automate workflows. Use when the user wants to interact with Raygun 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/raygun/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 CLI commands and a solid connect-and-poll workflow, but it carries some padding in the intro and asides and could split its detailed reference material into bundle files.

Suggestions

Trim the opening marketing paragraph and "rather than auth plumbing"-style asides to assume Claude's competence.

Fix the step numbering (define explicit Step 1 / Step 2 headers instead of a lone "1b" and a referenced-but-unlabeled "Step 2").

Move the clientAction state-machine detail and proxy flag table into a references/ file, leaving SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but the opening marketing paragraph ("improving user experience"), the "rather than auth plumbing" aside, and the bare "Use action names and parameters as needed" line add unnecessary explanation that could be trimmed.	3 / 5
Actionability	Copy-paste-ready bash commands cover install, login, connection ensure/get, action list/run, and proxy requests, plus a concrete flag table — fully executable across the common cases.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with a state-checking feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the "1b" / "Step 2" numbering is inconsistent and some checkpoints are implicit.	4 / 5
Progressive Disclosure	The single file is well-sectioned with clear headers and an external official-docs link; with no bundle files present, structure is appropriate, though the detailed clientAction state machine and proxy flag table could live in separate reference files.	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 has an explicit use-when trigger and a distinct product niche, but its capability description is generic ("manage data, records, automate workflows") rather than reflecting Raygun's actual error/crash-monitoring features.

Suggestions

Replace generic actions with concrete Raygun capabilities, e.g. "Query error groups, crash reports, users, sessions, and deployments."

Add natural trigger synonyms users would say, such as "errors", "crash reports", or "performance monitoring".

Keep the existing "Use when the user wants to interact with Raygun data" clause but pair it with the more specific capability list.

Dimension	Reasoning	Score
Specificity	It names the domain ("Raygun integration") but the actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete Raygun capabilities like error monitoring or crash reports.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Raygun data") are present; the "what" is generic, keeping it just below a 5.	4 / 5
Trigger Term Quality	The keyword "Raygun" / "Raygun data" is present and natural, but it misses common variations and synonyms users would actually say (errors, crash reports, monitoring, deployments).	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product "Raygun" with the trigger "interact with Raygun data" gives it a clear niche with minimal overlap risk against other skills.	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/raygun/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.