perplexity-cli-schemas

JSON input and output schemas for all perplexity-cli commands (search, ask, chat). Use when constructing --json payloads or parsing command output programmatically.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/web-search-with-perplexity/schemas/SKILL.md

Quality

Content

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

This is a high-quality, actionable schema reference with executable payloads and jq recipes and well-flagged backend gotchas. Its weakest point is progressive disclosure: a broken sibling-skill reference and a large amount of reference content inlined into one file rather than split across one-level-deep reference files.

Suggestions

Fix or remove the broken reference to ../models/SKILL.md (the path does not resolve), or replace it with inline guidance on choosing a model.

Consider moving the verbose minimal/maximal payload blocks or the full CLI↔JSON mapping table into a separate references/ file, keeping SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable JSON schemas and jq examples and avoids explaining basic concepts Claude already knows; the main inefficiency is providing both 'minimal' and 'maximal' payload examples for every command, which slightly inflates length but stays accurate.	4 / 5
Actionability	It provides copy-paste-ready minimal/maximal JSON payloads, complete field notes with formats and edge cases (e.g. the array-vs-string domains gotcha), and concrete executable jq recipes covering the common cases for each command.	5 / 5
Workflow Clarity	The CLI↔JSON mapping table and backend-difference notes sequence the usage clearly, and the destructive/batch cap does not apply since this is reference documentation rather than a risky mutation workflow; it lacks an explicit validate-then-act checkpoint but the domain does not demand one.	4 / 5
Progressive Disclosure	Content is organized into clear sections, but the single cross-reference to '../models/SKILL.md' points to a path that does not exist, and substantial per-field reference material is fully inlined with no split into separate files — structure is present but navigation and separation could be better.	3 / 5
	Total	16 / 20 Passed

Description

78%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, scoped to a clear niche, and pairs a concrete 'what' with an explicit 'Use when...' trigger. It is strong overall, with the main room for improvement being broader trigger-term synonyms and a slightly wider range of use scenarios.

Suggestions

Broaden the 'Use when...' clause with additional natural triggers, e.g. 'Use when working with perplexity-cli, constructing --json payloads, parsing JSON output, or troubleshooting command field formats'.

Add common synonyms/aliases (e.g. mention 'Perplexity API', 'sonar models', 'stdin JSON') so users searching varied phrasings land on this skill.

Dimension	Reasoning	Score
Specificity	Names concrete capabilities — 'JSON input and output schemas for all perplexity-cli commands (search, ask, chat)' and the specific use cases 'constructing --json payloads or parsing command output programmatically' — covering several distinct actions with only minor coverage gaps.	4 / 5
Completeness	It states a clear 'what' (schemas for the commands) and an explicit 'when' via 'Use when constructing --json payloads or parsing command output programmatically'; the 'when' is concrete but fairly narrow and could name more trigger contexts.	4 / 5
Trigger Term Quality	Natural terms users would say are present ('search', 'ask', 'chat', 'JSON payloads', 'parsing command output', '--json') with good coverage, though it lacks synonyms or alternative phrasings a user might naturally invoke.	4 / 5
Distinctiveness Conflict Risk	The 'perplexity-cli' niche plus 'JSON input and output schemas' is highly specific and clearly scoped to this single tool, with minimal risk of triggering the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: slurpyb/perplexity-cli
Path: .claude/skills/web-search-with-perplexity/schemas/SKILL.md
Commit: 5624eaa

Reviewed: 2 days 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.