Supernal Coding CLI
PassAudited by VirusTotal on May 11, 2026.
Overview
Type: OpenClaw Skill Name: sc Version: 1.0.0 The skill bundle is classified as suspicious due to two main indicators found in `SKILL.md`. First, it instructs the agent to install an external npm package (`@supernalintelligence/supernal-coding`), introducing a supply chain risk where a compromised package could lead to malicious execution. Second, it includes a recommendation to 'add to heartbeat or nightly cron' with a command (`know tidy --fix && know reindex`), which is a direct instruction for the agent to establish system-level persistence. While the stated purpose of the `know tidy` command appears benign (knowledge store cleanup), the capability to instruct an agent to modify system scheduling is a significant security vulnerability and a high-risk prompt injection vector, even if not explicitly malicious in its current form.
Findings (0)
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.
Installing the package would run and trust code that is not included in the reviewed artifacts.
The skill asks users to install a global npm CLI package, but the provided artifact set contains no package code or lockfile for review.
npm install -g @supernalintelligence/supernal-coding
Install only if you trust the package source; review the npm package details and prefer pinned versions or a sandboxed environment for first use.
If run in the wrong repository or without review, these commands could change files, branches, task state, or documentation indexes.
The documented commands can automate git workflow, autonomous task execution, and local file cleanup, which are powerful but aligned with the stated developer-workflow purpose.
sc git smart # Smart commits, branch management sc ralph execute task-name.md --max-iterations 10 know tidy --fix # Auto-fix issues (normalize tags, move misplaced files)
Run mutating commands only in the intended repository, preferably on a branch, and review changes before committing or pushing.
A scheduled cleanup could repeatedly modify or reorganize knowledge-store files without a fresh prompt each time.
The skill suggests recurring scheduled cleanup/reindexing. This is disclosed and user-directed, but it introduces persistent background behavior if the user implements it.
# Recommended: add to heartbeat or nightly cron know tidy --fix && know reindex
Do not add cron or heartbeat jobs unless you understand the affected paths and have reviewed the cleanup behavior.
A session key may grant access to link or identify OpenClaw session information.
The skill references an optional session key for linking tasks to a current session; this is plausible for dashboard integration but is a sensitive session-related value.
sc task link TASK-123 # Link to current session (needs OPENCLAW_SESSION_KEY)
Use the session-linking command only when needed, keep OPENCLAW_SESSION_KEY private, and avoid exposing it in logs or shared task notes.
Local project notes, tasks, or indexed knowledge could influence later agent work if stale or incorrect content is stored.
The skill describes local search, indexing, and persistent task storage, which may reuse local project or knowledge content across workflow tasks.
sc search <query> # Search across all content know reindex # Rebuild INDEX.md **Storage:** `.supernal/tasks/` (per-repo) or `~/.supernal/tasks/` (global)
Keep task and knowledge-store content accurate, avoid placing secrets in indexed notes, and confirm what paths the CLI searches or reindexes.