Aria2 Downloader

v1.0.2

使用 aria2 下载磁力链接、种子、HTTP 文件。下载完成后自动转存到 115 网盘并删除本地文件。当用户发送磁力链接(magnet:)、种子文件(.torrent)、或要求下载文件时触发此 skill。

2· 1.6k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The description promises downloading and then automatically transferring to 115网盘 and deleting local files, but the SKILL.md contains only aria2 RPC curl examples and a note that a host-side 'on-download-complete' hook should perform transfer. No instructions, endpoints, or required credentials for 115 are provided. That discrepancy means the skill's declared purpose (automatic transfer to 115 + cleanup) is not implemented in the instructions.
Instruction Scope
Runtime instructions are limited to calling aria2's local JSON-RPC (localhost:6800) and showing how to add torrents/magnets and query status. This scope is appropriate for an aria2 controller, and there are no external network endpoints in the examples. However the instructions include a repeated literal token string ("token:e603c18b871468e81ec2b2458d3356e5") in RPC payloads and reference using an RPC secret without declaring the env var name. The doc also instructs base64-encoding a local .torrent path (which implies reading local files) — that is expected for torrent uploads but should be explicit about file access and permissions.
Install Mechanism
This is an instruction-only skill with no install steps or code files, so nothing is written to disk by the skill itself. That minimizes install-time risk.
!
Credentials
The skill metadata declares no required environment variables or credentials, yet the SKILL.md references an RPC secret and shows a concrete token embedded in every example. Additionally, the described automatic upload to 115网盘 would require 115 credentials (API token/login) but none are requested or documented. The mismatch between declared required credentials (none) and the token/115 workflow in the doc is disproportionate and unclear.
Persistence & Privilege
The skill is not always-enabled and uses default autonomous invocation settings. It does not request to persist or modify other skills or global agent settings. No elevated platform privileges are requested.
What to consider before installing
What to consider before installing: - The skill's description promises automatic upload to 115网盘 and deletion of local files, but the instructions only show aria2 JSON-RPC calls and say you must provide a host-side on-download-complete script. Installing this skill alone will not perform the 115 upload — you must supply and secure that script and any 115 credentials yourself. - The SKILL.md contains a repeated literal RPC token string (token:e603c18b871468e81ec2b2458d3356e5) in examples but the skill metadata does not declare any required env vars. Treat that token as sensitive: verify whether it's a placeholder or a real secret before using it. Do not expose real credentials in skill text. - The skill's runtime actions (curl to localhost, reading/encoding a local .torrent) require access to local files/aria2 RPC. Only enable this skill if your aria2 instance is intentionally exposed on localhost, protected by a strong secret, and you trust the environment that will run on-download hooks. - If you plan to enable automatic upload to 115, require and configure explicit environment variables for 115 credentials (do not hard-code them in SKILL.md), and review the host-side script that performs the transfer — ensure it safely handles credentials and removes files only after successful transfer. - Legal/privacy: downloading magnet/torrent content can involve copyrighted content. Ensure users and the host comply with local law and acceptable use policies. - Because the metadata and instructions are inconsistent, ask the maintainer (or inspect the host-side scripts) for clarification about: 1) whether the embedded token is a real secret or placeholder, 2) exactly how 115 uploads are implemented and where to store credentials, and 3) expected file paths/permissions for the on-download hook. Given these inconsistencies, treat this skill as suspicious until the missing pieces (115 upload flow and credential handling) are clarified and secrets are removed from documentation.

Like a lobster shell, security has layers — review code before you run it.

latestvk978nksrvcryp9deeytx17vs4n80nnma

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments