CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitor-trial-monitor

Monitor competitor clinical trial progress and alert on market risks.

Quality

63%

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/Evidence Insight/competitor-trial-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 operational core — CLI commands, parameter tables, alert rules, data storage, and a fallback-aware workflow — is genuinely actionable and executable. However, the file is bloated with duplicated sections, circular self-references, contradictory dependency statements, and generic template boilerplate that waste context and confuse setup.

Suggestions

Remove the circular "See `## Features`/`## Usage`/`## Workflow` above" filler and merge the duplicated Key Features/Features and Example Usage/Usage sections into single occurrences.

Resolve the dependency contradiction: the script uses only stdlib urllib, so delete the "pip install requests python-dateutil" block (or the contradicting Prerequisites section), and state one authoritative setup step.

Move the generic Risk Assessment, Security Checklist, Evaluation Criteria, and Lifecycle Status template sections into references/ (or delete them) so SKILL.md stays a lean overview with well-signaled, one-level-deep references, and add one example of expected command output.

DimensionReasoningScore

Conciseness

The body is noticeably padded: circular filler lines ("See `## Features` above", "See `## Usage` above", "See `## Workflow` above"), duplicated Features/Usage sections, and generic template boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add no task-specific knowledge. It avoids score 1 because the core CLI reference, parameter tables, and alert rules are dense and non-redundant.

2 / 5

Actionability

Concrete executable commands with realistic arguments ("python scripts/main.py add --nct NCT05108922 --company \"Pfizer\" ..."), complete parameter tables, storage paths, and a config example make the guidance mostly copy-paste ready. Not 5 because no expected output is shown for any command, and the Dependencies section ("pip install requests python-dateutil") directly contradicts Prerequisites ("No additional Python packages required") and the script's stdlib-only urllib implementation, leaving setup ambiguous.

4 / 5

Workflow Clarity

The Workflow section gives a clear sequence with checkpoints: validate scope before work, "stop early if the task would require unsupported assumptions", a py_compile quick check, and an explicit fallback path on failure. Not 5 because the checkpoints are generic template language rather than task-specific validation (e.g., NCT ID format checks, API response verification), and error-recovery loops are described only abstractly.

4 / 5

Progressive Disclosure

The single reference (references/audit-reference.md) is real, one level deep, and clearly signaled, and the packaged script path is accurate — but nearly all operational detail (alert rules, config, storage layout, security checklist, evaluation criteria) is inlined in SKILL.md, and the circular "See ## X above" pointers degrade navigation. Some structure, but organization could be materially better — anchor 3.

3 / 5

Total

13

/

20

Passed

Description

53%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 a concise, correctly third-person statement with a clear 'what' and a distinct niche, but it reads more like a title than a skill description: no 'when to use' trigger clause, no milestone-level specifics, and no keyword variations. It lands squarely at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. "Use when tracking competitor pharma trial milestones, scanning ClinicalTrials.gov/EU CTR/WHO ICTRP for status changes, or preparing competitive-risk alerts."

Name the concrete actions the skill performs (add/list/remove watched NCT IDs, scan registries for enrollment/unblinding/results/approval events, generate a time-boxed risk report) to lift specificity.

Include natural synonyms such as "clinical trial tracking", "competitive intelligence", and "pharma competition" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Monitor competitor clinical trial progress and alert on market risks" names the domain plus two actions, matching the anchor for 1-2 concrete actions without comprehensive coverage (no milestone-level actions like enrollment tracking or approval alerts are mentioned). It is not 4 because only two generic actions appear with no specifics about what is monitored or alerted on.

3 / 5

Completeness

The 'what' is clear (monitor trial progress, alert on risks) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Relevant natural keywords exist ("clinical trial", "competitor", "market risks") but common variations and synonyms users would say are missing ("track trials", "competitive landscape", "pharma", "NCT"). Fits anchor 3: some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

"Competitor clinical trial progress" defines a fairly clear niche, but the description could also fire for a general clinical-trial search or pharma news-monitoring skill since no competitive-intelligence framing beyond the word 'competitor' distinguishes it. Mostly distinct with minor overlap risk — anchor 4; not 5 because it lacks the concrete trigger phrases that would fully separate it from adjacent skills.

4 / 5

Total

13

/

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/Evidence Insight/competitor-trial-monitor/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.