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

firehydrant

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/firehydrant/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 copy-paste ready CLI commands and a well-sequenced connection workflow including validation checkpoints. Its main weaknesses are minor verbosity in the intro and slightly inconsistent step numbering rather than structural problems.

Suggestions

Remove the filler intro paragraph and 'Use action names and parameters as needed.' since Claude already knows what an incident platform is.

Fix the step numbering: label the connection steps as 'Step 1/Step 2' consistently or remove the dangling 'skip to Step 2' reference.

Consider moving the detailed connection state-machine table into a references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient executable commands, but the intro paragraph ('used by SREs, DevOps engineers... to streamline incident workflows') explains context Claude already knows and 'Use action names and parameters as needed.' is filler, fitting 'mostly efficient but includes some unnecessary explanation' rather than the 4-anchor's only minor instances.	3 / 5
Actionability	Commands are copy-paste ready throughout (install, login, connection ensure, action list/run, request) with flags and JSON examples, and the proxy options table covers the common cases, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear with explicit state-machine validation and feedback loops (poll until READY, re-poll after user action), but 'skip to Step 2' references a non-existent Step 2 header and the '1b' numbering is inconsistent, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Sections are well-organized with no nested references and a single external docs link, but at ~140 lines with no bundle files the detailed connection state machine and proxy options are inlined rather than split out, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the 5-anchor.	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 correctly targets a named product and includes an explicit 'Use when' trigger, but its action list is generic and it omits the incident-specific trigger terms users would naturally say. It is functional but lacks the concrete, domain-specific vocabulary that would make it crisp and distinctive.

Suggestions

Replace generic verbs with FireHydrant-specific actions, e.g. 'Create and manage incidents, runbooks, and tasks; track severity and artifacts'.

Add concrete trigger terms users actually say, e.g. 'Use when the user mentions FireHydrant, incidents, on-call response, or runbooks'.

Tighten the 'when' clause to name the specific FireHydrant workflows (incident response, runbook execution) rather than 'interact with FireHydrant data'.

Dimension	Reasoning	Score
Specificity	The description names the FireHydrant domain but the actions "Manage data, records, and automate workflows" are generic verbs rather than concrete FireHydrant capabilities (e.g. incidents, runbooks), matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires concrete actions.	2 / 5
Completeness	It states both a 'what' (manage data, records, workflows) and an explicit 'Use when the user wants to interact with FireHydrant data' trigger, but the 'when' could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the 5-anchor which requires concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the keyword "FireHydrant" but the trigger phrase "interact with FireHydrant data" is generic and omits the natural incident/on-call/runbook terms users would actually say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product "FireHydrant" gives a clear niche with minimal conflict risk, but the generic action verbs leave minor overlap risk with adjacent data-management skills, fitting 'mostly distinct; minor overlap risk' rather than the 5-anchor's fully distinct triggers.	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/firehydrant/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.