CtrlK
BlogDocsLog inGet started
Tessl Logo

perplexity-cli-commands

Full command syntax, all flags, and worked examples for perplexity-cli search, ask, and chat commands.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/web-search-with-perplexity/commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A high-quality command reference: executable examples, clean flag tables, and well-signaled external references, with only minor room to tighten the prose notes.

DimensionReasoningScore

Conciseness

The body is lean: flag tables, syntax blocks, and executable examples assume Claude's competence, with only a few short prose notes (command disambiguation, OpenRouter fallback) that could be trimmed but mostly earn their place.

4 / 5

Actionability

Every section gives fully executable, copy-paste-ready commands covering common cases across all three subcommands, including flag combinations, JSON input, stdin pipes, and jq extraction examples.

5 / 5

Workflow Clarity

As a reference doc it has no multi-step destructive workflow, but command selection is unambiguous and the Backend/Auth section documents precedence, fallback codes, and exit behavior clearly; minor validation/checkpoint gaps are irrelevant for read-only queries.

4 / 5

Progressive Disclosure

Content is well structured into per-command sections with clearly signaled one-level-deep references (root SKILL.md for setup, models/SKILL.md for models); no bundle files exist, and bulk detail is appropriately placed inline for a command reference.

4 / 5

Total

17

/

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.

A concrete, well-scoped description that names the tool and its commands plus the deliverables, but it omits explicit activation/trigger guidance, which limits its completeness score.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when running perplexity-cli or when the user wants to search the web or get AI answers via the Perplexity CLI.'

Include a couple of natural synonyms a user might say (e.g. 'web search', 'AI answer', 'perplexity') to strengthen trigger-term coverage.

State the primary use case up front so the 'when' is as explicit as the 'what'.

DimensionReasoningScore

Specificity

Names the tool, its three commands (search, ask, chat), and three concrete deliverables ("full command syntax, all flags, and worked examples"), giving comprehensive coverage of the command surface with only minor gaps.

4 / 5

Completeness

It clearly states what the skill provides (syntax, flags, examples for the three commands) but lacks any explicit "Use when..." trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The command names "search", "ask", and "chat" are exactly the natural terms users invoke, with good keyword coverage, though it leans slightly technical and omits a few common phrasings.

4 / 5

Distinctiveness Conflict Risk

Naming the specific "perplexity-cli" tool with its three subcommands carves a clear niche with mostly distinct triggers and only minor overlap risk against sibling Perplexity skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
slurpyb/perplexity-cli
Reviewed

Table of Contents

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.