Skill flagged — suspicious patterns detected

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

bshio

v1.0.0

Microsoft Outlook/Live.com email and calendar client via Microsoft Graph API. List, search, read, send emails. View and create calendar events. Supports devi...

0· 62·0 current·0 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
high confidence
!
Purpose & Capability
The skill's name and description (Outlook/Microsoft Graph client) align with the instructions (list/read/send emails, calendar). However the metadata/execution block says the runtime is a Python script with main './outlook' and requires the 'outlook' CLI, yet no executable or Python code is included in the package manifest — only README and SKILL.md files. That mismatch (declaring a runnable CLI but shipping no code) is incoherent.
!
Instruction Scope
The SKILL.md instructs the agent/user to run commands like 'outlook configure' and 'outlook auth' and to read/write token files (~/.config/outlook-cli/token.json). Those actions are appropriate for an email client, but the instructions assume a local 'outlook' program exists. The README also instructs creating a client secret, while other parts promote device-code auth for headless environments — these authentication instructions conflict and broaden scope without justification.
Install Mechanism
This is an instruction-only skill with no install specification and no downloaded code. That lowers install-time risk. The metadata suggests Python and the 'requests' package are required, which is reasonable for a Graph API client.
Credentials
No environment variables or unrelated credentials are requested (good). The skill requires storing OAuth tokens at ~/.config/outlook-cli/token.json which is expected for an OAuth client. However, the README's guidance to create and input a client secret conflicts with the stated support for device-code (public client) flows — requiring a client secret may be unnecessary and increases risk if users are encouraged to store it locally.
Persistence & Privilege
The skill is not marked 'always:true' and uses normal model invocation. It stores tokens in its own config path (~/.config/outlook-cli) which is reasonable for this functionality and does not request system-wide privileges.
What to consider before installing
This skill's purpose (an Outlook CLI) is plausible, but there are important red flags you should resolve before installing or running anything: - The bundle contains only documentation (README and SKILL.md) and no executable or Python script named 'outlook'. Ask the author where the CLI binary or source code is and why it's not packaged. Do not rely on running commands like 'outlook auth' until you have the actual program. - Authentication guidance is inconsistent: SKILL.md advertises device-code flow (which typically does not require a client secret) but the README instructs creating and entering a client secret. Confirm which auth flow the tool uses. Avoid entering or storing client secrets unless you have audited the code and understand why they are needed. - The skill will store OAuth tokens at ~/.config/outlook-cli/token.json. That is expected, but ensure the file permissions are set (chmod 600) and never share or commit the file. Prefer device-code / public client flows if you want to avoid storing client secrets. - Because this is instruction-only (no install), there is low install-time risk — but you must obtain the actual CLI implementation from a trustworthy source (official repo or release). If the implementation is delivered from an unknown URL later, treat that as higher risk. Recommended next steps before use: obtain and inspect the actual 'outlook' program source (or official release), verify the auth flow and minimal Graph API permissions, and confirm there are no hidden network endpoints or telemetry beyond Microsoft Graph. If the author cannot provide the code or an official release, avoid installing or entering sensitive credentials.

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

latestvk97cvqpjnw7hzcvm58k6zfvkq183h6p9

License

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

Runtime requirements

📧 Clawdis
Binspython3

Comments