v32-multi-direction-scan

Scans PubMed and OpenAlex across rotation research directions to detect white-space literature gaps.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill v32-multi-direction-scan-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: v32-multi-direction-scan
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/extended/research-tools/synthos-akne-bridge/v32-multi-direction-scan
Command: npx skills add https://github.com/yakeworld/Synthos --skill v32-multi-direction-scan-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Autonomous research pipelines need a repeatable way to check whether candidate research directions already have competing PINN/ODE literature before investing in gap analysis. This Skill standardizes multi-direction literature scanning across PubMed and OpenAlex so each cron run produces consistent, scored scan results. ## Core Features & Use Cases - Multi-Direction Scanning: Executes PubMed targeted queries plus OpenAlex broad/cited queries across 5 rotation and 5 new exploration directions per run. - Resilient API Access: Uses a Python urllib-based utility (scripts/pubmed_utils.py) with automatic retry, BOM stripping, and JSON resilience to handle NCBI eUtils instability and environments where curl is blocked by security scanners. - Scoring and State Tracking: Applies a scoring matrix (START/CANDIDATE/POSTPONE) and updates research state files with candidate status, gate results, and staleness detection between parent queues and candidate state files. - Use Case: A scheduled autonomous research agent runs this scan each cycle to confirm which vestibular/oculomotor modeling directions remain ABSOLUTE_WHITE (no PINN/ODE competitors) before queuing them for gap analysis. ## Quick Start Ask the agent to run the v32 multi-direction scan over the five rotation directions using scripts/pubmed_utils.py and report each direction's status and score.

Frequently Asked Questions about v32-multi-direction-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan PubMed and OpenAlex for competing literature?

Run targeted PubMed queries plus broad OpenAlex queries for each research direction using the pubmed_count and openalex_search functions in scripts/pubmed_utils.py. Zero PINN/ODE hits across both sources indicates an ABSOLUTE_WHITE gap.

How to query PubMed when curl is blocked by security scanners?

Use Python's urllib through scripts/pubmed_utils.py instead of curl. Requests originating from a Python process do not trigger shell-pipeline scanners, and the module includes automatic retry and JSON resilience for NCBI eUtils endpoints.

What scoring decides whether a research direction proceeds to gap analysis?

Directions scoring 24 or higher with feasibility of at least 3 get START status, scores of 18-23 become CANDIDATE, and anything below 18 is POSTPONE. Results are recorded in the research_scan field of the state file.

Why do PubMed queries fail intermittently with NCBI eUtils?

NCBI eUtils endpoints like eFetch and esummary are intermittently unreliable, returning 502/503/504 errors or malformed JSON. The utility retries up to 5 times with delays and strips BOM or preamble bytes before parsing.

What are the limitations of abbreviation-based literature queries?

Abbreviations like VCR collide with unrelated domains such as viral clearance rate and vaccine coverage rate. Always use full domain terms and query all known name variants to avoid missing or misclassifying literature.