probe-contact

Diagnose contact extraction failures in résumé PDFs across parsing pipeline stages.

8|Updated May 29, 2026
One-click install
npx skills add https://github.com/offlinecv/OfflineCV --skill probe-contact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: probe-contact
Source: https://github.com/offlinecv/OfflineCV/tree/main/.claude/skills/probe-contact
Command: npx skills add https://github.com/offlinecv/OfflineCV --skill probe-contact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool identifies why specific contact fields like name, email, or phone numbers fail to extract from résumé PDFs, pinpointing whether the failure occurs during line assembly, section routing, or field-specific heuristic processing.

Core Features & Use Cases

  • Layered Diagnostics: Separates failures into line-assembly, section-routing, or field-heuristic categories.
  • Independent Verification: Performs a raw text re-scan to distinguish between parser misses and genuinely missing data.
  • Use Case: Use this when a candidate's contact information is missing or incorrect in the system to determine if the issue is a malformed PDF layout or a bug in the extraction logic.

Quick Start

Run the probe by executing the vitest command with the absolute path to your target PDF assigned to the RL_CONTACT_PDF environment variable.

Frequently Asked Questions about probe-contact

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

FAQPage Schema
How do I debug contact information extraction failures from résumé PDFs?

To debug résumé PDF contact extraction failures, you run a diagnostic probe that analyzes the parsing pipeline across line assembly, section routing, and field heuristics to pinpoint the exact root cause of data loss.

Why does my résumé parser miss email addresses and phone numbers in PDF files?

Your résumé parser misses email addresses and phone numbers due to failures in line assembly, section routing, or field-specific heuristics, which a diagnostic probe can localize and identify for targeted fixes.

How do I run a PDF parsing diagnostic test using vitest?

To run the PDF parsing diagnostic using vitest, execute the vitest command with the RL_CONTACT_PDF environment variable set to the absolute file path of your target résumé PDF document.

Can I distinguish between a malformed PDF layout and a bug in my extraction logic?

Yes, you can distinguish between a malformed PDF layout and an extraction logic bug by performing an independent raw text re-scan, which verifies whether the contact data genuinely exists or was missed by the parser.

Do I need a local PDF file path to diagnose résumé contact parsing issues?

Yes, you need a local PDF file path assigned to the RL_CONTACT_PDF environment variable to execute the diagnostic harness and analyze the contact parsing pipeline for extraction failures.

What is the best way to triage missing candidate contact fields from parsed resumes?

The best way to triage missing candidate contact fields is using a layered diagnostic approach that separates failures into line-assembly, section-routing, or field-heuristic categories for precise root cause identification.