Matrix Detection
v1.0.0Identify patterns where ignorance, noise, hype, and manipulation disguise themselves. Reveal dependency loops, governance theater, and predatory incentive st...
⭐ 0· 89·0 current·0 all-time
byMauricio Z. Filho@mzfshark
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (detecting manipulation, hype, dependency loops) align with the skill's footprint: it requests no binaries, env vars, or installs. Minor provenance inconsistency: registry metadata lists an owner ID (kn741...) while the skill files identify the author/owner as 'Morpheus' / 'morpheus-agent-001' and the Source/Homepage are unknown; this is not a functional risk but reduces traceability.
Instruction Scope
SKILL.md is purely descriptive/purpose text and contains no runtime commands, file paths, environment access, or external endpoints. There are no vague 'gather whatever context you need' instructions — scope is limited to conceptual detection.
Install Mechanism
No install spec and no code files; nothing is written to disk or downloaded. This is the lowest-risk install profile.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no undeclared env accesses in the instructions.
Persistence & Privilege
always is false, user-invocable is true, and disable-model-invocation is false (the platform default). This provides normal autonomous invocation capabilities but does not force permanent inclusion or elevated privileges.
Assessment
This skill appears internally consistent and low-risk because it is instruction-only and asks for no secrets or installs. Before installing, consider: (1) provenance — the skill has no homepage and the author/owner identifiers differ from the registry owner ID, so you may want to verify the publisher if origin matters; (2) outputs are conceptual — validate any strong claims the skill makes rather than treating them as authoritative; and (3) never provide secrets or private data to a skill unless it explicitly needs them and you trust the source.Like a lobster shell, security has layers — review code before you run it.
betavk97dmrx5v43fc1bt90dv34gwn983y68tlatestvk97dmrx5v43fc1bt90dv34gwn983y68t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.