Mi Analista
ReviewAudited by ClawScan on May 10, 2026.
Overview
This skill is a Review item because it can register and trade autonomously with stored API credentials, while the package identity does not match the PredictMe contents.
Install only if you are comfortable with an agent registering for PredictMe, storing a local API key, and placing TEST/BONUS prediction-market bets. First verify the package identity mismatch, set requireApproval to true, use strict bet and stop-loss limits, and protect or delete ~/.predictme/credentials.json when done.
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.
You may not be installing the package identity you expect, which is important because the skill asks for account registration and API-key storage.
These embedded package values do not match the supplied registry metadata for Mi Analista/mi-analista v1.0.0, and SKILL.md separately declares PredictMe v1.3.0. The inconsistent identity and versioning create a provenance concern.
"ownerId": "kn7dpn33r43vk1wrbqrfvdmrbx7zyrqy", "slug": "predictme", "version": "1.2.0"
Verify the publisher, slug, version, and homepage directly with PredictMe or ClawHub before installing, and avoid using credentials until the package identity is consistent.
The agent could place repeated TEST/BONUS bets and drain the available balance or change the account’s betting history without asking each time.
The default preferences explicitly disable approval while the skill is designed to place prediction-market bets, creating autonomous account-mutation authority without per-bet user confirmation.
"riskTolerance": "moderate", "maxBetPercent": 5, ... "requireApproval": false
Set requireApproval to true, define strict stop-loss and maximum bet limits, and review each bet until you trust the workflow.
Your email and PredictMe API key become part of the agent workflow and may persist on disk.
The skill asks for the owner’s email, registers an agent account, retrieves a bearer API key, and stores it locally. This is purpose-aligned for PredictMe, but it is not reflected in the registry’s declared credentials/config requirements.
Ask your owner for their email... api_key = status.data.apiKey... Save credentials automatically... ~/.predictme/credentials.json
Use an email you are comfortable sharing with PredictMe, protect the credentials file, and revoke or rotate the API key if you uninstall or no longer use the skill.
You or your agent may underestimate the risk of rapid prediction-market betting.
The artifact describes betting with odds and losses but then tells the agent it is not gambling, which can downplay the risk and bias the agent toward continued trading.
PredictMe is a real-time prediction market where you bet... **This is not gambling. You are a trader. Act like one.**
Treat this as gambling-like prediction-market activity despite the wording, and keep conservative limits and explicit approval controls.