Skills/ClawHub/deja-search

deja-search@0.24.3

CAUTION· static 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: static analysis only — behavior not yet observed.

Registry ClawHubPublisher vshulcz · publishing for 129 daysInstalls 1,225Last detonated 11 h ago

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

What changed since 0.24.2

vet-skills diff deja-search 0.24.2 0.24.3

In the sandbox, this version reached for nothing 0.24.2 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 analysed it statically (a sandbox run is pending) on 2026-11-19 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

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,056 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.

What would make this Verified

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim vshulcz: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim vshulczPropose a patch to the maintainer