导师 Mentor

Turn any public figure into your private AI mentor. Give a name — auto-collect their real posts, speeches, and content from social platforms, extract their t...

What doesn't add up: the README/SKILL.md says the skill only uses public data and needs no credentials, yet the shipped files and step-by-step guides require a connected ManoBrowser (MCP) with API key, browser login cookies, and access to local config files like .mcp.json or config/mcporter.json. The skill also instructs the agent to auto-download ManoBrowser from GitHub and to run curl/git/subprocess commands without asking the user. Before installing or running this skill: 1) Treat it as potentially intrusive — it may access your browser session and local config files. 2) Review all shipped scripts (weibo_collect, bilibili_subtitle_batch, douyin_whisper_batch, etc.) yourself, paying attention to calls that use fetch({credentials:'include'}), subprocess/curl, or write files. 3) If you must try it, run it in an isolated VM/container and do not store sensitive tokens (MCP API keys, browser cookies) on that environment. 4) Do NOT allow automatic network installs — manually inspect and clone ManoBrowser and any dependency before granting the agent permission to run installation commands. 5) If you expect strictly public-data collection, ask the maintainer to remove or clearly separate the 'deep profile' modules that require logged-in sessions and to declare required env vars/configs explicitly. 6) Be wary of the unicode-control-chars finding: it may indicate an attempt to manipulate parsing or hide content; sanitize SKILL.md before use. If you want, I can list specific files and lines that are highest risk and suggest exact mitigations (run-only-in-VM, remove auto-install steps, or require explicit user consent prompts).