CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-monitor

This skill should be used when the user says "set up monitoring", "arn infra monitor", "infra monitor", "configure monitoring", "set up observability", "add logging", "configure alerting", "set up alerts", "infrastructure monitoring", "add metrics", "set up cloudwatch", "configure grafana", "observability setup", "logging setup", "alerting setup", "health checks", "monitor infrastructure", "arn-infra-monitor", "set up cloud monitoring", "configure notifications", "prometheus", "datadog", "new relic", "sentry", or wants to set up logging, metrics collection, and alerting for their deployed infrastructure.

66

Quality

80%

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 ./plugins/arn-infra/skills/arn-infra-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, highly actionable monitoring skill: clear sequenced workflow with validation gates, concrete tables and dispatch conventions, and well-signaled one-level references. The main improvement lever is conciseness, since some provider mapping and log-level exposition repeats what Claude already knows.

Suggestions

Move the per-provider native-stack mapping (AWS/GCP/Azure/Kubernetes/PaaS/Multi-cloud) and the log-level/retention rationale into the observability-stack-guide reference, leaving the body with the decision points.

Trim exposition of standard concepts (e.g., 'JSON for machine parsing', retention 'Cost optimization'/'Debugging window') to bare values.

DimensionReasoningScore

Conciseness

The body is largely efficient and action-oriented, but several sections restate concepts Claude already knows (standard log levels, retention rationale like 'Cost optimization', and per-provider native-tool mappings) that could be tightened or pushed to references.

2 / 3

Actionability

It provides concrete, executable guidance: specific Glob patterns, exact threshold tables, a templated IaC context block, named agent dispatch with a model path, and AskUserQuestion option sets, all copy-paste ready.

3 / 3

Workflow Clarity

The 8-step workflow is explicitly sequenced with validation checkpoints (config-presence checks that stop, detected-vs-fresh branching, approval-before-write, and a dedicated Error Handling section with fallback and retry loops).

3 / 3

Progressive Disclosure

SKILL.md is an overview that signals two real one-level-deep references (observability-stack-guide.md, alerting-patterns.md, both present in references/) via blockquote pointers, keeping the body focused with no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 has strong trigger-term coverage and clear what/when completeness, anchored by the distinctive skill name. Its main weakness is specificity: the capability set is described in one broad bundled phrase rather than enumerated concrete actions.

Suggestions

Enumerate concrete capabilities (e.g., 'generate monitoring IaC, configure health-check alerts, recommend an observability stack per cloud provider') rather than collapsing them into 'set up logging, metrics collection, and alerting'.

Lead with the third-person capability statement before the trigger list so the action description is not buried inside the 'when' clause.

DimensionReasoningScore

Specificity

It names a domain (logging, metrics collection, alerting for infrastructure) but the specific actions are limited to a single broad phrase ('set up logging, metrics collection, and alerting'); it is not a comprehensive list of distinct concrete capabilities.

2 / 3

Completeness

It states both what (logging, metrics collection, alerting) and when via an explicit 'Use when' trigger ("This skill should be used when the user says..."), satisfying both halves of the rubric.

3 / 3

Trigger Term Quality

It covers a wide spread of natural user phrasings including 'set up monitoring', 'add logging', 'configure alerting', 'health checks', 'prometheus', 'datadog', 'sentry', and the skill name, matching terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The trigger set is tightly scoped to infrastructure observability setup and includes the unique skill name 'arn-infra-monitor', making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation15 / 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
AppsVortex/arness
Reviewed

Table of Contents

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.