ClawHub

Smart Memory Query

v1.0.0

Enforce proactive, query-optimized memory_search usage. Must run memory_search when (1) prior context is referenced, (2) a new task starts, or (3) a proper n...

⭐ 0· 363·2 current·2 all-time
by조민준@jo-minjun
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name and description match the SKILL.md: the skill exists solely to enforce when and how to call memory_search. It does not request unrelated binaries, environment variables, or config paths.
✓
Instruction Scope
Runtime instructions are narrowly focused on building and issuing small, targeted memory_search calls based on clear triggers (prior context, new tasks, proper nouns). The instructions do not ask the agent to read unrelated files, access other system state, or transmit results to arbitrary external endpoints.
✓
Install Mechanism
Instruction-only skill with no install spec or code files; nothing is written to disk or fetched at install time.
✓
Credentials
The skill requires no environment variables, credentials, or config paths, which matches its stated purpose of shaping memory_search behavior.
ℹ
Persistence & Privilege
The skill sets always: true which forces it to be included in every agent run. That is explainable given the skill's aim to enforce proactive searches, but it does increase the skill's runtime presence and the number of memory_search calls the agent may make. Consider whether you want this behavior globally enabled.
Assessment
This skill is coherent and lightweight: it only instructs the agent how and when to call memory_search and requests no credentials or installs. The main thing to consider before installing is the always: true setting — the skill will be loaded for every agent session and may cause the agent to run additional memory_search queries automatically (which can increase compute, latency, and the surface area for any data pulled from your memory store). If you are concerned about cost, noise, or privacy, either disable or request a version without always: true, or limit when the skill may be activated. Also review how your memory_search implementation handles sensitive data so automated searches do not inadvertently surface secrets.

Like a lobster shell, security has layers — review code before you run it.

latestvk9713wdtrp98cq650ercrs798n81t82h

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments