ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Retrospective

v1.0.0

Run a structured weekly agent retrospective. Analyses wins, failures, skill gaps, cron health, and config issues from the last 7 days. Produces honest, speci...

⭐ 0· 102·0 current·0 all-time
byDavid Furlong@davidfurlong
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (weekly retrospective) aligns with the instructions: reading memory/, reading MEMORY.md, analysing recent runs, checking cron history, recommending skills, and writing a retro. Nothing requested is unrelated to running a retrospective.
✓
Instruction Scope
SKILL.md's runtime steps are explicit and bounded: read memory files, check cron status, assess skills, write memory/retro-YYYY-MM-DD.md, update MEMORY.md, and optionally add a cron job. These actions are within the skill's purpose; there is no instruction to access unrelated system paths or external endpoints.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files. No downloads or package installs—minimal surface area.
✓
Credentials
Requires no environment variables, credentials, or config paths. The SKILL.md reads local agent memory files and cron status only, which is proportionate to the retrospective function.
ℹ
Persistence & Privilege
Skill will create a weekly cron job (persistent scheduled task) and write retros to memory/. This is appropriate for the purpose but is a persistent change the user should review (cron entry and files written). The skill is not always:true and does not request broader platform privileges.
Assessment
This skill appears coherent and limited to its stated purpose, but check the following before enabling: 1) It will read your memory/ files and MEMORY.md — ensure those files don't contain secrets you don't want re-processed. 2) It will create a recurring cron job that writes to memory/ and can run autonomously; review the cron entry (schedule, payload) after first run and remove if undesired. 3) The retro may recommend installing other skills — review any recommended skills and their permissions before installing. 4) If you want a dry run, run the skill manually once rather than allowing it to auto-schedule. Overall this is coherent behavior for a retrospective skill.

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

latestvk9729a227sxnm7bzgghxq11z1n83az6t

License

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

Comments