ai-dev-jobs-mcp

Search 8,400+ AI and ML jobs across 489 companies, inspect listings and employers, match roles, and view salary and market stats via AI Dev Jobs MCP

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete, copy-paste-ready tool invocations and a complete MCP configuration, organized into clean navigable sections appropriate for a simple MCP skill. The main drag on conciseness is the redundant Examples section that duplicates the tool calls already shown, plus a time-sensitive stat that will go stale.

Suggestions

Trim the six 'Examples' blocks that restate tool calls already shown in 'Available Tools', keeping at most 1-2 non-obvious examples such as the match_jobs or get_salary_data workflows.

Move or qualify the time-sensitive '8,405 active roles... $213,500 median salary' figure so it is clearly framed as live data rather than hard-coded facts, matching the Limitations note about refreshing get_stats.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with lean tool definitions and examples, but the six near-identical 'Use @ai-dev-jobs-mcp...' example blocks restate the tool calls already shown in 'Available Tools', and the time-sensitive '8,405 active roles... April 17, 2026' figure adds padding that will go stale.	2 / 3
Actionability	Each tool ships with a concrete, copy-paste-ready invocation (e.g. `search_jobs({ query: "machine learning engineer", location: "remote" })`), and the MCP config block is complete and executable with a real endpoint.	3 / 3
Workflow Clarity	This is a simple single-task skill with unambiguous one-call tool usage, which can score 3 per the simple-skills note; 'Best Practices' sequences multi-tool patterns (discover via list_companies, then search by company) and the Limitations section flags refreshing get_stats before quoting live figures.	3 / 3
Progressive Disclosure	For a sub-50-section skill with no external bundle files needed, the body is well-organized into clearly labeled sections (Overview, When to Use, MCP Configuration, Available Tools, Examples, Best Practices, Limitations, Related Skills) with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, naming four concrete capabilities in third person. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness, and slightly thin coverage of common user phrasings.

Suggestions

Add an explicit trigger clause, e.g. 'Use when searching for AI/ML jobs, researching hiring companies, or analyzing the AI labor market.'

Broaden trigger terms to include natural phrasings users actually say: 'job search', 'recruiting', 'hiring companies', 'job listings'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Search... jobs', 'inspect listings and employers', 'match roles', and 'view salary and market stats' — each a distinct, specific capability rather than vague language.	3 / 3
Completeness	Clearly states what the skill does, but there is no explicit 'Use when...' trigger clause; the 'when' is only implied by the domain, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Contains natural terms like 'AI and ML jobs', 'jobs', 'salary', and 'market stats' that users would say, but misses common variations such as 'job search', 'recruiting', 'hiring', or 'job listings' that the body itself uses.	2 / 3
Distinctiveness Conflict Risk	The niche (live AI/ML job index via a specific MCP) is clear and distinct with specific triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 2aaaf59

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.