Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Ai Shifu Course Creator
v1.0.1Convert raw course material into optimized, runnable MarkdownFlow teaching scripts and deploy them as live courses through a five-phase pipeline covering seg...
⭐ 0· 163·0 current·0 all-time
byClarkHe@heshaofu2
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (convert materials → MarkdownFlow → deploy to AI‑Shifu) aligns with the files and examples (pipeline phases, build/import/publish examples). The included CLI and many docs are coherent with that purpose.
Instruction Scope
Runtime instructions direct the agent to run a local CLI (scripts/shifu-cli.py) for build/import/publish and to perform interactive login flows (ask user for region, phone number, SMS code, or for a browser token). That requires collecting PII/sensitive tokens. The SKILL.md also instructs writing the token to {skillDir}/.env and to always use CLI rather than raw HTTP calls. The skill documentation references environment variables and file paths the agent will read/write (SHIFU_TOKEN, SHIFU_BASE_URL, {skillDir}/.env) even though none are declared as required in the registry metadata — this mismatch is a scope/information gap.
Install Mechanism
There is no install spec (instruction-only behavior) which minimizes surprise installs, but the package includes a sizable script (scripts/shifu-cli.py). The full contents of that script were not provided in the inspected text, so its network endpoints and exact behavior cannot be audited here — review of that file is recommended before running.
Credentials
Top-level metadata lists no required env vars, yet the docs and CLI reference SHIFU_TOKEN, SHIFU_BASE_URL, and storing a token in {skillDir}/.env. The skill expects credentials and user SMS codes (sensitive data) for login flows but does not declare them as required — this is an incoherence and increases the risk of unexpected credential handling or leakage.
Persistence & Privilege
always:false and no OS restrictions. The skill writes/reads credentials to a local `{skillDir}/.env` per docs; retaining a token in its own directory is plausible for a CLI tool but the exact storage mechanics and file permissions should be inspected. The skill does not request global/always-on privileges or indicate it will modify other skills.
What to consider before installing
This skill appears to implement the course-authoring + deployment workflow it advertises, but there are a few red flags to check before installing or running it:
- Inspect scripts/shifu-cli.py (the included CLI) before execution. Verify which network endpoints it talks to, what it sends, and whether it logs or transmits course or user data elsewhere. Do not run it until you confirm endpoints are only the expected AI‑Shifu hosts (app.ai-shifu.cn / app.ai-shifu.com) or other documented URLs.
- The docs reference storing a login token in {skillDir}/.env and using SHIFU_TOKEN / SHIFU_BASE_URL env vars, yet the registry declares no required env vars — treat credential handling as optional but sensitive. Confirm where the token is stored, file permissions, and whether it is encrypted or accessible to other processes/users.
- The login flow asks for phone number and SMS verification codes (PII and OTP). Only provide those to the CLI if you trust the code after review. For non-China regions the docs advise copying a browser token — prefer that approach if you can inspect and control the token value.
- Because the package includes executable Python code, run it in an isolated environment (container or VM) when you first test; monitor network traffic and filesystem changes (especially writes to {skillDir}/.env, and any unexpected uploads).
- If you cannot or will not review shifu-cli.py, do not provide SMS codes or tokens. Consider asking the skill author for an audit summary or a signed release from a trusted source.
If you want, provide the full contents of scripts/shifu-cli.py and I can analyze it for network endpoints, credential handling, and any suspicious code patterns.Like a lobster shell, security has layers — review code before you run it.
latestvk97cys3bs54f2vjz1h1b3z8b9x842f3t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
