AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Court Proceedings Data

skill-taivop-marketplace-court-proceedings-data · by taivop

Query public Estonian court-proceedings and related judicial information from Riigi Teataja court information pages.

No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-taivop-marketplace-court-proceedings-data

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-taivop-marketplace-court-proceedings-data)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Court Proceedings Data? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Estonia Court Proceedings Data

Use when

  • You need publicly listed court proceedings information.
  • You need searchable judicial procedure records for legal-operational analysis.

Avoid when

  • You need sealed/non-public case files.

Inputs

  • Court/proceeding filters, date ranges, case keywords.

Outputs

  • Proceedings extract with case metadata and links.

Primary endpoints

  • Proceedings listing: https://www.riigiteataja.ee/kohtulahendid/koik_menetlused.html
  • Court session search: https://www.riigiteataja.ee/kohtuteave/kohtuistungid_otsing.html

Workflow

  1. Use proceedings/session search pages for scope.
  2. Extract case references, dates, and court identifiers.
  3. Normalize case metadata for downstream analysis.
  4. Return case/proceedings table with source links.

Human setup (when needed)

  • If anti-bot/UI controls block direct extraction, guide user through manual query and ask them to share resulting URLs.

Quality checks

  • Do not infer legal outcomes unless explicitly listed.
  • Keep sensitive fields strictly within what is publicly exposed.

Access reality

  • Public access type: Public webpage/document extraction.
  • Verification run: 2026-02-24.
  • https://www.riigiteataja.ee/kohtulahendid/koik_menetlused.html (HTTP 200, text/html;charset=utf-8, file links detected: 0)
  • https://www.riigiteataja.ee/kohtuteave/kohtuistungid_otsing.html (HTTP 200, text/html;charset=utf-8, file links detected: 0)

Request contract

  • Use the listed primary endpoints as authoritative entry points.
  • If API/query parameters are only visible in-browser, preserve exact request URL, params, and headers in output metadata.
  • If endpoint is UI-only, document click path and extraction method used.

Output schema expectations

  • Keep at least: source URL, retrieval timestamp, publication/update date (if available), title/record label, and extracted governance-relevant fields.
  • Preserve original field names when present in downloadable/API output.

Limits and caveats

  • Confirm whether data is open-download, UI-only, or authenticated before claiming full access.
  • Separate narrative/guidance text from measurable records.

Verification hooks

  • Validate endpoint reachability and content type before extraction.
  • Validate that each extracted claim is linked to a concrete source URL.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.