Your agent just wrote a custom PDF parser.

There were four maintained libraries that do exactly this. It didn't check. It never does.

This is the default behavior of every coding agent: task arrives → code is written → you maintain the bespoke solution forever.

skill-hunter is the missing pause.

What It Does

skill-hunter is a pre-execution layer for coding and automation agents. Before your agent writes a single line, it:

Classifies the request — what kind of task is this?

Scans the ecosystem — MCP servers, CLIs, npm/pip packages, APIs, GitHub repos, existing repo utilities

Scores candidates — fit, maintenance activity, permissions, security, docs quality, license, integration effort

Recommends a path — reuse, adapt, build minimally, or build custom

Gates risky actions — installs, credentials, external service connections, destructive ops require explicit approval

The agent checks the toolbox before building another hammer.

The Before / After

Without skill-hunter:

User: "Parse these PDFs and…