CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-cloudformation-cloudwatch

Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability. Use when creating CloudWatch metrics, alarms, dashboards, log groups, log subscriptions, anomaly detection, synthesized canaries, Application Signals, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references, and CloudWatch best practices for monitoring production infrastructure.

70

Quality

88%

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

The canonical home for this skill is giuseppe-trisciuoglio/developer-kit

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced workflow with strong validation feedback loops and clear references to four bundle files. The main weaknesses are duplicated best-practice/constraint content inflating the body and two bundle files (examples.md, reference.md) that exist but are not surfaced in the body.

Suggestions

Consolidate the overlapping 'Best Practices' and 'Constraints and Warnings' subsections (Monitoring Strategy, Log Management, Alarm Configuration) to remove duplicated bullets and tighten the body.

Add links to the existing references/examples.md and references/reference.md from the body's References section so all bundle files are navigable.

Move the large inlined Examples section into references/examples.md, keeping only one representative snippet inline and pointing to the file for the rest.

DimensionReasoningScore

Conciseness

The body is mostly efficient and executable, but the 'Best Practices' and 'Constraints and Warnings' sections overlap substantially—'Monitoring Strategy', 'Log Management', and 'Alarm Configuration' repeat points already in Best Practices—adding padding that could be trimmed.

3 / 5

Actionability

Every step ships copy-paste-ready YAML and bash (alarms, dashboards, log groups, metric filters, composite alarms, validate-template, create-stack, describe-alarms, set-alarm-state), covering the common cases fully.

5 / 5

Workflow Clarity

The 10-step sequence is explicit with a validation checkpoint (validate-template) and a verify loop (wait stack-create-complete, describe-alarms, get-dashboard, set-alarm-state test), satisfying the destructive/batch feedback-loop requirement.

5 / 5

Progressive Disclosure

Structure is good with a well-signaled one-level-deep References section linking alarms.md, dashboards.md, logs.md, and constraints.md, but the inlined Examples and Constraints sections partly belong in reference files, and the bundled examples.md and reference.md are never linked from the body.

4 / 5

Total

17

/

20

Passed

Description

92%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, third-person description that comprehensively covers capabilities and provides an explicit 'Use when' trigger clause with concrete CloudWatch/CloudFormation terms. Minor room to add colloquial synonyms, but it cleanly satisfies the top anchors for specificity, completeness, and distinctiveness.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions—'metrics, alarms, dashboards, log groups, log subscriptions, anomaly detection, synthesized canaries, Application Signals' plus 'Parameters, Outputs, Mappings, Conditions, cross-stack references'—giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It explicitly answers both what ('Provides AWS CloudFormation patterns for CloudWatch monitoring...') and when ('Use when creating CloudWatch metrics, alarms, dashboards...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It enumerates strong natural terms users say ('CloudWatch metrics, alarms, dashboards, log groups, anomaly detection, canaries'), but the triggers lean toward enumerated AWS resource types rather than colloquial synonyms; coverage is good but not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The CloudFormation-plus-CloudWatch niche is clearly scoped with distinct triggers ('synthesized canaries', 'Application Signals', 'cross-stack references'), making conflict with other skills minimal.

5 / 5

Total

19

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

giuseppe-trisciuoglio/developer-kit

Path

plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-cloudwatch/SKILL.md

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.