Trilium

Use when interacting with a Trilium Notes server via the ETAPI REST API - creating, reading, updating, searching, or deleting notes, branches, attributes, at...

This skill appears to be a straightforward curl-based helper for the Trilium ETAPI, but there are a few practical concerns to consider before installing or letting an agent use it: - Metadata omission: The SKILL.md relies on TRILIUM_URL and TRILIUM_TOKEN (and shows exchanging a password for a token), but the skill metadata declares no required environment variables. Ask the publisher to declare TRILIUM_URL and TRILIUM_TOKEN (and any password usage) explicitly so you can audit and control what credentials are provided. - Destructive operations: Examples include DELETE /notes, POST /notes/{id}/import, and PUT /backup/{name}. Test with a safe, non-production Trilium instance first and prefer read-only operations to confirm behavior. - Local file I/O: The snippets read local files (e.g., --data-binary @body.html) and write outputs (e.g., -o subtree.zip). Ensure the agent has access only to intended files and that scripts run in a controlled directory. - Auth handling: Prefer supplying a pre-generated ETAPI token rather than a password. If you must use a password exchange, verify you are pointing to a trusted TRILIUM_URL and be aware the password is sent to that server. - Autonomous invocation: The skill can be invoked autonomously by the agent (platform default). That is normal, but because the skill can perform destructive actions on your Trilium server, restrict autonomous use or limit credentials to a read-only token for automated workflows where possible. If you plan to use this skill, request that the publisher update the skill metadata to declare the required env vars and document intended safety defaults (e.g., example tokens with limited scope or read-only tokens) so you can make an informed decision.

Type: OpenClaw Skill Name: trilium-etapi Version: 0.0.1 The skill bundle provides documentation and functional curl/jq examples for interacting with the Trilium Notes ETAPI. It covers standard CRUD operations, authentication, and search functionality as described in the official Trilium documentation. No evidence of malicious intent, data exfiltration, or prompt injection was found; the instructions are strictly aligned with the stated purpose of managing a Trilium Notes instance.