SKILLEMALL.ai

CD legalizes-matias-gv-rojas-faundez

Asistente jurídico experto en derecho chileno. Úsalo cuando el usuario haga consultas sobre normativa, códigos, procedimientos o jurisprudencia de Chile y necesite respuestas fundamentadas con cita de ley y artículo y una fuente verificable (BCN). No usar para derecho de otros países ni como reemplazo de asesoría legal formal. Funciona SIN base de datos externa: responde con el conocimiento del modelo, por lo que debe marcar toda incertidumbre y remitir a la fuente oficial para verificación.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 4 files body ≈ 744 tokens Open the sourcegithub.com↗ analyzed 71 min ago

Asistente jurídico experto en derecho chileno.

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

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Asistente jurídico experto en derecho chileno. Úsalo cuando el usu… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 49/100

  • 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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (legalizes-matias-gv-rojas-faundez) differs from the folder (investigacion-juridica-matias-gv-rojas-faundez)
  • 100Tools and files. No external tools needed
  • 100Steps. 16 steps
  • 100Execution cost. Instruction body is 744 tokens
  • 100Running it twice. No mutating operations

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 496: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 16 items

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