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
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/ai-dev-jobs-mcp/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and distinctiveness, clearly naming concrete actions and a well-defined domain. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The natural trigger terms are well-covered through the action descriptions themselves.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AI/ML job openings, tech job salaries, employer information, or career opportunities in artificial intelligence and machine learning.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: search jobs, inspect listings and employers, match roles, view salary and market stats. Also specifies the domain (AI and ML jobs) and scale (8,400+ jobs, 489 companies). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and domain, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the nature of the actions described. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'AI jobs', 'ML jobs', 'job search', 'salary', 'companies', 'listings', 'market stats', 'match roles'. These cover common variations of how users would ask about AI/ML job searching. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: AI/ML job searching via a specific MCP tool (AI Dev Jobs MCP). The combination of job search, AI/ML domain, salary stats, and the named MCP makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent MCP tool catalog skill that clearly documents available tools and their parameters, but suffers from redundancy between the Available Tools section and the Examples section. The time-sensitive statistics in the overview (specific counts, median salary, date) will become stale quickly. The skill would benefit from trimming repetitive content and showing actual response schemas rather than narrative descriptions of what the agent will do.
Suggestions
Remove or significantly condense the Examples section—each example merely restates the tool call already shown in Available Tools with a narrative wrapper. Instead, show one example with an actual response shape/schema.
Move the time-sensitive statistics ('8,405 active roles', '$213,500 median salary', 'April 17, 2026') out of the overview or note them as approximate/example values, since they will become stale and should be fetched live via get_stats.
Add example response schemas or sample JSON output for at least the most-used tools (search_jobs, get_job) so Claude knows what data shape to expect and can format results appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity: the overview paragraph with specific live stats (which are time-sensitive and will become stale), the 'When to Use This Skill' section explains obvious use cases Claude can infer, and the examples section is repetitive—each example just restates the tool call already shown in the Available Tools section with minimal added value. | 2 / 3 |
Actionability | Tool calls are shown with example parameters which is helpful, but they're not fully executable code—they use a pseudo-function-call syntax without specifying the actual MCP invocation mechanism. The examples section describes what 'the agent will call' rather than providing concrete input/output pairs showing actual response shapes. | 2 / 3 |
Workflow Clarity | For this type of skill (MCP tool catalog with independent, non-destructive read-only operations), there are no multi-step destructive workflows requiring validation checkpoints. The Best Practices section provides clear sequencing guidance (e.g., use list_companies then search_jobs, use get_stats before quoting numbers), which is appropriate for the skill's complexity. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no bundle files. The six examples could be trimmed or moved to a separate EXAMPLES.md since they largely duplicate the tool documentation. The Limitations and Best Practices sections are appropriately inline, but the overall document is longer than necessary for a tool catalog skill. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
22710e9
Table of Contents
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.