SKILLEMALL.ai

BF aws-observability

Builds, configures, debugs, and optimizes AWS observability with CloudWatch (Log Insights, Metrics, Alarms, Dashboards, EMF), X-Ray, CloudTrail, and ADOT (AWS Distro for OpenTelemetry), AND enables/onboards services to Application Signals using ADOT auto-instrumentation SDKs. Covers Log Insights queries, alarms (metric, composite, anomaly), dashboards, custom metrics/EMF, X-Ray tracing and sampling, ADOT collector config, CloudTrail auditing, and end-to-end Application Signals enablement via ADOT SDKs (CloudWatch Observability EKS add-on, CloudWatch Agent IAM, OTLP endpoints, ServiceEvents, Dynamic Instrumentation), breakpoint and snapshot in Dynamic Instrumentation, live data capture in running service, debug without redeploying. Applies to CloudWatch, alarms, dashboards, EMF, X-Ray, traces, CloudTrail, ADOT, monitoring, synthetics/canaries, OR enabling/onboarding/instrumenting a service for Application Signals. Not for app logging or security threat detection.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 1 362 tokens Open the sourceclawhub.ai analyzed 2 d ago

Builds, configures, debugs, and optimizes AWS observability with CloudWatch (Log Insights, Metrics, Alarms, Dashboards, EMF), X-Ray, CloudTrail, and ADOT (AWS…

As a process F 23/100 · Will not run — References files that are not bundled: references/application-signals-onboarding.md, references/application-signals-cicd-metadata.md, references/appsignals-guides/eks-python.md

GeneratorAWSInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
54
Run on models
none yet
Process rating
F
23/100
Will not run
References files that are not bundled: references/application-signals-onboarding.md, references/application-signals-cicd-metadata.md, references/appsignals-guides/eks-python.md
Tools and files w 18
0
Steps w 15
0
Result and completion w 14
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/application-signals-onboarding.md
  • warning missing-ref reference to a missing file: references/application-signals-cicd-metadata.md
  • warning missing-ref reference to a missing file: references/appsignals-guides/eks-python.md
  • warning missing-ref reference to a missing file: references/log-insights.md
  • warning missing-ref reference to a missing file: references/alarms.md
  • warning missing-ref reference to a missing file: references/metrics.md
  • warning missing-ref reference to a missing file: references/tracing.md
  • warning missing-ref reference to a missing file: references/dashboards.md
  • warning missing-ref reference to a missing file: references/troubleshooting.md
  • warning missing-ref reference to a missing file: references/synthetics.md
  • warning missing-ref reference to a missing file: references/cloudtrail.md
  • warning missing-ref reference to a missing file: assets/alarm-template.ts
  • warning missing-ref reference to a missing file: assets/otel-config.yaml
  • warning missing-ref reference to a missing file: references/dynamic-instrumentation.md
  • warning missing-ref reference to a missing file: references/appsignals-guides/<platform>-<language>.md
  • warning missing-ref reference to a missing file: references/appsignals-guides/
  • warning missing-ref reference to a missing file: scripts/di_instrumentation.py
  • warning missing-ref reference to a missing file: scripts/di_snapshots.py

Process rating: all ten parameters 23/100

Will not run. References files that are not bundled: references/application-signals-onboarding.md, references/application-signals-cicd-metadata.md, references/appsignals-guides/eks-python.md
  • 0Tools and files. 18 referenced file(s) missing: references/application-signals-onboarding.md, references/application-signals-cicd-metadata.md, references/appsignals-guides/eks-python.md
  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 8 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1362 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Description length 976: 120–800 characters recommended
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +4Structure: 4 headings

Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.