SKILLEMALL.ai

BF monte-carlo-analyze-root-cause

Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 3 795 tokens Open the sourcegithub.com analyzed 2 d ago

Investigate data incidents and find root causes using Monte Carlo's observability data.

As a process F 50/100 · Will not run — References files that are not bundled: references/<type>-investigation.md, references/data-exploration.md, references/intake-no-incident.md

AnalyzerGitHubGoogle CloudAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
F
50/100
Will not run
References files that are not bundled: references/<type>-investigation.md, references/data-exploration.md, references/intake-no-incident.md
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: monte-carlo-analyze-root-cause (sickn33/agentic-awesome-skills)

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/<type>-investigation.md
  • warning missing-ref reference to a missing file: references/data-exploration.md
  • warning missing-ref reference to a missing file: references/intake-no-incident.md
  • warning missing-ref reference to a missing file: references/common-root-causes.md
  • warning missing-ref reference to a missing file: references/freshness-investigation.md
  • warning missing-ref reference to a missing file: references/volume-investigation.md
  • warning missing-ref reference to a missing file: references/schema-investigation.md
  • warning missing-ref reference to a missing file: references/etl-failure-investigation.md
  • warning missing-ref reference to a missing file: references/query-change-investigation.md
  • warning missing-ref reference to a missing file: references/field-anomaly-investigation.md
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: references/<type>-investigation.md, references/data-exploration.md, references/intake-no-incident.md
  • 0Tools and files. 10 referenced file(s) missing: references/<type>-investigation.md, references/data-exploration.md, references/intake-no-incident.md
  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 9 branches
  • 85Steps. 64 steps, 3 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3795 tokens
  • 100Running it twice. Mutating operations check current state
  • 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 217: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 64 items
  • +4Has examples (1 code blocks)
  • +1License stated

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