pocket-detection

Multi-method binding pocket detection and druggability assessment. Grid-based, fpocket, and P2Rank detection with druggability scoring, visualization, and cross-structure comparison.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/chemistry/pocket-detection/SKILL.md

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, well-structured skill body with executable workflows and externalized scripts; the main gaps are an orphaned reference file and minor redundancy.

Suggestions

Link references/methods_guide.md from the body (e.g., under Output Interpretation) so the bundled reference is discoverable rather than orphaned.

Trim the redundancy between the Overview 'Key capabilities' list and the 'When to Use This Skill' bullets.

Add an explicit validate-output checkpoint between steps in Workflow 6 (e.g., confirm pockets.json contains a center before feeding it to docking).

Dimension	Reasoning	Score
Conciseness	Dense and action-oriented with concrete commands and JSON examples throughout; minor redundancy between the Overview key-capabilities list and the 'When to Use' bullets keeps it just below a 5.	4 / 5
Actionability	Fully executable, copy-paste-ready bash commands across six workflows with realistic flags, plus concrete JSON output schemas and a script reference table covering the common cases.	5 / 5
Workflow Clarity	Workflows are numbered and sequenced with a Quick Verification checkpoint and Species Validation step; the skill is read-only analysis so the destructive-operation cap does not apply, but inter-step output validation in the full pipeline is only implicit.	4 / 5
Progressive Disclosure	Implementation is properly externalized into linked scripts (scripts/detect.py etc., all real files) with clear section headers, but references/methods_guide.md is never linked from the body and some reference-style interpretation tables are inlined.	4 / 5
	Total	17 / 20 Passed

Description

75%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 specific, capability-rich description with a clear niche, but it lacks an explicit 'when to use' trigger clause, which caps its completeness score.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when finding binding pockets, assessing druggability, or comparing binding sites across structures').

Add natural synonyms users might say, such as 'active site' and 'binding site', alongside the method names.

Drop or de-emphasize the fpocket/P2Rank method names in the description in favor of natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Grid-based, fpocket, and P2Rank detection', 'druggability scoring, visualization, and cross-structure comparison' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'binding pocket detection' and 'druggability assessment' are natural user terms, but fpocket/P2Rank are jargon and common synonyms like 'active site' or 'binding site' are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche — pocket detection and druggability assessment — distinct from related docking/affinity skills, with minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/chemistry/pocket-detection/SKILL.md
Commit: 3a6c3a9

Reviewed: 1 day 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.