AC court-practice
Russian court practice (судебная практика РФ) via reputation.ru — find cases, get a synthesized analysis report, or fetch a document's full text across arbitration (арбитраж), general jurisdiction (СОЮ), and the Supreme Court (ВС РФ). Use for «найди практику по…», «как суды решают…», «обзор практики», «полный текст решения». Paid service — needs REPUTATION_API_KEY; if tools are missing or you get 401/403, do the Setup section first.
Russian court practice (судебная практика РФ) via reputation.ru — find cases, get a synthesized analysis report, or fetch a document's full text across…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "requires" - note
frontmatter-keyunknown frontmatter key "primaryEnv"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (court-practice) differs from the folder (reputation-courts-practice)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 30 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 3961 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +5Description quotes 4 example trigger phrases
- +3Description length 436: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (4 code blocks)
- +1License stated
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.