oo-knowbe4KnowBe4 (knowbe4.com). Use this skill for ANY KnowBe4 request — searching and reading data. Whenever a task involves KnowBe4, use this skill instead of calling the API directly.
Install via ClawdBot CLI:
clawdbot install oomol/oo-knowbe4Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Potentially destructive shell commands in tool definitions
curl -fsSL https://cli.oomol.com/install.sh | bashCalls external URL not in known-safe list
https://static.oomol.com/logo/third-party/knowbe4.pngAI Analysis
The skill is a straightforward KnowBe4 connector wrapper that uses the oo CLI with server-side credential injection, and its actions (get/list account, users, groups) are consistent with the stated purpose. The only flagged items are a standard curl|bash install command for the oo CLI and a static logo URL, neither of which constitutes data exfiltration, credential harvesting, or hidden malicious instructions. No evidence of unauthorized external data transmission or intent override was found.
Audited Oct 11, 2026 · audit v1.0
Generated Oct 11, 2026
A security operations analyst pulls every KnowBe4 user to identify which employees still need their first simulated phishing training. They cross-reference accounts with group membership to prioritize high-risk departments such as finance and executive assistants, then trigger targeted enrollment in the security awareness program.
A compliance officer at a healthcare provider uses list_users and list_groups to produce evidence that all staff completed required HIPAA security awareness training. They filter by group to separate clinical and administrative teams and export the data into quarterly audit packages for regulators.
An HR operations specialist builds a recurring report showing training completion percentages across business units. By listing groups and users with expanded group data, they surface teams that lag behind and send targeted reminders before the training deadline.
After a real phishing incident, a security engineer checks the affected user's KnowBe4 profile and training history to determine whether they had failed the relevant simulation. They then assign remedial training and monitor progress to closure as part of the incident response process.
An IT director performs a quarterly subscription and license usage review using get_account to confirm seat counts align with current headcount. They then reconcile active users against the directory to avoid paying for unused licenses or falling short on coverage.
KnowBe4 sells subscription access to simulated phishing and security training content on a per-user, per-year basis. Customers pay recurring fees based on seat count, then use platform data to measure and improve employee resilience against social engineering attacks.
Managed service providers use KnowBe4 APIs to monitor and administer security awareness programs on behalf of many client organizations. They aggregate phish-prone percentages and training completion rates into client-facing dashboards and recurring advisory services.
A GRC or compliance automation platform integrates KnowBe4 data to prove that workforce training controls are continuously met. The vendor maps training completion records to frameworks like SOC 2, HIPAA, or ISO 27001 and surfaces gaps inside its own compliance dashboards.
💬 Integration Tip
Always run 'oo connector schema "knowbe4" --action "<action>"' first to confirm exact input fields (like status, group, per_page, cursor) before constructing --data; if authentication errors appear, verify the KnowBe4 API key connection in the OOMOL console rather than re-running auth login.
Scored Oct 11, 2026
Real-time search engine supporting web search, vertical domain search, parallel batch search, and URL content extraction.
Manage Feishu (Lark) calendars by listing, searching, checking schedules, syncing events, and marking tasks with automated date extraction.
cad reference tool
Search, install, and create OpenClaw skills using intelligent matching across built-in, local, and GitHub skill repositories.
Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for CLI design, argument parsing, interactive prompts, progress indicators, shell completions.
Publish local skills to ClawHub with customizable version, name, path, and optional changelog using command line or Python API.