memory-compactor
Skill declares memory file manipulation and scheduled execution but provides no implementation code to audit, creating a doc-to-code verification gap.
Why this conclusion was reached
2/4 dimensions flagged1 undeclared or violating capabilities were inferred.
No obvious high-risk egress or execution signals were found.
The report includes 4 attack-chain steps and 0 severe findings.
Dependency information is incomplete, so supply-chain confidence stays limited.
Attack Chain
Entry · SKILL.md:1
reconnaissance · SKILL.md:12
Escalation · SKILL.md:15
Impact · SKILL.md:22
What drove the risk score up
SKILL.md describes filesystem operations but has zero scripts to audit
Claims '定时任务自动执行' (scheduled auto-execution) without explaining mechanism
Skill accesses memory files that may contain sensitive data but no code to audit behavior
Missing explicit declaration of required filesystem permissions
Most important evidence
Documentation-only skill with unverifiable behavior
The skill describes filesystem operations (compress, clean, write) on memory files but provides zero implementation code. Cannot verify if declared behavior matches actual execution.
SKILL.md:1 Undeclared scheduled execution mechanism
SKILL.md states '定时任务自动执行: 每周日22:00' but does not explain how scheduled execution is implemented. Could involve cron jobs, systemd timers, or hidden agent hooks.
SKILL.md:22 Memory file access without visibility into data handling
Skill operates on memory files that may contain sensitive user data, preferences, or potentially credentials. No code to verify data remains local and is not exfiltrated.
SKILL.md:12 Declared capability vs actual capability
SKILL.md describes '压缩冗余内容,清理过期信息' (compress redundant content, clean expired info) but provides no implementation Suspicious artifacts and egress
No obvious IOC was extracted.
Dependencies and supply chain
There are no structured dependency warnings.
File composition
SKILL.md