Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Solo Leveling — Life RPG

v1.0.0

Solo Leveling — a life RPG skill that turns real-world habits into an addictive progression system. Inspired by the manhwa Solo Leveling, this skill features...

0· 681·1 current·1 all-time
byAnmol moses@anmolmoses
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill claims to be a local 'life RPG' habit tracker, which plausibly might send notifications. However, bundled scripts implement Twilio voice calls and ElevenLabs TTS (scripts/twilio_call.py and scripts/elevenlabs_call.py) and attempt to upload audio to transfer.sh. The registry metadata declares no required credentials or services. Either the skill should explicitly state it will make phone calls and require Twilio/ElevenLabs credentials, or these capabilities are unexpected and disproportionate to the stated description.
!
Instruction Scope
SKILL.md instructs the agent to run onboarding, write references/config.json, run scripts/player_data.py, and 'set up cron jobs'. The README mentions verification via Telegram timestamps, but there is no Telegram integration code. The runtime instructions therefore direct file writes (config and data files), cron modification (persistence), and execution of scripts that will perform network calls to external services — actions that go beyond mere local habit tracking and are not fully documented in the skill metadata.
Install Mechanism
There is no install spec (instruction-only), which is lower risk for supply-chain installs. However, the included scripts perform runtime network interactions: ElevenLabs API calls, Twilio calls, and uploading audio to transfer.sh as a fallback. Although nothing is downloaded at install time, the runtime behavior includes contacting third-party hosts and writing caches under ~/.openclaw/workspace/solo-leveling-data, which the user should be aware of.
!
Credentials
Registry requirements list zero env vars/credentials, but scripts expect a twilio-config.json (account_sid, auth_token, twilio_number, target_number) and ElevenLabs API keys. The scripts also honor environment variables like TWILIO_CONFIG and SOLO_DATA_DIR. Requesting sensitive API keys and phone credentials is plausible for voice notifications, but the skill fails to declare them and does not document where credentials will be stored (default path is an unencrypted JSON under the user workspace). This is disproportionate and opaque.
!
Persistence & Privilege
The skill is not 'always:true', but SKILL.md instructs setting up cron jobs for recurring notifications — that implies persistent, scheduled execution and potential modification of the user's crontab. The scripts also create files and caches under ~/.openclaw/workspace/solo-leveling-data. Combined with outbound calls and credential use, this persistent behavior increases risk and should be made explicit and auditable.
What to consider before installing
Before installing or enabling this skill, consider the following: - The skill's package contains working code to place phone calls via Twilio and generate TTS via ElevenLabs. To do that it expects Twilio credentials (account SID, auth token, from/to numbers) and an ElevenLabs API key — but the registry metadata claims no credentials are required. Ask the author to explicitly list required secrets and explain where they are stored. - The ElevenLabs/Twilio code will send data to external services and may upload audio to a public file host (transfer.sh) as a fallback. Audio and TTS text could include private content. If you use this, do not store API keys or personal phone numbers in plaintext files in shared locations. - SKILL.md suggests setting up cron jobs. Cron changes give the skill scheduled/persistent behavior. Only allow that if you understand and approve the exact cron entries; prefer manual scheduling or a sandboxed environment first. - Twilio calls can incur real charges and place calls to any configured 'target_number'. Verify the configured number(s) in twilio-config.json before running, and consider restricting network access or using test credentials. - The skill references Telegram-based verification in its rules but provides no Telegram integration code — ask for clarification on how verification is meant to work and whether any additional integrations are required. What would make this clearly safe: the author updates the registry metadata to list required credentials (Twilio & ElevenLabs), documents where credentials/config are stored and why, removes or documents the use of public upload fallback (transfer.sh), provides an option to disable external calls, and supplies explicit, reviewable cron setup commands. If you cannot get those clarifications, run the skill in a restricted sandbox, do not provide real API keys or phone numbers, or avoid installing it.

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

latestvk9710hrw3456hee857ryw6myb1817rjj

License

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

Comments