E Notary
Use RIK e-notary service context for notarial workflow guidance and structured extraction of publicly accessible process information.
Install
$ agentstack add skill-taivop-marketplace-e-notary ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-taivop-marketplace-e-notary) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
E-Notary
Use when
- You need official notarial e-service process context.
- You need structured extraction of public e-notary workflow outputs.
Avoid when
- You need confidential notarial records.
Inputs
- Service type, procedural stage, and period.
Outputs
- Structured e-notary process/output references.
Primary endpoints
- Chamber of Notaries portal: https://notar.ee
- E-notary service info: https://www.rik.ee/en/other-services/e-notary
Workflow
- Identify relevant e-notary service route.
- Extract process requirements and available outputs.
- Normalize service/stage terminology.
- Return structured process map and references.
Human setup (when needed)
- If interaction requires authenticated service usage, guide user through required steps and continue from provided results.
Quality checks
- Separate process guidance from official output artifacts.
- Preserve legal references and fees where listed.
Access reality
- Public access type: Public webpage/document extraction.
- Verification run: 2026-02-24.
- https://www.rik.ee/en/other-services/e-notary (HTTP 200, text/html;, 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.
- Author: taivop
- Source: taivop/marketplace
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.