Monitor and summarize competitor clinical trial status changes from ClinicalTrials.gov.
62%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./scientific-skills/Evidence Insight/clinicaltrials-gov-parser/SKILL.mdMonitor and summarize competitor clinical trial status changes from ClinicalTrials.gov.
Use this command to verify that the packaged script entry point can be parsed before deeper execution.
python -m py_compile scripts/main.pyUse these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.
python -m py_compile scripts/main.py
python scripts/main.py --help| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
--sponsor | string | - | No | Trial sponsor name |
--condition | string | - | No | Medical condition/disease |
--status | string | - | No | Trial status (Recruiting, Completed, etc.) |
--trials | string | - | No | Comma-separated trial IDs (NCT numbers) |
--output | string | json | No | Output format (json, csv) |
--days | int | 30 | No | Number of days for monitoring |
from scripts.main import ClinicalTrialsMonitor
# Initialize monitor
monitor = ClinicalTrialsMonitor()
# Search for trials
trials = monitor.search_trials(
sponsor="Pfizer",
condition="Diabetes",
status="Recruiting"
)
# Get trial details
trial = monitor.get_trial("NCT05108922")
# Check for status changes
changes = monitor.check_status_changes(trial_ids=["NCT05108922"])# Search trials
python scripts/main.py search --sponsor "Pfizer" --condition "Diabetes"
# Get trial details
python scripts/main.py get NCT05108922
# Monitor status changes
python scripts/main.py monitor --trials NCT05108922,NCT05108923 --output json
# Generate summary report
python scripts/main.py report --sponsor "Pfizer" --days 30| Method | Description |
|---|---|
search_trials() | Search trials with filters |
get_trial(nct_id) | Get detailed trial information |
check_status_changes() | Check for status updates |
get_recruitment_status() | Get enrollment updates |
generate_summary() | Generate competitor summary |
references/api-docs.md for API documentationreferences/status-codes.md for trial status definitionsreferences/examples.md for usage examples| Risk Indicator | Assessment | Level |
|---|---|---|
| Code Execution | Python scripts with tools | High |
| Network Access | External API calls | High |
| File System Access | Read/write data | Medium |
| Instruction Tampering | Standard prompt guidelines | Low |
| Data Exposure | Data handled securely | Medium |
# Python dependencies
pip install -r requirements.txtEvery final response should make these items explicit when they are relevant:
scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.This skill accepts requests that match the documented purpose of clinicaltrials-gov-parser and include enough context to complete the workflow safely.
Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:
clinicaltrials-gov-parseronly handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
Use the following fixed structure for non-trivial requests:
If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
| Field | Required | Format/Source | Example | If Missing |
|---|---|---|---|---|
| User task description | Yes | Text | Research question, writing goal, analysis objective | Stop and ask user to provide |
| Primary input material | Depends on task | Text, file path, ID, table, or literature | PMID, PDF, CSV, DOCX, keywords, etc. | Specify which material type is missing |
| Output preference | No | Text | Language, format, target journal, template | Use skill default format |
aipoch/medical-research-skills
686e09d
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.