Memory Pruner
The skill declares shell runtime and references a memory-pruner script that does not exist, constituting a documentation mismatch with no functional code present.
Why this conclusion was reached
0/4 dimensions flaggedDeclared resources and inferred behavior are broadly aligned.
No obvious high-risk egress or execution signals were found.
There is no explicit malicious chain in the report.
Dependency information is incomplete, so supply-chain confidence stays limited.
What drove the risk score up
SKILL.md declares 'memory-pruner' CLI script and 'memory/' directory that do not exist in the file tree
config.json declares runtime: 'shell' suggesting shell:WRITE permissions, but no scripts are present to review
Most important evidence
Referenced implementation files are missing
SKILL.md references 'memory-pruner' as the main CLI script and 'memory/' as the working directory, but these files do not exist in the package. The pre-scan confirms hasScripts: false.
SKILL.md:58 Entry point declared but not present
config.json specifies 'entry': 'memory-pruner' with runtime: 'shell', indicating a shell script entry point that is absent from the package.
config.json:12 Declared capability vs actual capability
config.json declares runtime: shell but no scripts exist to verify config.json declares runtime: shell but memory-pruner script is missing Suspicious artifacts and egress
No obvious IOC was extracted.
Dependencies and supply chain
There are no structured dependency warnings.
File composition
config.json SKILL.md