Name: pirate-weather
Rating: 58.4 (1 reviews)
Author: membranedev

pirate-weather

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pirate-weather/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 a highly actionable, command-driven guide with a solid connection-state feedback loop, but it carries some unnecessary intro prose, redundant action-list duplication, and loose step numbering that hold back conciseness and workflow clarity.

Suggestions

Remove the opening marketing paragraph ('Pirate Weather is a weather API...used by developers and businesses...') and other non-essential prose that Claude does not need to execute the workflow.

Dedupe the action-list command: keep it in 'Searching for actions' and have 'Popular actions' either list actual common actions or point back to that section instead of restating the discovery command.

Tighten the workflow numbering — add a labeled 'Step 2' (and a '1a') so the 'skip to Step 2' reference resolves, and add a brief validation note for checking an action run's output for errors.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete commands, but the opening marketing paragraph about who uses Pirate Weather is unnecessary, some prose could be trimmed, and the action-list command is repeated across the 'Searching for actions' and 'Popular actions' sections.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for the entire workflow (install, login, connection ensure/get, action list/run, request proxy) plus a proxy-options table, covering the common cases.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence is present with an explicit connection-state feedback loop (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll until READY), but step numbering is loose ('skip to Step 2' with no labeled Step 2; '1b' without '1a') and there is no validation checkpoint after running an action.	4 / 5
Progressive Disclosure	Content is well-organized with clear section headers and logical flow, and all content is appropriately inline for a CLI-command skill; however there are no external references for a >50-line skill and the 'Popular actions' section is near-empty and redundant.	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 establishes a clear, distinct niche (Pirate Weather) with an explicit 'Use when' clause, but its action list is generic boilerplate and its trigger terms lack natural synonyms like 'forecast' or 'alerts'. It is functional but could be sharpened with concrete weather actions and richer trigger phrases.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete weather-specific ones, e.g. 'Fetch weather forecasts, current conditions, and alerts for a location'.

Add natural trigger synonyms users would actually say, such as 'forecast', 'weather forecast', 'current conditions', or 'weather alerts'.

Tighten the 'when' clause to reference concrete intents, e.g. 'Use when the user wants weather forecasts, current conditions, or alerts for a location via the Pirate Weather API.'

Dimension	Reasoning	Score
Specificity	The description names the Pirate Weather domain but the listed actions ('Manage data, records, and automate workflows') are generic boilerplate rather than concrete weather-specific actions like fetching forecasts or alerts.	2 / 5
Completeness	Both a 'what' ('Pirate Weather integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Pirate Weather data') are present, though the trigger could be more specific and concrete.	4 / 5
Trigger Term Quality	It includes 'Pirate Weather' and 'weather data' but misses common natural synonyms a user would say, such as 'forecast', 'weather forecast', 'current conditions', or 'alerts'.	3 / 5
Distinctiveness Conflict Risk	Pirate Weather is a specific named API and the trigger ('interact with Pirate Weather data') is narrowly scoped, giving it a clear niche with minimal conflict 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/pirate-weather/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.