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.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-policy-audit/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a clean, executable CLI reference that avoids verbosity, but it lacks workflow validation for destructive policy operations and does not progressively disclose the large command catalog into separate reference materials. Examples also under-demonstrate flag usage.

Suggestions

Add a validation/confirmation workflow for destructive commands (e.g. 'Before policy delete, run policy get <id> to confirm the target; --yes skips the prompt').

Show at least one realistic flag combination in the examples (e.g. `omniroute audit search failed_logins --actor alice --since 2026-08-01`).

Move the bulk subcommand/flag catalog into a separate REFERENCE.md and keep SKILL.md as an overview with a few common-case examples.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept explanation, but each subcommand repeats a bare 'Example' block (e.g. `omniroute audit`) that adds little value, so it is efficient with minor trim opportunities rather than fully lean.	4 / 5
Actionability	Concrete subcommands and flag listings are executable, but the examples never demonstrate flag combinations (e.g. `omniroute audit search <query> --actor <id> --since <ts>`), leaving a minor gap in copy-paste-ready usage.	4 / 5
Workflow Clarity	This is a flat command reference with no multi-step sequencing, and destructive operations (policy delete, policy update, policy import --overwrite) carry no validation or verification guidance, which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Section headers per subcommand give reasonable in-file structure, but the large command reference is entirely inlined with no navigation to a separate reference file and no bundle files exist, so it sits between 'some structure' and 'good structure'.	3 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and covers a coherent compliance/ops niche with natural trigger terms, but it lacks an explicit 'Use when...' guidance clause, capping its completeness. Adding concrete trigger phrasing would push it toward the top anchor.

Suggestions

Add an explicit trigger clause such as 'Use when the user needs to audit CLI activity, manage access policies, or review compliance telemetry.'

Tighten 'manage access policies' into concrete verbs (e.g., 'create, update, and delete access policies') to lift specificity.

Include a synonym or file-format term (e.g., 'audit trails', 'access control rules') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions tied to specific domains ('Inspect audit logs, manage access policies, view telemetry data, and review request history') plus concrete filtering dimensions, but 'manage' is somewhat broad, leaving minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	The 'what' is clearly stated, but the 'when' is only weakly implied by 'for compliance workflows' and there is no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like 'audit logs', 'access policies', 'telemetry data', 'request history', and 'compliance workflows' are present and would be said by users, but synonyms and file/format extensions are missing, so it falls short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The CLI audit/policy/telemetry/compliance niche is mostly distinct with clear triggers, with only minor overlap risk against other ops/admin tooling skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: diegosouzapw/OmniRoute
Path: skills/cli-policy-audit/SKILL.md
Commit: 6435f61

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.