CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-investigation

Investigates what is happening in an AWS account from evidence already recorded there. Not for capturing new data from running code (snapshots of function arguments on a live service, Dynamic Instrumentation), questions answered from the CloudWatch Omni context graph or Application Signals service map, or building or changing infrastructure. Covers reading deployment records instead of the newest stored version (completed AppConfig deployments, the version an alias points to, a stack's current template), following a request through every service's own logs (exact per-layer fields, unique failed requests in an alarm's breach window, failure boundary per event), and answering questions from the account's data (exact counts and breakdowns, coverage of the requested range, exact filters and joins, the rule behind failed or unmatched records, verbatim values). Use to triage an alarm, error spike or failed request, trace a request across services, or count, break down, extract or join records.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, well-structured investigative skill: an explicit three-phase workflow (route → investigate under rules → validate against a closing checklist) with strong progressive disclosure into four genuine reference files. The two dimensions at 4 reflect minor trimmable redundancy between the rules and the closing checklist, and the absence of any worked example in the body itself.

Suggestions

Trim the overlap between 'Rules for every investigation' and the closing checklist: checklist items 6–7 restate the reference table rows and rule 2, so cutting the checklist to non-overlapping verification items would make every token earn its place.

Add one compact worked example in the body — e.g. a filled-in provenance note line such as `alias prod points to version 12 <- lambda get-alias output, 2026-11-08` — to make the evidence-tracking rule copy-paste concrete without expanding the reference files.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with zero explanation of concepts Claude already knows — every rule adds domain-specific discipline (e.g. "Keep a short provenance note per claim (`claim <- artifact, record or query`)"), and details like "airport-code regions such as PDX = us-west-2, IAD = us-east-1" are genuinely non-obvious. It is not a 5 because closing-checklist items 6–7 restate the routing-table rows and rule 2 ("claims about live configuration come from the deployed artifact, not the latest stored version"), a minor duplication that could be trimmed.

4 / 5

Actionability

As an instruction-only skill it gives concrete, copy-ready guidance: the provenance notation "`claim <- artifact, record or query`", the tactic "list resources, log groups and data stores in the likely regions and search for the identifiers in the request", and the directive "report unique entities separately from raw records". It is not a 5 because the body contains no worked example or sample command — the command-level specifics are delegated to the reference files — leaving minor gaps against the 'specific examples cover the common cases' anchor.

4 / 5

Workflow Clarity

The sequence is explicit and phased: pick the reference first ("Read the reference that matches the question before you start"), apply the five rules during the investigation, then run a dedicated 10-item closing checklist ("Before submitting your analysis") that includes a re-check feedback loop ("reread your conclusion against each piece of evidence you collected and removed any statement that contradicts it"). This matches the anchor-5 pattern of clear sequence, explicit validation steps, and a checklist for a complex process; the skill is read-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

The body is a lean overview that routes to four real, verified reference files via a question-type table ("What a deployed system currently does... → references/deployed-artifacts.md"), with all referenced paths present on disk. The references are one level deep — sibling links only, no nested chains — and content is appropriately split between overview and detail, matching the anchor-5 structure of well-signaled navigation.

5 / 5

Total

18

/

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 highly specific, well-scoped description that clearly states both capabilities and use-when triggers, with explicit exclusions that sharply reduce conflict risk. Its only weakness is that natural-term coverage stops short of comprehensive: a few common user phrasings ('root cause', 'debug') are absent amid otherwise dense AWS-specific terminology.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "reading deployment records... (completed AppConfig deployments, the version an alias points to, a stack's current template)", "following a request through every service's own logs", "count, break down, extract or join records" — each instantiated with concrete examples and comprehensively covering its three sub-domains, matching the anchor-5 example's density. It is not a 4 because the coverage goes beyond 'minor gaps': every capability area is paired with specific instances.

5 / 5

Completeness

It explicitly answers 'what' ("Investigates what is happening in an AWS account from evidence already recorded there. Covers reading deployment records... following a request... answering questions from the account's data") and 'when' ("Use to triage an alarm, error spike or failed request, trace a request across services, or count, break down, extract or join records"), plus explicit 'Not for...' exclusions — mirroring the anchor-5 example's structure of capabilities followed by concrete trigger phrases. Not a 4 because the 'when' clause is already fully explicit with concrete triggers, not merely 'could be more specific'.

5 / 5

Trigger Term Quality

The closing clause "Use to triage an alarm, error spike or failed request, trace a request across services, or count, break down, extract or join records" contains natural phrases users would say, giving good keyword coverage. It is not a 5 because common natural synonyms such as 'root cause', 'debug', or service-log phrasings (e.g. CloudWatch Logs) are missing, and the middle of the description leans on internal jargon ('CloudWatch Omni context graph', 'Dynamic Instrumentation') that serves scoping rather than triggering.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — investigating an AWS account from recorded evidence — and explicitly fences off adjacent skills ("Not for capturing new data from running code... questions answered from the CloudWatch Omni context graph or Application Signals service map, or building or changing infrastructure"), minimizing overlap with instrumentation, observability, or infrastructure skills. Not a 4: the conflict boundaries are explicit rather than leaving 'minor overlap risk'.

5 / 5

Total

19

/

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

aws/agent-toolkit-for-aws

Path

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