SKILLEMALL.ai

BD Oracle DB

Write Oracle SQL and PL/SQL with proper syntax, hints, and performance patterns.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 884 tokens Open the sourcegithub.com analyzed 2 d ago

Write Oracle SQL and PL/SQL with proper syntax, hints, and performance patterns.

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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.
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 name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 46/100

  • 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
  • 30Running it twice. 7 mutating operations with no state check
  • 40Consistency. Frontmatter name (Oracle DB) differs from the folder (oracle-db)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 48 steps
  • 100Execution cost. Instruction body is 884 tokens
  • 100Progress reporting. Reports progress
  • low 12 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 80: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 48 items

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