unified-notifications-ops

Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.

Quality

77%

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/unified-notifications-ops/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.

A well-structured, actionable planning skill with a clear sequenced workflow and a concrete output template, hindered mainly by cross-section repetition of the severity/routing logic that inflates the token budget. No external references are needed and none are referenced.

Suggestions

Consolidate the interrupt/digest/suppress guidance so it lives once (e.g., in the severity table) and is merely referenced from workflow step 2 and the recommendation rules, rather than restated.

Merge or trim 'Good Use Cases' against 'When to Use' to remove overlapping trigger phrasing and save tokens.

Add one explicit checkpoint in the workflow (e.g., 'confirm the inventory and severity model are complete before designing routing') to give the sequence a validation beat.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-style prose with no padding about concepts Claude already knows, but the interrupt/digest/suppress logic is restated across the severity table, workflow step 2, recommendation rules, and output format, so it could be tightened.	3 / 5
Actionability	Concrete, actionable guidance throughout — a copy-paste Output Format template, a severity table with examples and handling, specific duplicate patterns to look for, and a source/gate/shape/channel/action routing schema — with only minor abstract phrasing in the 'decide what deserves interruption' step.	4 / 5
Workflow Clarity	A clearly sequenced five-step workflow (inventory, decide interruption, collapse duplicates, design ECC-native workflow, return action-biased design) each with specific sub-actions; no explicit validation checkpoints, but the planning task is non-destructive so that gap is minor.	4 / 5
Progressive Disclosure	Single self-contained file with no bundle files present; content is well-organized into clearly headed sections that appropriately belong inline for a planning skill, with minor redundancy between 'When to Use' and 'Good Use Cases' keeping it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong description that clearly states both the capability and a concrete 'Use when' trigger set tied to a distinct notification-operations niche. It is slightly below the top anchor on specificity and trigger-term coverage but otherwise excellent.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete operations (alert routing, deduplication, escalation, inbox collapse) plus specific surfaces (GitHub, Linear, desktop alerts, hooks), with only minor gaps versus the comprehensive-action anchor.	4 / 5
Completeness	It explicitly answers both what ('Operate notifications as one ECC-native workflow across...') and when ('Use when the real problem is alert routing, deduplication, escalation, or inbox collapse') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when' clause surfaces natural phrases a user would say (alert routing, deduplication, escalation, inbox collapse); a few common variants like 'notification fatigue' or 'too many alerts' are missing, so it stops short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The unified-notification-lane framing and named ECC surfaces carve a clear niche with distinct triggers; overlap with related ops skills is minimal.	5 / 5
	Total	18 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/unified-notifications-ops/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.