Name: mozilla-observatory
Rating: 52 (1 reviews)
Author: membranedev

mozilla-observatory

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

Quality

57%

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

Quality

Content

57%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 actionable with solid CLI command coverage and a useful connection state-machine, but it is held back by an over-explained intro, a broken step-numbering scheme, an empty Overview section, and some command repetition. Tightening padding and fixing the cross-references would improve clarity and conciseness.

Suggestions

Fix the broken step numbering: add a real "Step 1"/"1a" label and either create a "Step 2" section header or reword the "skip to Step 2" reference to point at the actual "Searching for actions" section.

Remove the empty "Mozilla Observatory Overview" stub and trim the introductory paragraph that explains what Observatory is, since that is context Claude does not need.

De-duplicate the action-discovery command (it appears in both "Searching for actions" and "Popular actions") and add a brief note on validating action-run output or handling error states.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it over-explains what Mozilla Observatory is in the intro, includes an empty "Mozilla Observatory Overview" stub section, and repeats the action-list command in "Popular actions", so it could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests, plus a flag table; the main gap is reliance on placeholder IDs (CONNECTION_ID, actionId) without a fully worked end-to-end example.	4 / 5
Workflow Clarity	The connection state-machine has a clear polling feedback loop, but the text references a nonexistent "Step 2" and a "1b" with no "1a", and offers no validation guidance for action runs, leaving sequence and checkpoint gaps.	3 / 5
Progressive Disclosure	No bundle files are used and section headers are present, but the empty Overview stub and the redundant repetition of the search command show organization gaps for a body over 50 lines.	3 / 5
	Total	13 / 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 is identifiable and includes an explicit use-when trigger, but its capability language is generic boilerplate rather than concrete Observatory-specific actions, and its trigger terms lack useful synonyms. Sharpening the action list and adding natural trigger phrases would raise specificity and trigger quality.

Suggestions

Replace generic boilerplate ("Manage data, records, and automate workflows") with concrete Observatory actions such as scanning a site, retrieving scan grades, and reviewing HTTP header / TLS recommendations.

Add natural trigger synonyms users would actually say, e.g. "Use when the user wants to scan a website's security, check HTTP headers or TLS configuration, or review a Mozilla Observatory grade."

Make the use-when clause less tautological by naming the triggering scenarios (security scan, header/TLS review) rather than restating "interact with Mozilla Observatory data".

Dimension	Reasoning	Score
Specificity	The description names the domain ("Mozilla Observatory") but its actions — "Manage data, records, and automate workflows" — are generic Membrane boilerplate rather than concrete Observatory capabilities like scanning sites or reviewing security grades, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." clause, but the "when" is somewhat tautological ("interact with Mozilla Observatory data") and could be more specific, fitting the anchor for both present with room to sharpen.	4 / 5
Trigger Term Quality	It includes the natural keyword "Mozilla Observatory" and "data", but misses common variations and synonyms a user might say (security scan, HTTP headers, TLS, website grade), so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Mozilla Observatory" gives it a clear, distinct niche with low conflict risk, though the generic "manage data/workflows" framing is shared across Membrane integration skills, leaving minor overlap risk.	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/mozilla-observatory/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.