ClawHub

Context Recovery

v1.2.2

Automatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram,...

⭐ 3· 4.6k·33 current·35 all-time
byJonathan Rhyne@jdrhyne
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (recover missing conversation context) matches the instructions: fetch channel/thread history, parse messages, and synthesize a summary. There are no unrelated environment variables, binaries, or install steps requested.
ℹ
Instruction Scope
Instructions confine operations to platform/session APIs (message:read, sessions_list, sessions_history) and explicitly prohibit broad filesystem scans and external exfiltration. They do parse for identifiers like URLs, branch names, PRs and may look for 'working directories' mentioned in messages (parsing only). Note: the skill can auto-trigger on compaction indicators and will read channel/thread history automatically when triggered, which has privacy implications depending on connector permissions.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files. This minimizes disk/exec risk — nothing is downloaded or written by default.
ℹ
Credentials
The skill declares no required env vars or credentials (proportional). However, its operation depends on the agent's channel connectors having message-read permissions (e.g., Slack/Discord tokens). Those connector permissions can grant broad access to chat history, so review platform scopes/credentials before use.
✓
Persistence & Privilege
always:false and user-invocable:true. The skill may auto-trigger in-session (appropriate for its purpose) but does not request permanent presence or modify other skills. It requires explicit consent before writing recovered context to disk or persistent memory.
Assessment
This skill appears coherent and does what it says: it reads channel/thread history and synthesizes a recovered context, then asks before saving anything. Before installing, verify the following: 1) The agent connectors (Slack, Discord, Telegram, etc.) only have the minimal scopes you intend — message-read scopes can expose a lot of history. 2) Confirm your runtime actually enforces the 'no filesystem scans / no external sending' constraints described in SKILL.md (instruction-only skills rely on the agent runtime to honor guidance). 3) If you prefer tighter control, disable automatic invocation or require manual invocation, and ensure the skill prompts you before persisting recovered context. If you want extra assurance, run the skill in a limited-test workspace first to observe behavior.

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

latestvk97ba31epck4dyq713vc07ja1s820yvg

License

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

Runtime requirements

🔄 Clawdis

Comments