Skills/ClawHub/deja-search

deja-search@0.25.0

VERIFIED· install only

Publisher claims: "deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before any plan, review, or blank-slate task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error, when concrete names (repo, service, file, error, flag) surface mid-task by batching recall with reads, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher vshulcz · publishing for 131 daysInstalls 1,277Last detonated 1 h ago
$clawhub install deja-search
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What changed since 0.24.3

vet-skills diff deja-search 0.24.3 0.25.0

In the sandbox, this version reached for nothing 0.24.3 did not. Compared from the two recorded runs, not from source.

0.24.3 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-21 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packageSKILL.md:68 · npx invocation of non-well-known package — may execute untrusted code…ber of hits you got back. - If `deja` is not on PATH, run the same command via `npx -y @vshulcz/deja-vu ...`; if neither works or the index is empty, say that history…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

No other findings across 137 lines in 2 files.

Cost to the agent

Instructions loaded
≈3,090 tok
1 file · 2 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.