Fortune Teller

PassAudited by ClawScan on May 1, 2026.

Overview

This appears to be a low-risk entertainment fortune-telling skill, but it has incomplete install/provenance metadata and can store local command/data logs.

This skill looks safe for casual entertainment use. Before installing, know that it may create files under ~/.local/share/fortune-teller or FORTUNE_TELLER_DIR, command documentation does not fully match the included scripts, and any personal information you enter may remain in local logs unless you delete them manually.

Findings (3)

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.

NoteHigh Confidence

ASI04: Agentic Supply Chain Vulnerabilities

What this means

You may need to verify how the command is installed and which bundled script is actually used.

Why it was flagged

The package includes runnable scripts and references a CLI, but the registry-level source/install requirements are not fully declared.

Skill content

Source: unknown ... No install spec — this is an instruction-only skill ... Code file presence: scripts/fortune.sh, scripts/script.sh

Recommendation

Review the included scripts before use; the publisher should declare the install method and required binaries such as bash/python3.

NoteHigh Confidence

ASI06: Memory and Context Poisoning

What this means

Personal details entered into commands could remain in local files even after the session ends.

Why it was flagged

The script creates a local data directory and records command history/data, so user-entered content can persist on disk.

Skill content

DATA_DIR="${FORTUNE_TELLER_DIR:-${XDG_DATA_HOME:-$HOME/.local/share}/fortune-teller}"; DB="$DATA_DIR/data.log"; mkdir -p "$DATA_DIR"; _log() { ... >> "$DATA_DIR/history.log"; }

Recommendation

Avoid entering sensitive personal information, or set FORTUNE_TELLER_DIR to a temporary/private location and delete the data directory when finished.

NoteHigh Confidence

ASI09: Human-Agent Trust Exploitation

What this means

A user could believe local stored data was deleted when it may still remain in data.log or history.log.

Why it was flagged

The remove command prints that an item was removed but does not modify the stored data file.

Skill content

cmd_remove() {
    echo "  Removed: $1"
    _log "remove" "${1:-}"
}

Recommendation

Verify deletion manually in the configured data directory; the publisher should either implement removal or change the message.