CtrlK
BlogDocsLog inGet started
Tessl Logo

perplexity-cli-patterns

Agent recipes, piping patterns, scripting idioms, and common workflows for perplexity-cli. Use when constructing multi-step queries, piping output, or integrating into agent workflows.

70

Quality

85%

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

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 highly actionable, code-forward recipe collection with clear workflow sequencing and reflection feedback loops. Its only weaknesses are mild verbosity in the methodology section and no use of external reference files to keep the main body leaner.

DimensionReasoningScore

Conciseness

The body is code-forward and lean, assuming Claude's competence with bash/jq and avoiding concept-padding; the 'Research Methodology — Read This First' prose and the reflect-loop template are substantive but slightly redundant with the broad→narrow example above them, so minor trimming is possible.

4 / 5

Actionability

Dozens of copy-paste-ready bash commands with concrete jq filters, flags, and stdin payloads cover the common cases (extract content, citations, search, streaming capture, domain/academic/SEC modes), matching the fully-executable anchor.

5 / 5

Workflow Clarity

The research methodology is clearly sequenced (Round 1 broad → AGENT REFLECTS → Round 2 narrow → Round 3) with explicit reflection feedback loops and an exit-code map for error recovery; held below 5 because the checkpoints are advisory rather than strict validation gates.

4 / 5

Progressive Disclosure

No bundle files exist; the single ~310-line file is well-organized into clearly-headed sections separated by horizontal rules with easy navigation, but it does not split the lengthy research methodology or a jq-pattern reference into one-level-deep files, leaving a minor organization gap for a document this size.

4 / 5

Total

17

/

20

Passed

Description

87%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 well-constructed description that explicitly covers both capabilities and trigger conditions for a specific CLI tool, with strong distinctiveness. The main weakness is trigger-term coverage that omits the most natural end-user verbs (search/research).

DimensionReasoningScore

Specificity

Names the domain ('for perplexity-cli') and several concrete action categories — 'recipes, piping patterns, scripting idioms' plus 'constructing multi-step queries, piping output, integrating into agent workflows' — but these are pattern-category names rather than fully granular verbs, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' ('Agent recipes, piping patterns, scripting idioms, and common workflows for perplexity-cli') and 'when' via a concrete 'Use when...' trigger clause, matching the anchor for clearly and explicitly answering both.

5 / 5

Trigger Term Quality

The 'Use when constructing multi-step queries, piping output, or integrating into agent workflows' clause supplies natural developer-facing terms; however, the most common user phrases for a Perplexity tool ('search', 'research', 'web look-up') are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoping to a named tool ('perplexity-cli') with tool-specific triggers creates a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.