CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lipinski-rule-filter

Filter compound libraries based on Lipinski's Rule of Five for drug-likeness.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/lipinski-rule-filter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 core usage commands and parameter documentation are solid and executable, but the body is heavily padded with template boilerplate, self-contradictory (Dependencies requires rdkit-pypi while Prerequisites says no packages required), and its cross-references point the wrong direction. Tightening to the genuinely useful sections and adding output validation would make this a strong skill.

Suggestions

Cut the boilerplate sections (Key Features, Implementation Details, Output Requirements, Response Template, Risk Assessment/Security Checklist/Evaluation Criteria/Lifecycle) and keep Usage, Parameters, Lipinski's Rules, Workflow, and Error Handling.

Fix the contradictions: Dependencies says rdkit-pypi is required while Prerequisites says 'No additional Python packages required'; correct the 'See ## X above' references that actually point to sections below; remove the nonsensical audit command that passes prose as a --input file.

Link the reference explicitly (e.g. 'Rule details and citations: see [references/lipinski_references.md](references/lipinski_references.md)') and de-duplicate the rule thresholds between SKILL.md and the reference file.

Add a result-level validation step to the workflow for batch runs, e.g. checking the output file row count or spot-checking a known compound's violation count.

DimensionReasoningScore

Conciseness

The ~200-line body for a single-script skill is padded with generic boilerplate ('Key Features', 'Implementation Details', 'Output Requirements', 'Response Template') and broken cross-references ('See `## Usage` above' points to a section defined below; same for Prerequisites/Workflow). It is not anchor 1 because the Usage, Parameters, and Lipinski's Rules sections carry genuine task content.

2 / 5

Actionability

Concrete executable commands ('python scripts/main.py --input compounds.smi --output filtered.smi', '--smiles "CC(=O)Oc1ccccc1C(=O)O" --check') and a complete parameter table cover the common cases. It misses anchor 5 because the 'Audit-Ready Commands' include a bogus invocation feeding prose ('Audit validation sample with explicit symptoms...') as a --input SMILES file.

4 / 5

Workflow Clarity

The Workflow section lists steps but they are generic ('Confirm the user objective...', 'Use the packaged script path...'), and validation is limited to a syntax check (py_compile) plus --help with no result-level checkpoint for this batch filtering operation. Per the batch-operation cap, workflow clarity cannot exceed 3 without validation of the output.

3 / 5

Progressive Disclosure

The bundle structure is reasonable (SKILL.md + scripts/main.py + one-level-deep references/lipinski_references.md), but the body only gestures generically ('Reference material available in `references/`') without naming or linking the reference file, and Lipinski's rules are duplicated in both SKILL.md and the reference. Some structure exists, so it sits at anchor 3 rather than 2.

3 / 5

Total

12

/

20

Passed

Description

65%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, third-person description with good domain keywords, but it omits any explicit 'when to use' trigger clause and describes only a single action. Adding a 'Use when...' clause with terms like SMILES/SDF file filtering would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when filtering SMILES/SDF compound libraries, screening molecules for drug-likeness, or checking compounds against the Rule of Five.'

Mention the output the user gets (filtered compound list plus a rule-violation report) to strengthen specificity.

Include natural synonyms and file extensions users would say: 'SMILES', '.smi', 'SDF', 'ADMET screening'.

DimensionReasoningScore

Specificity

The description names the domain ('compound libraries', 'Lipinski's Rule of Five') and one concrete action ('Filter'), matching the '1-2 concrete actions, but not comprehensive' anchor. It does not list several specific actions, so it falls below anchor 4.

3 / 5

Completeness

The 'what' is clear (filter compound libraries by Lipinski's Rule of Five), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Lipinski', 'Rule of Five', 'drug-likeness', and 'compound libraries' are natural phrases a user would say. Common variations and file formats (SMILES, SDF, ADMET, bioavailability) are missing, so it does not reach comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming a specific pharmacology heuristic ('Lipinski's Rule of Five') gives this a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/lipinski-rule-filter/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.