CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-cloudwatch-investigation

Reusable investigation patterns for AWS CloudWatch: Logs Insights query templates, alarm-to-deployment correlation, blast-radius narrowing decision tree, and PromQL-style metric query patterns for structured incident triage.

Quality

76%

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 ./skills/aws-cloudwatch-investigation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 dense, highly actionable investigation playbook: real Logs Insights, CloudTrail, and metric-math queries with useful gotchas and a clear blast-radius decision procedure. Main weaknesses are the absence of execution commands, no explicit verification checkpoints before drawing conclusions, and a monolithic single-file structure that inlines what could be progressive-disclosure reference material.

Suggestions

Add the concrete commands to execute each artifact (e.g., `aws logs start-query --log-group-name ... --query-string ...`, `cloudtrail query ...` for CloudTrail Lake) so the queries are runnable end-to-end, not just well-formed.

Insert an explicit verification step in Patterns 2 and 5 (e.g., re-check the correlation against the previous healthy deployment window, or confirm the timeline ordering before naming a root event) so conclusions are checkpointed.

Split the query-template library (Pattern 1 and Pattern 4) into a references/ file and keep SKILL.md as a lean overview that indexes the patterns, enabling progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dominated by directly usable artifacts (Logs Insights queries, CloudTrail Lake SQL, MetricDataQueries YAML) with almost no explanation of concepts Claude already knows; e.g., 'CloudWatch metric timestamps are end-of-period' is non-obvious operational knowledge, not padding. Minor trimmable spots remain — the intro line restates the frontmatter description and the ASCII blast-radius tree ('START | v [1] ACCOUNT...') could be a compact if/then list — so it is efficient with minor instances of over-explanation rather than lean throughout.

4 / 5

Actionability

Nearly every pattern ships copy-paste-ready queries with concrete field names and functions ('fields @timestamp, @duration, operation | filter ispresent(@duration) | stats avg(@duration) ... pct(@duration, 99) as p99Ms', 'Expression: "errors / invocations * 100"'). Minor gaps keep it below 5: no CLI/API invocation commands (e.g., `aws logs start-query`), and placeholders like '<event-data-store-id>' and 'Dimensions: [{Name: FunctionName, Value: TARGET}]' are not shown being filled.

4 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced ('1. Get alarm transition time... 2. Query CloudTrail... 3. Correlation criteria... 4. Strengthening the correlation') and the blast-radius tree gives if/then branches at each level, with correlation criteria acting as checkpoints. It falls short of 5 because no step explicitly validates findings before concluding (e.g., confirming a correlation against a control window is implied, not instructed), though as a read-only investigation skill it avoids the destructive/batch validation cap.

4 / 5

Progressive Disclosure

This is a single-file skill with no references/, scripts/, or assets/ directories; everything is inline in ~330 lines. Sections are clearly headed ('## Pattern 1: Logs Insights Query Templates' through 'Pattern 5'), but the full query-template library is inlined in SKILL.md rather than split into a references file with a lean overview — matching 'some structure but... content that should be separate is inline'. It is not a 2 because nothing is buried and navigation is easy; not a 4+ because the pattern catalog is exactly the 'detailed material' the rubric expects in separate files.

3 / 5

Total

15

/

20

Passed

Description

70%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 specific, well-scoped description that names four concrete capabilities in a distinctive CloudWatch incident-triage niche. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and leaves activation conditions only weakly implied by 'for structured incident triage'.

Suggestions

Append an explicit trigger clause, e.g., 'Use when investigating a CloudWatch alarm, spike in AWS errors or latency, or a production incident involving Lambda, ECS, or API Gateway.'

Add natural trigger synonyms users would actually say — 'troubleshooting', 'CloudWatch alarm fired', 'production incident', 'root cause' — and reconsider 'PromQL-style', which CloudWatch users rarely say.

Mention the incident timeline reconstruction capability so the description covers all five patterns in the body.

DimensionReasoningScore

Specificity

The description lists several specific concrete capabilities: 'Logs Insights query templates', 'alarm-to-deployment correlation', 'blast-radius narrowing decision tree', and 'PromQL-style metric query patterns'. It stops short of 5 because these are named patterns rather than comprehensive action coverage — the body's incident-timeline reconstruction capability is unmentioned, and actions are stated as artifact names, not outcomes.

4 / 5

Completeness

The 'what' is clear (four named investigation pattern families for CloudWatch), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'for structured incident triage' only weakly implies when to invoke it. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3 even with a clear 'what'.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'AWS CloudWatch', 'Logs Insights', 'alarm', 'incident triage' — phrases a user would plausibly say during an AWS incident. A few natural terms are missing (e.g., 'troubleshooting', 'metrics', 'production incident', 'root cause'), and 'PromQL-style' is jargon CloudWatch users rarely say, so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche — AWS CloudWatch incident investigation combining logs, alarms, metrics, and deploy correlation — with distinct trigger terms; minimal overlap risk with generic AWS, logging, or alerting skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

github/awesome-copilot

Path

skills/aws-cloudwatch-investigation/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.