Ext Ops Panel
Open dashboard
Comparison

job-assistant vs ATS Engine

job-assistant is a plugin bundle for AI coding tools published by imfelixkim. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ATS Engine is an MCP server published by VeriWorkly. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacejob-assistantATS Engine
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.0
Downloads/month (npm): 1 255
Downloads/week (npm): 1 255
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

job-assistant vs ATS Engine
Factjob-assistantATS Engine
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)Not published2026-10-15
Where it runs (differs)Installs as a plugin bundleOn your machine (@veriworkly/ats-engine-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/imfelixkim/job_assistantgithub.com/veriworkly/ats-engine
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

job-assistant

In its own words, on Claude Code: claude-plugins-community:

Analyze job postings and optimize your resume with an 11-step interactive workflow. The plugin conducts company research, structures job requirements, performs gap analysis between your resume and the posting, optimizes your resume for ATS keywords, and delivers a 4-perspective review (practitioner, recruiter, HR, CEO). Includes 8 specialized agents and 3 skills. Supports Korean job market with privacy-first design (personal info masking throughout the process).

ATS Engine

In its own words, on Official MCP Registry:

Read your own resume the way an ATS does and score it with a published, deterministic rubric.

How to run each

job-assistant As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install job-assistant@claude-community

ATS Engine As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ats-engine -- npx -y @veriworkly/ats-engine-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of ATS Engine publish no settings it asks for, so we do not compare settings.

What it can do: job-assistant · What it can do: ATS Engine · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built