TL;DR: OpenClaw skill audits found 41% of 2,890+ skills with vulnerabilities, plus 9,515 findings and 539 malware indicators, ClawSecure reported. Agentic workflows need runtime permission control because installed skills can still reach files, shells, and clipboard data.
Editorial analysis by NHI Mgmt Group, based on content published by ClawSecure: “ClawSecure Reached #2 Product of the Day on Product Hunt”.
By the numbers:
- ClawSecure recorded 1,498 new users scanning agents through the platform on launch day.
- ClawSecure found that 41% of popular OpenClaw skills have security vulnerabilities.
- ClawSecure detected 9,515 total security findings across the audited dataset.
Key questions
Q: Why do approved agent skills still create security risk after scanning?
A: Scanning only tells you what was visible at one point in time.
Q: How should security teams manage permissions for AI agents?
A: Security teams should regularly assess and update the permissions granted to AI agents to ensure they align with their intended scope.
Q: What breaks when AI agent skills are treated like documentation instead of runtime policy?
A: The review model breaks because the agent consumes skill instructions as operational input, not as explanatory text.
Practitioner guidance
- Define agent skills as governed identities Classify each OpenClaw skill by the authority it can exercise, including filesystem, clipboard, shell, and other tool permissions, then assign an owner and review cadence.
- Gate installation on delegated authority review Require a pre-install approval step that checks what the skill can do at runtime, not just whether its code scans cleanly or its repository looks reputable.
- Monitor approved skills for post-install change Track code, dependencies, and observed behaviour after deployment so a later update or hidden action cannot silently expand the skill's access path.
Bottom line: AI agent skills create a governance problem because their authority continues after installation, when they can still reach files, shells, and clipboard data.
Glossary terms: Agentic Skill, Delegated Authority, Runtime Trust, Privilege Drift
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Agentic skill governance is now an access control problem, not a software catalog problem. The article's core evidence is that skills can request filesystem, clipboard, and shell access, which means the real governance unit is delegated authority. That shifts the control question from 'is this package clean?' to 'what can this runtime entity do if it is trusted?' Practitioners should classify agent skills as governed identities with scoped permissions, not just installable artifacts.
A question worth separating out:
Q: What signs show that an agent skill ecosystem is outpacing governance?
A: High vulnerability density, repeated malware indicators, and broad tool permissions across popular skills all point to governance lag. If teams cannot say who approved a skill, what it can touch, and how it is monitored after install, the ecosystem is already beyond manual review capacity.
👉 Read our full editorial: OpenClaw skill audits show AI agent governance is already lagging