How do I install the Expand Current skill?

Run npx skillmds add vimalinx/expand-current in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Expand Current safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Expand Current?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Expand Current free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Expand Current?

vimalinx (@vimalinx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Expand Current by vimalinx — Agent Skill

Name: Expand Current
Rating: 4.666666666666667 (3 reviews)
Author: vimalinx

File contents

expand-current

CLI tool for expanding and indexing current PubMed archive files for local EDirect operations.

Quick Start

Command: EDIRECT_LOCAL_ARCHIVE=/path/to/local/archive PATH=/home/vimalinx/miniforge3/envs/bio/bin:$PATH /home/vimalinx/miniforge3/envs/bio/bin/expand-current
Local executable: /home/vimalinx/miniforge3/envs/bio/bin/expand-current
Full reference: See references/help.md for complete documentation

When To Use This Tool

Refresh the local Current PubMed archive inside an EDirect local archive installation.
Expand *.xml.gz current-archive files into indexed XML and rebuild derived merged / indexed / inverted layers.
Maintain a local offline-style PubMed archive workflow after new archive content arrives.

Common Patterns

# 1) Expand and rebuild the current local PubMed archive
EDIRECT_LOCAL_ARCHIVE=/data/edirect-archive \
PATH=/home/vimalinx/miniforge3/envs/bio/bin:$PATH \
  /home/vimalinx/miniforge3/envs/bio/bin/expand-current

# 2) Run inside a maintenance script after archive synchronization
export EDIRECT_LOCAL_ARCHIVE=/data/edirect-archive
export PATH=/home/vimalinx/miniforge3/envs/bio/bin:$PATH
/home/vimalinx/miniforge3/envs/bio/bin/expand-current

Recommended Workflow

Confirm EDIRECT_LOCAL_ARCHIVE resolves to a real local archive tree before running anything.
Make sure companion commands such as rchive, pm-collect, and xtract are available.
Run expand-current during a maintenance window, because it deletes previous derived index files before rebuilding them.
Verify that fresh XML files and rebuilt index layers exist before pointing downstream local queries at the archive.

Guardrails

This is an operational maintenance script, not a safe metadata probe.
It deletes prior *.e2x*, *.inv*, and *.mrg* files under the derived archive layers before rebuilding them.
In the current environment, a missing EDIRECT_LOCAL_ARCHIVE or missing helpers such as pm-collect can still lead to noisy partial execution and a final EXIT 0, so pre-flight checks matter.
Sufficient disk space is required because compressed current-archive XML is expanded into plain XML during the rebuild.

---name: expand-currentdescription: Use when expanding and rebuilding the local EDirect PubMed `Current` archive plus its derived index layers.--- # expand-current CLI tool for expanding and indexing current PubMed archive files for local EDirect operations. ## Quick Start - **Command**: `EDIRECT_LOCAL_ARCHIVE=/path/to/local/archive PATH=/home/vimalinx/miniforge3/envs/bio/bin:$PATH /home/vimalinx/miniforge3/envs/bio/bin/expand-current` - **Local executable**: `/home/vimalinx/miniforge3/envs/bio/bin/expand-current` - **Full reference**: See [references/help.md](references/help.md) for complete documentation ## When To Use This Tool - Refresh the local `Current` PubMed archive inside an EDirect local archive installation. - Expand `*.xml.gz` current-archive files into indexed XML and rebuild derived merged / indexed / inverted layers. - Maintain a local offline-style PubMed archive workflow after new archive content arrives. ## Common Patterns ```bash # 1) Expand and rebuild the current local PubMed archive EDIRECT_LOCAL_ARCHIVE=/data/edirect-archive \ PATH=/home/vimalinx/miniforge3/envs/bio/bin:$PATH \ /home/vimalinx/miniforge3/envs/bio/bin/expand-current ``` ```bash # 2) Run inside a maintenance script after archive synchronization export EDIRECT_LOCAL_ARCHIVE=/data/edirect-archive export PATH=/home/vimalinx/miniforge3/envs/bio/bin:$PATH /home/vimalinx/miniforge3/envs/bio/bin/expand-current ``` ## Recommended Workflow 1. Confirm `EDIRECT_LOCAL_ARCHIVE` resolves to a real local archive tree before running anything. 2. Make sure companion commands such as `rchive`, `pm-collect`, and `xtract` are available. 3. Run `expand-current` during a maintenance window, because it deletes previous derived index files before rebuilding them. 4. Verify that fresh XML files and rebuilt index layers exist before pointing downstream local queries at the archive. ## Guardrails - This is an operational maintenance script, not a safe metadata probe. - It deletes prior `*.e2x*`, `*.inv*`, and `*.mrg*` files under the derived archive layers before rebuilding them. - In the current environment, a missing `EDIRECT_LOCAL_ARCHIVE` or missing helpers such as `pm-collect` can still lead to noisy partial execution and a final `EXIT 0`, so pre-flight checks matter. - Sufficient disk space is required because compressed current-archive XML is expanded into plain XML during the rebuild.

Frequently asked questions