Skip to main content
Agent skill

Cli Policy Audit

Inspect audit logs, manage access policies, view telemetry data, and review request history from the CLI. Filter by event type, user, or time range for compliance workflows.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Cli Policy Audit when an AI agent needs a reusable SKILL.md workflow for this job: Inspect audit logs, manage access policies, view telemetry data, and review request history from the CLI. Filter by event type, user, or time range for compliance workflows.

When not to use it

Skip Cli Policy Audit when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/cli-policy-audit
# Save SKILL.md to ~/.claude/skills/cli-policy-audit/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-policy-audit/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-policy-audit/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Cli Policy Audit skill for this task: Use Cli Policy Audit when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

## Overview

Inspect audit logs, manage access policies, view telemetry data, and review request history from the CLI. Filter by event type, user, or time range for compliance workflows.

## Quick install

```bash npm install -g omniroute # or: npx omniroute omniroute --version ```

## Subcommands

### `audit`

**Example:**

```bash omniroute audit ```

### `audit tail`

**Flags:**

- `--source <s>` - `--follow` - `--limit <n>`

**Example:**

```bash omniroute audit tail ```

### `audit search <query>`

**Flags:**

- `--source <s>` - `--since <ts>` - `--until <ts>` - `--limit <n>` - `--actor <id>` - `--action <a>`

**Example:**

```bash omniroute audit search <query> ```

### `audit export <file>`

**Flags:**

- `--source <s>` - `--format <f>` - `--since <ts>` - `--until <ts>`

**Example:**

```bash omniroute audit export <file> ```

### `audit stats`

**Flags:**

- `--source <s>` - `--period <p>`

**Example:**

```bash omniroute audit stats ```

### `audit get <id>`

**Flags:**

- `--source <s>`

**Example:**

```bash omniroute audit get <id> ```

### `logs`

**Flags:**

- `--follow` - `--filter <level>` - `--lines <n>` - `--timeout <ms>` - `--base-url <url>` - `--request-id <id>` - `--api-key <key>` - `--combo <name>` - `--status <code>` - `--duration-min <ms>` - `--duration-max <ms>` - `--export <path>`

**Example:**

```bash omniroute logs ```

### `policy`

**Example:**

```bash omniroute policy ```

### `policy list`

**Flags:**

- `--kind <k>` - `--scope <s>`

**Example:**

```bash omniroute policy list ```

### `policy get <id>`

**Example:**

```bash omniroute policy get <id> ```

### `policy create`

**Flags:**

- `--file <path>`

**Example:**

```bash omniroute policy create ```

### `policy update <id>`

**Flags:**

- `--file <path>`

**Example:**

```bash omniroute policy update <id> ```

### `policy delete <id>`

**Flags:**

- `--yes`

**Example:**

```bash omniroute policy delete <id> ```

### `policy evaluate`

**Flags:**

- `--api-key <k>` - `--action <a>` - `--resource <r>` - `--context <json>`

**Example:**

```bash omniroute policy evaluate ```

### `policy export <file>`

**Example:**

```bash omniroute policy export <file> ```

### `policy import <file>`

**Flags:**

- `--overwrite`

**Example:**

```bash omniroute policy import <file> ```

### `telemetry`

**Example:**

```bash omniroute telemetry ```

### `telemetry summary`

**Flags:**

- `--period <p>` - `--compare-to <p>`

**Example:**

```bash omniroute telemetry summary ```

### `telemetry export`

**Flags:**

- `--out <path>` - `--period <p>`

**Example:**

```bash omniroute telemetry export ```

Intended uses

  • Use Cli Policy Audit when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.