CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-structured CLI reference that is fully executable and easy to navigate. The only trims needed are the forker-oriented meta commentary and slightly more failure-handling guidance.

DimensionReasoningScore

Conciseness

The command reference is efficient with every flag documented tersely, but the forker-oriented meta blockquote ("country-agnostic worked example of the repo's job-portal-skill pattern") and intro lines restating the description are minor over-explanations that could be trimmed.

4 / 5

Actionability

Fully executable copy-paste commands with complete flag documentation, five worked examples covering common cases, an output-format table, and a documented error contract (stderr JSON with code, exit 1) — matching the top anchor.

5 / 5

Workflow Clarity

The simple two-command flow (search → pass numeric ID to detail) is unambiguous and error behavior is documented, but there is no explicit guidance on what to do when a command fails (e.g., rate-limit handling beyond the built-in retry).

4 / 5

Progressive Disclosure

A well-organized, self-contained single file with clear sections where nothing belongs in a separate file; it sits above the under-50-line simple-skill threshold and offers no overview-to-reference split, keeping it just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

87%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 description with explicit what/when guidance and an exhaustive natural trigger-phrase list. Its main weakness is that it never names LinkedIn, making it indistinguishable from sibling job-portal skills in the same repo.

Suggestions

Mention LinkedIn explicitly (e.g., "Search live job listings from LinkedIn's public job board") so this skill is distinguishable from other job-portal skills sharing the same trigger phrases.

Add the filtering capabilities (recency windows, remote/hybrid/onsite) as concrete actions to close the coverage gap in specificity.

DimensionReasoningScore

Specificity

Names three concrete actions — "search for jobs in any location or market, find job listings, or look up a specific job posting" — matching the several-specific-actions anchor with minor gaps (recency/workplace-type filtering and full-detail fetching from the body are not mentioned).

4 / 5

Completeness

Explicitly answers both what ("search for jobs... find job listings, or look up a specific job posting") and when ("Use this skill whenever the user wants to..." plus a concrete trigger-phrase list), matching the anchor that requires concrete trigger phrases.

5 / 5

Trigger Term Quality

The explicit trigger list — "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" — gives comprehensive natural-phrase coverage including synonyms, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The job-search niche is distinct from general skills, but the description never mentions LinkedIn, so every trigger ("find a job", "job search", "vacancies") is generic across job-portal skills — the body itself notes the repo follows a multi-portal skill pattern, creating real overlap risk.

3 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.