ClawHub

Learn & Reflect

v0.2.0

This skill should be used when the user asks to "record what we learned", "save lessons", "knowledge capture", "reflect on what happened", "write down experi...

⭐ 0· 73·0 current·0 all-time
byFuturize Rush@futurizerush
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 match the content: the SKILL.md provides a structured workflow for capturing lessons and 'annealing' fixes. No unexpected binaries, env vars, or config paths are requested.
ℹ
Instruction Scope
Instructions ask the agent to inventory actions, errors, file paths, and commands from the session and to identify targets for embedding fixes (code, CI, directives). This is appropriate for the stated purpose, but it presumes the agent will use conversational context or any user-provided artifacts — the skill itself does not instruct the agent to autonomously read system files or secrets.
✓
Install Mechanism
No install spec and no code files are present, so nothing is downloaded or written to disk. This is the lowest-risk model for an extension of this type.
✓
Credentials
No environment variables, credentials, or config paths are required. The declared requirements are minimal and appropriate for a documentation/reflection helper.
✓
Persistence & Privilege
always is false and the skill is user-invocable with normal autonomous invocation allowed. It does not request permanent presence or modify other skills or system settings.
Assessment
This skill appears coherent and low-risk because it is instruction-only and requests no credentials or installs. Before using it, consider: (1) Decide whether you want the agent to actually modify code or tooling as part of 'anneal' — prefer that the agent propose concrete changes and require your explicit approval (or a PR) before applying them. (2) Avoid capturing secrets or sensitive files in lesson entries (do not paste API keys, passwords, or private certificates into saved notes). (3) If you are concerned about automatic invocation, keep it user-invoked or require explicit confirmation for actions that change repositories/CI. (4) Review any recommended edits (scripts, linters, CI changes) manually or via your normal code-review process before merging. No static-scan findings were produced because this is an instruction-only skill; that lack of findings is expected and does not imply deeper analysis of runtime behavior.

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

ai-agentvk97b4d2cve576d2awm9xxd8qhn84meeqdocumentationvk97b4d2cve576d2awm9xxd8qhn84meeqknowledgevk97b4d2cve576d2awm9xxd8qhn84meeqlatestvk97b4d2cve576d2awm9xxd8qhn84meeqlearningvk97b4d2cve576d2awm9xxd8qhn84meeqplan-logvk97b4d2cve576d2awm9xxd8qhn84meeqreflectionvk97b4d2cve576d2awm9xxd8qhn84meeqself-annealingvk97b4d2cve576d2awm9xxd8qhn84meeq

License

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

Comments