Agent skill

Ops Competitors

by Lifecycle-Innovations-Limited in Lifecycle-Innovations-Limited/claude-ops

OPS on-demand: This skill should be used when the user asks to "competitor intel", "what did they…

MITAuto-check: notes

Install Ops Competitors

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-competitors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/ops-competitors .claude/skills/ops-competitors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ops-competitors" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors into .claude/skills/ops-competitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-competitors", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-competitors --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-ops/skills/ops-competitors .agents/skills/ops-competitors && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ops-competitors" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors into .agents/skills/ops-competitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-competitors", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-competitors --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-ops/skills/ops-competitors .cursor/skills/ops-competitors && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ops-competitors" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors into .cursor/skills/ops-competitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-competitors", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Lifecycle-Innovations-Limited/claude-ops.git --path claude-ops/skills/ops-competitors

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-competitors --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-ops/skills/ops-competitors .gemini/skills/ops-competitors && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ops-competitors" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors into .gemini/skills/ops-competitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-competitors", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-competitors

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-ops/skills/ops-competitors .github/skills/ops-competitors && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ops-competitors" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors into .github/skills/ops-competitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-competitors", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-competitors --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-ops/skills/ops-competitors .opencode/skills/ops-competitors && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ops-competitors" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-competitors into .opencode/skills/ops-competitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-competitors", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ops-competitors
GitHub stars: 542
Token cost: ~1.3k tokens
SKILL.md length: 269 words
Files: 1
Skills in repo: 67
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

OPS on-demand: This skill should be used when the user asks to "competitor intel", "what did they…

Works in 5 steps: Run competitor_context --brand ""… → Print brand metadata: category,… → Print per-competitor signal breakdown… → …
Asks to competitor intel
SKILL.md covers Runtime Context, Mode: No args — Dashboard, Mode: — Drill-down and Mode: refresh [brand], plus 4 more sections
Calls bash and jq

What it does

Ops Competitors is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "competitor intel", "what did they…

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.

When your agent uses it

Asks to competitor intel

Example prompts

“competitor intel”
“/ops-competitors”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Edit, AskUserQuestion

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Run competitor_context --brand "" --window-days 30
Print brand metadata: category, competitor list, last_run, last_discovery
Print per-competitor signal breakdown (group events by .competitor)
Read latest report
Print full high-severity event timeline sorted newest-first

What it can do on your machine

Read from SKILL.md and the folder at commit ee9c784. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Edit
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ops Competitors loads about 1.3k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 269 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~29
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read, Edit, AskUserQuestion
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Lifecycle-Innovations-Limited/claude-ops at commit ee9c784, republished under its MIT licence (© Lifecycle-Innovations-Limited). 269 words, ~1,297 tokens.

Download SKILL.mdSave it as .claude/skills/ops-competitors/SKILL.md (or your agent's skills folder).

name: ops-competitors
description: OPS on-demand: This skill should be used when the user asks to "competitor intel", "what did they…
allowed-tools: Bash, Read, Edit, AskUserQuestion
argument-hint: [brand-name|refresh [brand]|add-url <brand> <competitor> <kind> <url>|alerts|help]
effort: low
maxTurns: 15
disallowedTools: Write, NotebookEdit

Runtime Context

Before rendering, load competitor context:

bash

PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname $(which ops-competitors 2>/dev/null) 2>/dev/null)/..}"
OPS_DATA_DIR="${OPS_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}"
source "$PLUGIN_ROOT/scripts/lib/competitor/context.sh" 2>/dev/null || true
CTX=$(competitor_context 2>/dev/null || echo '{"configured":false,"reason":"lib_not_found"}')

OPS ► COMPETITORS — Intel Dashboard

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

Parse $ARGUMENTS and dispatch to the matching mode below.

Mode: No args — Dashboard

Show all tracked brands with last_run, alert counts, and recent activity. Use competitor_briefing_line for each brand row.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS ► COMPETITORS — [date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

TRACKED BRANDS ([n] total)
  [brand]   last run [date]   [n] alerts · [n] med · [n] low
  ...

PENDING QUEUES
  immediate: [n]   daily: [n]

RECENT HIGH ALERTS (last 7d)
  [timestamp]  [brand]  [competitor]  [snippet…]
  ...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If configured == false: print setup hint and stop.

bash

# Load context
source "$PLUGIN_ROOT/scripts/lib/competitor/context.sh"
competitor_context --window-days 7
competitor_briefing_line

Mobile mode (Rule 7): one line per brand, no banner, no box-drawing.

Mode: `<brand-name>` — Drill-down

Full event timeline (last 30d), top competitors, latest report, per-competitor signal breakdown.

Run competitor_context --brand "<brand>" --window-days 30
Print brand metadata: category, competitor list, last_run, last_discovery
Print per-competitor signal breakdown (group events by .competitor)

Read latest report:

bash

SLUG=$(echo "<brand>" | tr '[:upper:] /' '[:lower:]--' | tr -cd 'a-z0-9-_.')
REPORT="$OPS_DATA_DIR/reports/competitor-intel/latest-${SLUG}.md"
[[ -f "$REPORT" ]] && head -80 "$REPORT"

Print full high-severity event timeline sorted newest-first

Output format:

BRAND: [name]  category: [cat]  last run: [date]
competitors: [a, b, c, ...]

SIGNAL BREAKDOWN
  [competitor]   high: [n]  med: [n]  low: [n]

LATEST REPORT (excerpt)
  [first 80 lines of report]

EVENT TIMELINE (30d — [n] total)
  [timestamp]  HIGH  [competitor]  [source]  [snippet…]
  ...

Mode: `refresh [brand]`

Manually triggers the weekly intel cron immediately.

bash

PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-...}"
CRON_SCRIPT="$PLUGIN_ROOT/scripts/ops-cron-competitor-intel.sh"

# If a specific brand is given, pass it via env override
if [[ -n "$BRAND_ARG" ]]; then
  BRAND_NAME="$BRAND_ARG" bash "$CRON_SCRIPT"
else
  bash "$CRON_SCRIPT"
fi

Stream output. Inform the user when done and show updated competitor_briefing_line.

Mode: `add-url <brand> <competitor> <kind> <url>`

Add a page-diff monitored URL to preferences.json. Valid <kind> values: pricing, features, changelog, careers.

Validate args — if any missing, explain usage and stop.

Show the proposed change:

Add URL for [brand] → [competitor] ([kind]):
  [url]

AskUserQuestion: [Add] / [Cancel]

On confirm, merge via jq:

bash

PREFS="$OPS_DATA_DIR/preferences.json"
jq --arg brand "$BRAND" --arg comp "$COMP" --arg kind "$KIND" --arg url "$URL" '
  .competitor_intel.urls[$brand][$comp][$kind] = $url
' "$PREFS" > /tmp/prefs-tmp.json && mv /tmp/prefs-tmp.json "$PREFS"

Confirm written.

Mode: `alerts`

Tail the last 20 lines of the alerts log:

bash

ALERTS="$OPS_DATA_DIR/reports/competitor-intel/alerts.log"
if [[ -f "$ALERTS" ]]; then
  tail -20 "$ALERTS"
else
  echo "No alerts log found at $ALERTS"
fi

Mode: `help` / unknown args

Print available subcommands:

ops-competitors                           — dashboard (all brands)
ops-competitors <brand>                   — drill-down: events, report, breakdown
ops-competitors refresh [brand]           — run intel cron now (optional brand filter)
ops-competitors add-url <b> <c> <k> <url> — add page-diff URL to preferences.json
ops-competitors alerts                    — tail alerts.log (last 20 lines)
ops-competitors help                      — this message

Error states

configured == false → print "Competitor-intel not configured. Run /ops:setup competitor-intel to get started." and stop.
CRON_SCRIPT not found → print path and stop.
PREFS not writable for add-url → surface error, do not silently fail.

Files

Just SKILL.md in claude-ops/skills/ops-competitors of Lifecycle-Innovations-Limited/claude-ops.

Open the folder on GitHubat commit ee9c784

Compare with similar skills

Ops Competitors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ops Competitors compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ops Competitors this skillLifecycle-Innovations-Limited/claude-ops	542	—	~1.3k	Automated safety check: Notes	MIT	today
Competitorscoreyhaines31/marketingskills	54k	—	~3k	Automated safety check: Pass	MIT	yesterday
Competitor Analysissickn33/agentic-awesome-skills	47k	1 repos	~7.9k	Automated safety check: Notes	MIT	yesterday
Competitor Trackingsickn33/agentic-awesome-skills	47k	1 repos	~2.4k	Automated safety check: Pass	MIT	yesterday
Competitor Analysisphuryn/pm-skills	27k	—	~1.2k	Automated safety check: Pass	MIT	today
Competitor Alternativesalirezarezvani/claude-skills	28k	1 repos	~2.8k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use.
54k GitHub stars~3k tokensUpdated yesterday
Marketing & SEOAuto-check passed
Competitor Analysis
sickn33/agentic-awesome-skills
Research competitors with Browserbase discovery, enrichment lanes, screenshots, matrices, and HTML reports.
47k GitHub starsUsed in 1 repo~7.9k tokens
Marketing & SEOAuto-check: notes
Competitor Tracking
sickn33/agentic-awesome-skills
Systematic competitor analysis for developer tools. An agent skill from sickn33/agentic-awesome-skills.
47k GitHub starsUsed in 1 repo~2.4k tokens
Marketing & SEOAuto-check passed
Competitor Analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities.
27k GitHub stars~1.2k tokensUpdated today
Marketing & SEOAuto-check passed
Competitor Alternatives
alirezarezvani/claude-skills
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
28k GitHub starsUsed in 1 repo~2.8k tokens
Marketing & SEOAuto-check passed
Competitor Ad Intelligence
github/awesome-copilot
Official
A skill your agent uses when the user asks to analyze, tear down, or reverse-engineer a competitor's paid ads.
40k GitHub starsUsed in 1 repo~3.2k tokens
Marketing & SEOAuto-check passed

Questions about Ops Competitors

What does Ops Competitors do?

OPS on-demand: This skill should be used when the user asks to "competitor intel", "what did they…. Ops Competitors is an agent skill from Lifecycle-Innovations-Limited/claude-ops.

When should I use Ops Competitors?

Ops Competitors fits situations like: asks to competitor intel.

How do I install Ops Competitors in Claude Code?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-competitors in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/ops-competitors in your project. Claude Code loads it when a task matches its description.

How do I install Ops Competitors in Codex?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a codex`. Or copy the skill folder (claude-ops/skills/ops-competitors in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/ops-competitors in your project. Codex loads it when a task matches its description.

Can I use Ops Competitors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-competitors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-competitors, .gemini/skills/ops-competitors, .github/skills/ops-competitors and .opencode/skills/ops-competitors in your project.

What does Ops Competitors need to run?

Going by SKILL.md and its folder, Ops Competitors needs the command-line tools its instructions call (bash and jq). Its frontmatter pre-approves these tools: Bash, Read, Edit, AskUserQuestion.

Does Ops Competitors access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ops Competitors safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ops Competitors use?

Ops Competitors is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ops Competitors use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ops Competitors?

Skills that share tags, products or a category with Ops Competitors: Competitors (coreyhaines31/marketingskills, 54k stars), Competitor Analysis (sickn33/agentic-awesome-skills, 47k stars), Competitor Tracking (sickn33/agentic-awesome-skills, 47k stars) and Competitor Analysis (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ops Competitors?

Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 542 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 10, 2026.

Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ops Competitors

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Runtime Context

OPS ► COMPETITORS — Intel Dashboard

Mode: No args — Dashboard

Mode: <brand-name> — Drill-down

Mode: refresh [brand]

Mode: add-url <brand> <competitor> <kind> <url>

Mode: alerts

Mode: help / unknown args

Error states

Files

Compare with similar skills

Similar skills

More from Lifecycle-Innovations-Limited/claude-ops

Questions about Ops Competitors

Mode: `<brand-name>` — Drill-down

Mode: `refresh [brand]`

Mode: `add-url <brand> <competitor> <kind> <url>`

Mode: `alerts`

Mode: `help` / unknown args