Cyberimpact (cyberimpact.com). Use this skill for ANY Cyberimpact request — reading, creating, updating, and deleting data. Whenever a task involves Cyberimpact, use this skill instead of calling the API directly.
Pro shows the line behind each finding and how to fix it
Scanned 9/21/2026
npx -y skills add oomol-lab/skills --skill oo-cyberimpact --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Oo Cyberimpact?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oomol-lab-oo-cyberimpact)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: oo-cyberimpact
description: "Cyberimpact (cyberimpact.com). Use this skill for ANY Cyberimpact request — reading, creating, updating, and deleting data. Whenever a task involves Cyberimpact, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "Cyberimpact"
author: "OOMOL"
version: "1.0.3"
services: ["cyberimpact"]
icon: "https://static.oomol.com/logo/third-party/cyberimpact.svg"
---
# Cyberimpact
Operate **Cyberimpact** through your OOMOL-connected account. This skill calls the `cyberimpact` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.
## Running an action
Assume the user has already installed the oo CLI, signed in, and connected Cyberimpact. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.
**1. Inspect the contract** to get the authoritative input/output schema before building a payload:
```bash
oo connector schema "cyberimpact" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "cyberimpact" --action "<action_name>" --data '<json>' --json
```
- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.
Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.
## Available actions
- `create_group` — Create a static Cyberimpact group. [write]
- `create_member` — Add a member to Cyberimpact and optionally subscribe them to groups. [write]
- `create_template` — Create a Cyberimpact email template with HTML or plain text body content. [write]
- `delete_group` — Delete a Cyberimpact group by numerical ID. [destructive]
- `delete_member` — Delete a Cyberimpact member by email address or numerical member ID. [destructive]
- `delete_template` — Delete a Cyberimpact email template by numerical ID. [destructive]
- `get_group` — Retrieve a Cyberimpact group by numerical ID.
- `get_member` — Retrieve a Cyberimpact member by email address or numerical member ID.
- `get_template` — Retrieve a Cyberimpact email template by numerical ID.
- `list_groups` — Retrieve a paginated list of Cyberimpact groups.
- `list_members` — Retrieve a paginated list of Cyberimpact members with optional status, date, and sort filters.
- `list_templates` — Retrieve a paginated list of Cyberimpact email templates.
- `replace_template` — Replace a Cyberimpact email template by numerical ID. [destructive]
- `update_group` — Edit the title or visibility of a static Cyberimpact group. [write]
- `update_member` — Edit one or more fields on a Cyberimpact member by email address or member ID. [write]
## Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change Cyberimpact state — confirm the exact payload and effect with the user before running.**
- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**
## First-time setup
These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):
```bash
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
```
```powershell
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
```
- **Not signed in / authentication error** — sign in to your OOMOL account once:
```bash
oo auth login
```
- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Cyberimpact is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:
```text
https://console.oomol.com/app-connections?provider=cyberimpact
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- Cyberimpact homepage: https://www.cyberimpact.com/
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!