Ielts Review Upload
ReviewAudited by ClawScan on May 12, 2026.
Overview
The skill mostly matches its upload-dashboard purpose, but it sends local identity information and uses a hardcoded shared API key in dashboard links, so users should review the data and access boundaries before using it.
Before installing, make sure you are comfortable uploading the selected IELTS review file to tuyaya.online. Do not upload private unrelated files, avoid sharing the generated dashboard URL, and prefer a version that does not send your raw system username or expose a shared API key in the link.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The selected review file will be sent to the remote service.
The skill directs the agent to run a local script on a user-provided file and upload that content to an external backend. This is central to the stated purpose, but it is still a meaningful data-transfer action.
运行上传脚本: ```bash bash scripts/sync-review.sh <path-to-data.json> ``` **脚本功能**:... 上传数据到私有后端
Confirm the file path and contents with the user before running the upload.
A copied or shared dashboard link may include the service key, and the artifact does not make clear what that key can access or how it can be revoked.
The script embeds a default API key, uses it for backend authentication, and prints it in the dashboard URL. This makes the access boundary depend on a shared, exposed credential rather than a clearly scoped per-user secret.
API_KEY="${IELTS_API_KEY:-ielts_8b0832b3cfd38884e44ab26ee68acaeed294623ef8da9b201871a7768b072606}"
...
-H "x-api-key: $API_KEY"
...
echo " $API_BASE/web/?user=$USER_ID&key=$API_KEY"Use per-user scoped tokens or server-side sessions, avoid placing API keys in URLs, and declare/document credential scope and revocation behavior.
The remote service can receive study data together with a local username that may identify the user or their device account.
The backend request includes the review payload plus a stable host/user-derived identifier and the raw local OS username. The documentation discusses an anonymous hashed ID, but the raw username transmission and data retention boundaries are not clearly explained.
RAW_ID="$(hostname)-$(whoami)"
...
USER_NAME="${IELTS_USER_NAME:-$(whoami)}"
...
-H "x-user-id: $USER_ID" \
-H "x-user-name: $USER_NAME" \
-d "$PAYLOAD"Clearly disclose transmitted identity fields, avoid sending the raw OS username by default, ask for consent before upload, and document retention/deletion controls.
A future or changed remote script could run different upload logic than the packaged version.
The reviewed package includes the script, but the instructions provide an unpinned raw GitHub download fallback. If used, the executed code could differ from the reviewed artifact.
如果脚本不存在: 从当前 Skill 目录复制,或者从 GitHub 下载: ```bash curl -o scripts/sync-review.sh https://raw.githubusercontent.com/dengjiawei1226/ielts-reading-review/main/scripts/sync-review.sh chmod +x scripts/sync-review.sh ```
Prefer the included reviewed script, or pin the download to a specific commit and verify a checksum before execution.
