360 Secure SkillHub
360 安全技能中心

Plate Recognizer

该 Skill 借助 oo CLI 调用 OOMOL 托管的 Plate Recognizer 连接器，提供读取单张图片车牌（返回归一化检测结果）与查询当月 Snapshot Cloud 用量两项动作；凭据由服务端注入，需先安装并登录 oo CLI 且完成连接。

oomol
oomol
热度 50.58
最近更新 2026-09-15 12:12:48
分类：效率依赖：第三方 API / 代码执行应用场景：数据处理 / API 集成 / 报告撰写

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-platerecognizer
Metadata
name
oo-platerecognizer
description
Plate Recognizer (platerecognizer.com). Use this skill for ANY Plate Recognizer request — searching and reading data. Whenever a task involves Plate Recognizer, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Plate Recognizer","author":"OOMOL","version":"1.0.3","services":["platerecognizer"],"icon":"https://static.oomol.com/logo/third-party/platerecognizer.png"}

Plate Recognizer

Operate Plate Recognizer through your OOMOL-connected account. This skill calls the platerecognizer connector with the 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 Plate Recognizer. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to 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:

oo connector schema "platerecognizer" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "platerecognizer" --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

  • get_statistics — Retrieve current-month Plate Recognizer Snapshot Cloud usage and reset information.
  • read_number_plates — Read number plates from one image by calling Plate Recognizer Snapshot Cloud and returning normalized detections.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Plate Recognizer 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):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Plate Recognizer is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=platerecognizer

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources