Skillv1.0.0

ClawScan security

Intellectia Stock Forecast · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 27, 2026, 3:59 AM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's runtime instructions are coherent with calling the SkillBoss API, but there are inconsistent/missing package metadata and install declarations that make the package bookkeeping unreliable and worth extra caution before installing.
Guidance: This skill appears to do what it says (call SkillBoss API for stock forecasts) and the SKILLBOSS_API_KEY credential is appropriate — but metadata inconsistencies are concerning. Before installing: (1) verify the skill's publisher and a trustworthy homepage/source because 'source: unknown' and README references a different install slug; (2) confirm whether SKILLBOSS_API_KEY is actually required by the packaged skill and where/when you'll need to provide it; (3) prefer creating a scoped, rotatable API key (not your primary account key) and monitor its usage; (4) ask the publisher to fix registry metadata (declare required env var and provide a proper install spec) so automated audits can be accurate. If you cannot validate the publisher or the origin, do not install or expose sensitive credentials.

Review Dimensions

Purpose & Capability: concernThe SKILL.md clearly intends to call https://api.skillboss.com/v1 and requires a SKILLBOSS_API_KEY — that credential is appropriate for the stated purpose. However, the registry metadata provided with the skill (the top-level listing) claims 'Required env vars: none' while SKILL.md's embedded metadata lists requires_env: ["SKILLBOSS_API_KEY"]. This mismatch is an incoherence in packaging that should be resolved.
Instruction Scope: okSKILL.md instructs only to call the SkillBoss API (POST /v1/pilot) via curl or python3/requests and to pip-install requests if needed. It does not instruct reading unrelated files, scanning the system, or sending data to other endpoints. The use of SKILLBOSS_API_KEY is explicit in examples.
Install Mechanism: concernThe skill is instruction-only (no install spec in the registry), yet SKILL.md metadata and examples mention 'pip install requests' and provide an install label. The README also references a different install slug ('mar-intellectia-stock-forecast'), indicating inconsistent packaging. There is no automatic installer or downloadable code in the package, so installation behavior depends on external steps and these mismatches reduce trust.
Credentials: noteRequesting a SKILLBOSS_API_KEY is proportional to the skill's purpose (making authenticated API calls). The concern is the registry omission of that required env var — the skill asks for a secret but the top-level metadata doesn't declare it, which could confuse permission audits or automated checks.
Persistence & Privilege: okThe skill does not request always:true and doesn't ask to modify system or other skills' configs. It runs as an on-demand skill (user-invocable) and uses normal network calls; autonomous invocation is allowed by platform default but is not combined with other high-risk permissions here.