linkedin-search

Use this skill whenever the user wants to search for jobs in any location or market, find job listings, or look up a specific job posting — in any country, city, or remotely. Invoke for open positions, vacancies, and hiring across any sector or role (software, data, design, marketing, finance, legal, operations, etc.). The location is always supplied explicitly by the user. Trigger phrases: find a job, job search, search for jobs, job openings, vacancies, hiring, positions open, remote jobs, "are there any X jobs in <place>", look up this job posting.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

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

A tight, highly actionable CLI skill body with concrete commands and examples and a clear search→detail flow. Minor conciseness redundancy and a lack of any reference split keep it just short of maximum.

Suggestions

Merge the intro paragraph and the blockquote that both explain country-agnostic/no-auth behavior into a single concise statement to remove redundancy.

Consider moving the full flag reference into a separate REFERENCE.md (one level deep) to slim the main body while keeping the quick-start examples inline.

Add a one-line explicit workflow note ('Run search to get job IDs, then pass an ID to detail') to make the two-command sequence unambiguous at a glance.

Dimension	Reasoning	Score
Conciseness	Lean and free of concept-explaining fluff, but the intro paragraph and the following blockquote redundantly restate the 'country-agnostic / no-auth / location-passed-explicitly' message, which could be consolidated.	4 / 5
Actionability	Fully executable copy-paste commands with the complete script path, documented flags, and five worked examples covering query, location, remote, jobage, and detail lookups.	5 / 5
Workflow Clarity	A simple read-only skill where the search→detail sequence is made explicit ('id is the job ID from search results'); the simple-skill exception applies and no destructive/batch validation cap is triggered.	5 / 5
Progressive Disclosure	Well-organized into clear sections (when-to-use, commands, examples, formats, notes) with no bundle files to navigate, though at ~100 lines all content is inline with no separation of the reference-style flag table.	4 / 5
	Total	18 / 20 Passed

Description

96%Weight 40%Scale 1-5

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

A strong, trigger-rich description that explicitly states capabilities and when to invoke, with comprehensive natural-language trigger phrases. Only slight distinctiveness ambiguity from not naming the source portal.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'search for jobs', 'find job listings', 'look up a specific job posting' — across any sector/role, giving comprehensive coverage rather than a single generic action.	5 / 5
Completeness	Explicitly answers both 'what' (search/find/look up job postings across locations and sectors) and 'when' ('Use this skill whenever the user wants to search for jobs...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit trigger phrases cover natural synonyms users would say: 'find a job, job search, search for jobs, job openings, vacancies, hiring, positions open, remote jobs', including a templated natural query form.	5 / 5
Distinctiveness Conflict Risk	Clear job-search niche with distinct triggers, but the description does not name LinkedIn specifically, leaving minor overlap risk with sibling job-portal skills that share the same trigger vocabulary.	4 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: MadsLorentzen/ai-job-search
Path: .agents/skills/linkedin-search/SKILL.md
Commit: 5c423b4

Reviewed: about 9 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.