Name: oh-dear
Rating: 56.8 (1 reviews)
Author: membranedev

oh-dear

Oh Dear! integration. Manage data, records, and automate workflows. Use when the user wants to interact with Oh Dear! data.

Quality

65%

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

Quality

Content

67%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 highly actionable with real CLI commands and a clear connection-state workflow including validation feedback loops. It is held back by a padded introductory explanation and a broken 'Step 2' reference rather than any structural problem.

Suggestions

Delete or condense the introductory paragraph defining what Oh Dear! is; Claude can infer the service from the named app and overview list.

Label the 'Step 2' referenced in the READY branch (e.g. add a '### Step 2 — Search and run actions' header) so the cross-reference resolves.

Add one or two concrete Oh Dear! action examples (e.g. listing sites or creating a maintenance window) so the actionability reaches fully specific coverage.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Oh Dear! is ("a website monitoring service that checks your site for uptime, performance, and broken links") and phrases like "so you can focus on the integration logic rather than auth plumbing" add explanation Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready membrane commands (login, connection ensure, action list/run, request) with a flags table, but uses literal placeholders (CONNECTION_ID, QUERY) and gives no concrete Oh Dear!-specific action examples, leaving minor gaps versus the level-5 anchor.	4 / 5
Workflow Clarity	The connect-then-poll-then-act sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after user action), but a referenced 'Step 2' is never labeled, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-sectioned (Overview, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, and the modest length keeps the monolith acceptable; absence of any separate reference files leaves it just short of the ideal split structure.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly states both what the skill does and when to use it, and the named app keeps conflict risk low. Its main weakness is generic verbs and missing concrete monitoring trigger terms that users would naturally say.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Monitor site uptime, schedule maintenance windows, and check SSL/broken-link health."

Add natural trigger phrases users would say, such as "Use when the user asks about Oh Dear! monitoring, uptime, SSL certificates, or broken links."

Tighten the 'when' clause from "interact with Oh Dear! data" to specific intents to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain ("Oh Dear! integration") and lists several actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete, fitting the 1-2-concrete-actions anchor and stopping short of the specific-action list at level 4.	3 / 5
Completeness	Both halves are present ("Manage data, records, and automate workflows" for what; "Use when the user wants to interact with Oh Dear! data" for when), but the 'when' trigger is generic rather than concrete phrases, which is the level-4 anchor rather than 5.	4 / 5
Trigger Term Quality	It surfaces "Oh Dear!" and "data" but omits the natural monitoring vocabulary a user would say (uptime, SSL, broken links, monitoring), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the proprietary "Oh Dear!" app gives it a clear niche with minimal overlap risk, but the generic trigger wording leaves minor ambiguity versus other monitoring/data skills, placing it at 4 rather than 5.	4 / 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/oh-dear/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.