sherlock

Find accounts for a username across 400+ platforms.

Quality

68%

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 ./optional-skills/security/sherlock/SKILL.md

Quality

Content

75%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 highly actionable with concrete commands and a clear, validated workflow, supported by good section organization; the main weakness is redundancy around installation and an example interaction that restates the procedure.

Suggestions

Consolidate the installation guidance (currently repeated in Requirements, Procedure step 1, and the Installation section) into a single location to tighten conciseness.

Trim or shorten the Example Interaction since it largely reiterates the already-clear Procedure steps.

Consider moving the Pitfalls/error-recovery guidance closer to the relevant steps to make feedback loops inline rather than separated.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and procedural, but installation is covered redundantly in Requirements, Procedure step 1, and a dedicated Installation section, and the Example Interaction largely restates the procedure.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (`sherlock --print-found --no-color "<username>" --timeout 90`, install/docker commands) with documented flags and output-parsing examples covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence includes an upfront install-validation checkpoint and an end Verification checklist, with Pitfalls covering error recovery, but the feedback loops live in a separate section rather than being inline within the main flow.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clearly headed sections with no nested references; the only gap is the redundant Installation content that could be consolidated, keeping it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

61%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 a clear, distinctive niche with natural trigger terms, but it lacks an explicit "Use when..." trigger clause and only describes a single action, which limits completeness and specificity.

Suggestions

Add a "Use when..." trigger clause (e.g., "Use when finding social media accounts for a username or checking username availability") to lift completeness above 3.

Include additional concrete actions or synonyms (e.g., "social media profiles", "check username availability") to broaden trigger-term coverage and specificity.

Mention common user phrasings like "where is this username registered" to improve trigger-term naturalness.

Dimension	Reasoning	Score
Specificity	The phrase "Find accounts for a username across 400+ platforms" names the domain (username accounts) and one concrete action (find), with the "400+ platforms" scope adding specificity, but it lists only a single action rather than multiple capabilities.	3 / 5
Completeness	It clearly states what the skill does ("Find accounts for a username across 400+ platforms") but omits any "Use when..." trigger clause, capping completeness at 3 per the missing-trigger-guidance rule.	3 / 5
Trigger Term Quality	"accounts", "username", and "platforms" are natural terms a user would say, giving good keyword coverage, though common synonyms like "social media" and "profiles" are absent.	4 / 5
Distinctiveness Conflict Risk	The username-account-search niche across 400+ platforms is distinctive with low overlap risk, but without an explicit trigger phrase it falls short of the fully-triggered anchor 5 example.	4 / 5
	Total	14 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
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/security/sherlock/SKILL.md
Commit: 6327930

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.