pipeline

Process pending job posting URLs into scored reports, PDFs, and tracker entries.

Updated May 21, 2026
One-click install
npx skills add https://github.com/wahajahmed010/openclaw-skills --skill pipeline-wahajahmed010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/wahajahmed010/openclaw-skills/tree/main/skills/career-ops/skills/pipeline
Command: npx skills add https://github.com/wahajahmed010/openclaw-skills --skill pipeline-wahajahmed010

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

It eliminates the manual grind of reviewing pending job posting links and converting each one into consistent scores, reports, and application tracker entries.

Core Features & Use Cases

  • URL Inbox Processing: Reads a pipeline inbox, finds pending entries, and processes each posting in sequence while maintaining structured status markers.
  • Job Description Extraction & Scoring Pipeline: Extracts JD content using Playwright/WebFetch/WebSearch and runs an A–G evaluation workflow to generate a decision-ready report.
  • Report/PDF + Tracker Automation: Creates the next sequential report number, generates a PDF when the score threshold is met, and writes the outcome into the applications tracker.

Quick Start

Ask it to process the pipeline inbox and generate the next batch of scored reports and tracker updates for all pending job URLs, skipping any that require login with an actionable note.

Frequently Asked Questions about pipeline

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

FAQPage Schema
How do I automate job posting URL processing to generate scored reports?

To automate job posting URL processing, this Skill fetches pending links, extracts job descriptions using Playwright or WebFetch, and applies an A–G rubric to generate scored evaluation reports and tracker entries automatically.

What happens to login-gated URLs during web scraping for job descriptions?

Login-gated URLs are handled safely by skipping them during web scraping. The pipeline marks inaccessible job posting links with an actionable note in the tracker output rather than failing the extraction.

Can I use Playwright and WebFetch together for job description extraction?

You can use Playwright, WebFetch, and WebSearch together for job description extraction. The pipeline attempts Playwright first, falls back to WebFetch, then WebSearch to ensure robust content retrieval before scoring.

How do I generate PDFs and tracker entries from job application workflows?

To generate PDFs and tracker entries, the pipeline processes pending URLs, applies an A–G score threshold, creates the next sequential report number, outputs a PDF, and writes the outcome into the designated applications tracker path.

Does pipeline inbox processing require checking sync states before extracting job descriptions?

Pipeline inbox processing requires checking sync states via the cv-sync-check script before extracting job descriptions. The workflow reads pipeline.md pending and processed states to maintain structured status markers and sequential reporting numbers.

Why is my job description extraction not working for certain URLs?

Job description extraction fails when URLs are login-gated or inaccessible. The pipeline handles these safely by skipping the posting and logging an actionable note, ensuring the scoring workflow continues processing remaining pending entries without interruption.