CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

parallel-cli

Agent-native web search, deep research, and enrichment.

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 ./optional-skills/research/parallel-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 body is highly actionable with executable commands for every subcommand, clear sequenced workflows, explicit validation for batch enrichment, and an auth-error recovery loop. Its weaknesses are redundancy (the prefer-native-tools guidance repeated several times and usage patterns that restate section content) and a monolithic single-file structure where per-subcommand reference material could be split into bundled files.

Suggestions

Consolidate the "prefer Hermes native" guidance into one place (e.g. "When to use it") and remove the repetitions in the intro, core rule set, and Pitfalls.

Move per-subcommand detail (FindAll, Monitor, Enrichment flag reference) into references/ files (e.g. references/findall.md) and keep SKILL.md as an overview with one-level-deep pointers.

Trim "Recommended Hermes usage patterns" to only workflows not already covered step-by-step in their own sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient command examples with no explanations of known concepts, but the "prefer Hermes native tools" guidance is repeated roughly four times (intro expectations, "When to use it", core rule 7, and Pitfalls) and "Recommended Hermes usage patterns" restates guidance already given in each section. It is not 4 because this redundancy is more than minor trimming; not 2 because there is no padded conceptual explanation.

3 / 5

Actionability

Every subcommand (search, extract, research, enrich, findall, monitor) has copy-paste-ready executable commands with concrete flags and realistic examples, plus stdin patterns and a documented exit-code table. This matches the fully executable, common-cases-covered anchor.

5 / 5

Workflow Clarity

Multi-step workflows are explicitly sequenced (launch with --no-wait, capture the returned ID, continue other work, poll, summarize with citations), the batch enrichment workflow includes an explicit validation checkpoint ("Validate the output file before reporting success"), and the error-handling section provides a feedback loop for auth errors (check auth, confirm key/login, verify PATH).

5 / 5

Progressive Disclosure

The skill is a single ~380-line file with no bundle files at all; all subcommand API detail (quick reference tree, per-command flags, FindAll/Monitor/Enrichment reference material) is inlined in SKILL.md under good section headers. This matches the anchor of well-structured content where a sizable API reference that could live in separate files is inline. Not 4 because no references exist and the file well exceeds the under-50-lines simple-skill exception.

3 / 5

Total

16

/

20

Passed

Description

62%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 concise and names three concrete capabilities with natural trigger terms, but it omits any "when to use" guidance, which both caps completeness and increases conflict risk with native web search tools. Adding an explicit trigger clause mentioning Parallel-specific workflows would address the two weakest dimensions.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user mentions Parallel or parallel-cli, or needs async deep research jobs, structured CSV enrichment, FindAll entity discovery, or page monitoring.'

Include the distinctive capabilities (extraction, FindAll entity discovery, monitoring) to differentiate from native web_search/web_extract and reduce wrong-skill triggering.

Add natural user synonyms such as 'research reports', 'enrich a spreadsheet', or 'track page changes' alongside the current keywords.

DimensionReasoningScore

Specificity

"web search, deep research, and enrichment" lists several concrete capabilities, matching the anchor for several specific actions with minor gaps. It is not 5 because it omits extraction, entity discovery, and monitoring that the body demonstrates, and not 3 because it goes beyond naming just 1-2 actions.

4 / 5

Completeness

The description has a clear "what" ("Agent-native web search, deep research, and enrichment") but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

"web search" and "deep research" are natural phrases users would say, giving good keyword coverage, but "enrichment" is more jargon and common variations like "look up", "research", or "find information online" are absent. Not 5 because synonyms and variations are missing; not 3 because coverage of the core natural terms is solid.

4 / 5

Distinctiveness Conflict Risk

"web search" is broad and the skill body itself admits overlap with native web_search/web_extract, so a generic search request could trigger this skill incorrectly. "deep research" and "enrichment" give it a partial niche, so it is somewhat specific rather than very broad.

3 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/research/parallel-cli/SKILL.md

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.