How do I install the Archive Pids skill?

Run npx skillmds add vimalinx/archive-pids 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 Archive Pids 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 Archive Pids?

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 Archive Pids free to use?

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

Who published Archive Pids?

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

Archive Pids by vimalinx — Agent Skill

Name: Archive Pids
Rating: 4.5 (4 reviews)
Author: vimalinx

File contents

archive-pids

Quick Start

Command: archive-pids [daily|-index]
Local executable: /home/vimalinx/miniforge3/envs/bio/bin/archive-pids
Full reference: See references/help.md for complete documentation

When To Use This Tool

Build a local postings archive for the PubMed PMCID field.
Support offline PMID-to-PMCID style lookups inside a populated local EDirect archive.
Refresh the PMCID posting data after PubMed metadata updates.
Keep this identifier crosswalk in the same archive layout used by the rest of the PubMed local-data tools.

Common Patterns

# 1) Refresh the local PMCID postings archive
export EDIRECT_LOCAL_ARCHIVE=/data/edirect
archive-pids

# 2) Rebuild incremental index and invert layers after a refresh
archive-pids daily

# 3) Rebuild merged postings for downstream local queries
archive-pids -index

Recommended Workflow

Set EDIRECT_LOCAL_ARCHIVE and verify the target archive tree is writable.
Confirm pm-setup, pm-prepare, and the local Go toolchain are available.
Run archive-pids to refresh the underlying PMCID data.
Follow with daily or -index as a separate maintenance command when you need refreshed postings.
Check the timing summary before assuming the archive is ready for local identifier lookups.

Guardrails

--help and --version are not safe here; they still execute archive setup and prerequisite checks.
The script depends on EDIRECT_LOCAL_ARCHIVE, pm-setup, pm-prepare, and a working local go compiler.
Cleaning and indexing must be separate commands.
Cleanup aliases remove local scratch content, so treat them as destructive maintenance.
This tool is for building the local PMCID postings archive, not for extracting a one-off ID list from stdin.

---name: archive-pidsdescription: Use when maintaining a local PubMed-to-PMCID postings archive for offline identifier crosswalks in EDirect workflows.--- # archive-pids ## Quick Start - **Command:** `archive-pids [daily|-index]` - **Local executable:** `/home/vimalinx/miniforge3/envs/bio/bin/archive-pids` - **Full reference:** See [references/help.md](references/help.md) for complete documentation ## When To Use This Tool - Build a local postings archive for the PubMed `PMCID` field. - Support offline PMID-to-PMCID style lookups inside a populated local EDirect archive. - Refresh the PMCID posting data after PubMed metadata updates. - Keep this identifier crosswalk in the same archive layout used by the rest of the PubMed local-data tools. ## Common Patterns ```bash # 1) Refresh the local PMCID postings archive export EDIRECT_LOCAL_ARCHIVE=/data/edirect archive-pids ``` ```bash # 2) Rebuild incremental index and invert layers after a refresh archive-pids daily ``` ```bash # 3) Rebuild merged postings for downstream local queries archive-pids -index ``` ## Recommended Workflow 1. Set `EDIRECT_LOCAL_ARCHIVE` and verify the target archive tree is writable. 2. Confirm `pm-setup`, `pm-prepare`, and the local Go toolchain are available. 3. Run `archive-pids` to refresh the underlying PMCID data. 4. Follow with `daily` or `-index` as a separate maintenance command when you need refreshed postings. 5. Check the timing summary before assuming the archive is ready for local identifier lookups. ## Guardrails - `--help` and `--version` are not safe here; they still execute archive setup and prerequisite checks. - The script depends on `EDIRECT_LOCAL_ARCHIVE`, `pm-setup`, `pm-prepare`, and a working local `go` compiler. - Cleaning and indexing must be separate commands. - Cleanup aliases remove local scratch content, so treat them as destructive maintenance. - This tool is for building the local PMCID postings archive, not for extracting a one-off ID list from stdin.

Frequently asked questions