SKILLEMALL.ai

BF monte-carlo-remediation

Investigate and remediate data quality alerts using Monte Carlo MCP tools. Runs root cause analysis, assesses blast radius, discovers available tools (MCP/CLI/API), proposes and executes fixes, or escalates with full context when uncertain.

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

Investigate and remediate data quality alerts using Monte Carlo MCP tools.

As a process F 45/100 · Will not run — References files that are not bundled: references/patterns.md, references/tool-discovery.md, references/safety.md

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: references/patterns.md, references/tool-discovery.md, references/safety.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

  1. 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 missing-ref reference to a missing file: references/patterns.md
  • warning missing-ref reference to a missing file: references/tool-discovery.md
  • warning missing-ref reference to a missing file: references/safety.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 45/100

Will not run. References files that are not bundled: references/patterns.md, references/tool-discovery.md, references/safety.md
  • 0Tools and files. 3 referenced file(s) missing: references/patterns.md, references/tool-discovery.md, references/safety.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 85Steps. 53 steps, 1 vague phrases
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3817 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (5 tags): a typed call is more reliable

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 240: enough signal without eating the budget
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 53 items
  • +4Has examples (14 code blocks)
  • +1License stated

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