Supernote Cloud

This skill appears to implement a reasonable Supernote Private Cloud client, but there are two key issues to consider before installing: - Metadata mismatch: The registry entry declares no required environment variables or credentials, but the SKILL.md and scripts require SUPERNOTE_URL, SUPERNOTE_USER, and SUPERNOTE_PASSWORD. Don’t assume the skill is low-privileged — it needs your Supernote credentials and a URL. Only provide those to a trusted self-hosted server. - Token caching and local file access: The CLI caches an auth token in /tmp/.supernote_token (file permission 600) and will read local files you ask it to upload and will fetch arbitrary web URLs to convert into EPUB/PDF. If an attacker or untrusted package controls the configured BASE_URL, your credentials could be sent to that host. Also, the token file in /tmp may be accessible to other local users depending on your system policies. Recommendations: - Verify/inspect the full scripts yourself (you have them). Confirm BASE_URL is a server you control or trust before entering credentials. - Consider creating a dedicated, limited Supernote account for use with this skill rather than using a primary account. - Run the skill in an isolated environment (container or disposable machine) if you’re concerned about token leakage or untrusted network endpoints. - Be cautious when using the article conversion feature: it fetches arbitrary web pages and embedded images (network I/O). If you only need file upload/listing, avoid using article conversion or review the converter's behavior. Confidence: high that the skill is internally inconsistent (metadata vs runtime) and that the scripts will access sensitive credentials and perform network/local-file operations; this warrants a cautious installation approach.