Predict patient-specific neoantigen candidate peptides with high immunogenicity based on HLA typing and tumor mutation profiles, for tumor immunotherapy target screening.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Data analysis/neoantigen-predictor/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a technically precise description with strong specificity and clear domain focus in computational oncology/immunotherapy. Its main weaknesses are the lack of an explicit 'Use when...' clause and limited coverage of natural language variations users might employ when seeking this capability. The highly technical terminology serves distinctiveness but may miss users who phrase requests in simpler terms.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when analyzing tumor sequencing data for vaccine targets, predicting cancer neoantigens, or screening immunotherapy candidates.'
Include simpler trigger term variations like 'cancer vaccine targets', 'tumor antigens', 'personalized cancer immunotherapy', or 'MHC binding prediction' to capture more natural user phrasings.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Predict patient-specific neoantigen candidate peptides', 'high immunogenicity', 'based on HLA typing and tumor mutation profiles', 'tumor immunotherapy target screening'. These are precise, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (predict neoantigen candidates based on HLA/mutation data for immunotherapy screening), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the purpose statement. | 2 / 3 |
Trigger Term Quality | Contains relevant technical keywords like 'neoantigen', 'HLA typing', 'tumor mutation', 'immunotherapy', 'peptides', but these are highly specialized terms. Missing common variations or simpler terms users might say like 'cancer vaccine targets', 'tumor antigens', or 'personalized cancer therapy'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specialized niche in computational immunology/oncology. The combination of 'neoantigen', 'HLA typing', 'tumor mutation profiles', and 'immunotherapy' creates a distinct fingerprint unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflow guidance including validation checkpoints and fallback paths. The main weaknesses are some unnecessary explanatory content (e.g., explaining what neoantigens are) and a monolithic structure that could benefit from splitting detailed reference material into separate files. The scope boundaries and error handling are particularly well-defined.
Suggestions
Remove the 'Function Overview' section explaining what neoantigens are - Claude already knows this domain knowledge
Extract the detailed 'Response Template' section to a separate RESPONSE_FORMAT.md file and reference it
Consider moving the 'Scoring Algorithms' and 'Algorithm Limitations' sections to a separate ALGORITHMS.md reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity, particularly in explaining what neoantigens are (Claude knows this), and the response template section is overly prescriptive. However, the core technical content is reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable command-line examples, Python API code, concrete input format specifications with examples, and specific scoring thresholds. The code is copy-paste ready and includes real parameter values. | 3 / 3 |
Workflow Clarity | Clear numbered workflow steps with explicit validation gates, fallback behavior with specific failure handling, and input validation as a hard gate before processing. The fallback section explicitly states what can still be completed when parts fail. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is monolithic with no references to external files for detailed content like algorithm documentation or extended examples. The response template section could be extracted to a separate reference. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
ca9aaa4
Table of Contents
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.