resolve-portals

Inspect careers pages to identify ATS providers and verify slugs via JSON APIs.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Capataina/Cernio --skill resolve-portals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-portals
Source: https://github.com/Capataina/Cernio/tree/main/.claude/skills/resolve-portals
Command: npx skills add https://github.com/Capataina/Cernio --skill resolve-portals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the gap between company discovery and job application by identifying and verifying the correct Applicant Tracking System (ATS) portal for companies that automated scripts cannot match.

Core Features & Use Cases

  • ATS Identification: Inspects careers pages to identify the underlying ATS provider (e.g., Greenhouse, Lever, Ashby, Workday).
  • API Verification: Validates ATS slugs against provider-specific JSON APIs to ensure they are active and functional.
  • Lifecycle Management: Transitions companies from potential status to resolved or bespoke, ensuring the database remains accurate and actionable.

Quick Start

Invoke the resolve portals skill to identify and verify the ATS portals for all companies currently marked as potential in the database.

Frequently Asked Questions about resolve-portals

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

FAQPage Schema
How do I verify ATS portal slugs against provider APIs?

You can verify ATS portal slugs by checking them against provider-specific JSON APIs to confirm they are active and functional. This validation ensures the Applicant Tracking System connectivity is accurate before transitioning company statuses in your database.

What is the best way to identify a company's ATS provider from their careers page?

Identifying an ATS provider involves inspecting a company's careers page for specific ATS markers. This process detects underlying systems like Greenhouse, Lever, Ashby, or Workday to resolve portals that automated discovery scripts fail to match.

How do I resolve unmatched Applicant Tracking System portals in my database?

Resolving unmatched ATS portals requires inspecting careers pages for ATS markers and validating slugs via provider JSON APIs. This transitions companies from potential status to resolved or bespoke, ensuring database integrity.

Can I automate job board portal resolution for companies with bespoke career sites?

Yes, you can automate portal resolution for companies with bespoke career sites. The process verifies ATS connectivity and transitions the company status to bespoke, ensuring the database remains accurate and actionable for job scraping.

Why do automated discovery scripts fail to match some ATS portals?

Automated discovery scripts fail to match ATS portals when companies use non-standard or bespoke career page implementations. Manual inspection of careers pages for ATS markers is required to identify the underlying provider and verify slug validity.