CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

monitoring

System health monitoring, alerts, and error tracking

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/monitoring/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 executable, copy-paste-ready code and commands, and is reasonably token-efficient. Its weaknesses are the absence of any sequenced workflow with validation checkpoints and the lack of progressive disclosure — the entire API reference is inlined with no separate reference files.

Suggestions

Move the bulk TypeScript API reference into a separate file (e.g. references/API.md) and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure.

Add validation/verification steps for mutating operations (e.g. after addAlertTarget, list targets to confirm; after configure, run a health check to verify thresholds applied).

Collapse the duplicated configuration material (chat-command thresholds vs. the TypeScript configure() block) into a single canonical section to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly lean API surface with terse inline comments rather than concept explanations Claude already knows; minor redundancy (configuration shown twice) and a few obvious comments keep it just below 5.

4 / 5

Actionability

Copy-paste-ready TypeScript snippets and concrete chat commands cover the common cases (start/stop, health checks, alert targets, event handlers, manual alerts) with real signatures and values.

5 / 5

Workflow Clarity

Content is organized by feature rather than as a sequenced workflow, and there are no validation checkpoints or feedback loops (e.g. verify a target was added, confirm a threshold took effect) despite config/alert-target mutations.

3 / 5

Progressive Disclosure

No bundle files exist and the full API reference is inlined in SKILL.md; section headers provide structure, but bulk reference material that belongs in a separate file is kept inline with no one-level-deep references.

3 / 5

Total

15

/

20

Passed

Description

50%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 states a clear domain and a couple of concrete actions but omits any explicit 'when to use' trigger guidance, capping completeness at 3. Trigger terms are relevant but lack synonyms and natural variations.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when monitoring system health, configuring alerts, or tracking LLM provider downtime.'

Expand the action list to surface distinctive capabilities (health checks, thresholds, provider status) that separate this skill from generic logging/debugging skills.

Include natural synonyms users say ('uptime', 'downtime', 'metrics', 'observability') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('System health monitoring') and 1-2 concrete actions ('alerts', 'error tracking'), but coverage is not comprehensive — no mention of health checks, thresholds, or provider status that the body actually supports.

3 / 5

Completeness

There is a clear 'what' but no 'Use when...' clause or equivalent trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

'monitoring', 'alerts', and 'error tracking' are relevant natural terms, but common variations/synonyms a user might say (uptime, downtime, observability, health checks, metrics) are missing.

3 / 5

Distinctiveness Conflict Risk

'System health monitoring, alerts, and error tracking' is somewhat specific to an observability niche but could still overlap with general logging, debugging, or error-handling skills.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/monitoring/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill