Skip to main content
Optimus Labs logo

Use case · Secure SKILLs hub

Every SKILL in your fleet, vetted and governed.

SKILLs arrive as plugin bundles installed with a command, and each one can carry code, credentials, and instructions an agent will follow. Optimus Labs inventories every SKILL, analyzes its posture, and governs which ones run.

  • A complete inventory of every SKILL on every endpoint
  • Static analysis before a SKILL ever runs
  • Policy control over which SKILLs are allowed
Book a demo

Published · Updated

How do I check that the SKILLs my agents use are safe?

It depends on where your SKILLs come from. If you only use a small set of SKILLs written in-house and reviewed in code review, that process may be enough. If employees install SKILL bundles from public repositories and marketplaces, Optimus Labs fits: it inventories every SKILL on every endpoint, analyzes each one for leaked credentials, embedded instructions, and execution paths, and lets you allow, review, or block it by policy. For open-source package vulnerabilities, software composition analysis tools remain the right fit.

Optimus Labs
Illustrative
wallet-sync
Keychain and ~/.ssh

npx productivity-plugin install unpacks 3 SKILLs · Owner: Finance team

Evaluating
Policy · No SKILL runs downloaded installers
ScopeEnterpriseConditionSKILL executes or fetches unreviewed codeResponseBlock, notify admin and owner
How it was detected
Prerequisiterun a downloaded installerReadsbrowser keychain, ~/.sshNetworkunknown host
BlockedAlert sent to admin and owner

Avoided: company credentials handed over through a SKILL nobody vetted.

Illustrative scenarios. Bundle and SKILL names are examples, not customer data.

The risk

SKILLs are code, and they arrive unreviewed

A SKILL is not a document. It is a bundle that can execute, hold credentials, and instruct an agent. Treating it as harmless text is how the incidents below happen.

Leaked credentials

A SKILL bundle ships with live tokens or keys inside it.

Technical risk

Anyone who installs the SKILL inherits credentials that were never meant to leave.

Business impact

Account compromise traced back to a file an employee downloaded in good faith.

Embedded instructions

A SKILL tells the agent to take actions the user never asked for.

Technical risk

The agent follows attacker-written instructions with its full permissions.

Business impact

Data moves or changes hands through a tool the team trusted.

Execution at install or build time

A package or SKILL triggers code execution when published, installed, or built, not just when run.

Technical risk

Trusted build and documentation infrastructure runs supplied code.

Business impact

The compromise happens before any review would ever see it.

Unvetted sources

SKILLs come from public repositories and marketplaces with no publisher verification.

Technical risk

There is no reliable way to tell a safe SKILL from a malicious one by looking at where it came from.

Business impact

Every install is an unreviewed third-party dependency with agent-level access.

In practice

Evidence from the wild

One example comes from Optimus Labs · Civilizations research, one from public reporting. Each pairs technical risk with business impact and links to its source. Neither is customer telemetry.

From Optimus Labs · Civilizations

Research finding

SKILLs arrive as plugin bundles, not lone text files

Our research on agentic SKILLs found that most arrive as part of a productivity plugin installed with a single npx command. One install can unpack scripts, configuration, credentials, and instructions that an agent will follow, with no review step in between.

  1. 01npx install
  2. 02Bundle unpacked
  3. 03Agent follows it

Technical risk

A bundle can hide executable code and agent instructions behind a friendly name, and runs with whatever access the agent already has.

Business risk

Every SKILL an employee installs becomes an unreviewed third-party dependency with agent-level reach into company data.

What to review

  • Which SKILL bundles are installed, and which plugin brought them in
  • Scripts, hooks, and outbound calls inside each bundle
  • Credentials or tokens shipped inside the bundle

From public reporting

Real incident

341 malicious SKILLs shipped a credential stealer

An audit of 2,857 SKILLs on the ClawHub marketplace for OpenClaw found 341 malicious ones. Professional-looking documentation told users to install a prerequisite, which delivered the Atomic macOS Stealer and captured API keys and credentials, including those the agent already held.

  1. 01Popular-sounding SKILL
  2. 02Fake prerequisite
  3. 03Stealer installed

Technical risk

A SKILL's instructions were the attack. Nothing about its name or marketplace listing marked it as unsafe.

Business risk

Employees installing productivity SKILLs handed over company credentials through a marketplace no one vetted.

What to review

  • Which SKILLs are installed and from which marketplace
  • Install instructions that run downloaded files or terminal commands
  • Publisher verification for every SKILL

How Optimus Labs helps

From install to governed

  1. 01

    Inventory every SKILL

    Discovery finds every SKILL bundle on every endpoint, however it was installed, and maps it to its owner.

  2. 02

    Analyze before it runs

    Static analysis inspects each SKILL for credential leakage, embedded instructions, and execution paths, aligned with the OWASP Top 10 for Agentic Applications.

  3. 03

    Govern what runs

    Policies decide which SKILLs are allowed, which need review, and which are blocked, by user, group, or enterprise.

Deploys through your MDM in minutes. macOS and Windows today, Linux coming soon. Prompts and file contents stay on your devices by default. Optimus Labs receives only AI agent asset and behaviour metadata, never PII.

1,708

credential-leakage issues found across 17,022 analyzed agent SKILLs.

Research finding. Measured across public SKILL repositories. It does not describe any single organization's exposure.

Academic research, Jun 1, 2026

Questions

Are SKILLs really code?
Yes. SKILLs typically arrive as plugin bundles installed with a command, and they can carry scripts, credentials, and instructions the agent will execute. Our Top 10 Risks for Agentic SKILLs guide covers this in detail.
Can we allow some SKILLs and block others?
Yes. Policies apply per SKILL, per user, per group, or enterprise-wide. Start in observe-only mode and enforce when ready.
Does analysis happen on our devices?
Static analysis runs on the endpoint. Prompts and file contents stay on your devices by default, and Optimus Labs receives only asset and behaviour metadata, never PII.
What about SKILLs we build internally?
Internal SKILLs are inventoried and analyzed the same way, so a leaked credential or risky instruction is caught before it spreads.

See it on your own agent assets

Now in early access with design partners. Book a demo to join.

Book a demo

Backed by

Benhamou Global Ventures
Arka
Executive Venture Fund
a16z Scout Fund
Scout

Ecosystem

NVIDIA Inception ProgramAWS ActivateOpen Secure AI Alliance general memberThe Linux Foundation Silver MemberCarnegie Mellon University