CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scrape

Finds new job postings matching your profile via installed portal-search CLIs (LinkedIn, local job boards, and any skills added with /add-portal). Deduplicates across runs. Triggers on: job scrape, find jobs, search jobs, new jobs, job search, scrape jobs, /scrape

Quality

81%

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

77%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.

The body is an exceptionally actionable, well-sequenced workflow with strong validation and error-recovery loops, but it carries noticeable rationale/narrative prose that inflates token cost, and it is a single long file that inlines reference-style material while pointing at support files not present in the bundle.

Suggestions

Move the seen_jobs.json field-by-field rationale (posted_date, employment_type, source, /rank extension fields) into a separate reference file (e.g. references/schema.md) and keep only the entry structure and the never-infer rules inline, cutting several hundred tokens from SKILL.md.

Trim design-justification narratives, such as the freehire-search 2024-05-13 anecdote in the posted_date paragraph, down to the operative rule; put time-stamped history in a changelog/old-patterns section if it must be kept.

Ship the referenced support files (search-queries.md, tools/job_key.py, tools/scrape_state.py) in the skill bundle, or restructure the inlined health-check and quoting-syntax detail into a references/ file so SKILL.md works as the overview it is meant to be.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational instruction, but multi-paragraph design-rationale prose (e.g. "That gap landed for real: a freehire-search posting dated 2024-05-13 was scraped and ranked Strong Fit at position 1 of 133...") and field-by-field justification blocks (posted_date, employment_type, source) explain why rather than what to do, and a specific historical date appears outside any deprecated/old-patterns section. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 'minor instances' of the level above.

3 / 5

Actionability

Commands are copy-paste ready ("python3 tools/scrape_state.py candidates --results \"<temporary search results.json>\"", "python3 tools/job_key.py --company \"<company>\" --title \"<title>\" --url \"<url>\"", "bun --version"), the seen_jobs.json entry schema is given as concrete JSON, and LinkedIn URL templates are exact, covering the common cases.

5 / 5

Workflow Clarity

Steps 0 through 6 are explicitly sequenced with validation checkpoints and error-recovery loops throughout: the candidates pre-check before detail fetches, the bounded Step 4.75 health-check escalation (probe, single retry, rate-limit handling), non-zero CLI exit handling ("log the error message and continue"), 403 retry via fetch_page.py, and the closed-at-source/expired-entry rules, plus an Important Rules checklist.

5 / 5

Progressive Disclosure

Section headers are clear and references are clearly signaled, but no bundle files exist in this skill (no references/, scripts/, or assets/), the referenced support files (search-queries.md, tools/scrape_state.py, tools/job_key.py) are not part of the provided bundle, and ~40 lines of schema/field documentation and health-check procedure are inlined in SKILL.md where a separate reference file would fit. This matches 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

16

/

20

Passed

Description

78%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 an explicit trigger clause, third-person voice, and a clearly stated mechanism, held back only by limited coverage of the skill's full capability set and a few missing natural trigger synonyms. It is concise and free of fluff.

DimensionReasoningScore

Specificity

"Finds new job postings matching your profile via installed portal-search CLIs" and "Deduplicates across runs" are two concrete actions, but the description omits other capabilities the skill performs (fit assessment, referral links, portal health checks), matching the '1-2 concrete actions, but not comprehensive' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

The description clearly answers 'what' ("Finds new job postings matching your profile via installed portal-search CLIs... Deduplicates across runs") and 'when' with an explicit "Triggers on:" clause listing concrete trigger phrases, exactly matching the top anchor; the missing-trigger cap does not apply.

5 / 5

Trigger Term Quality

"Triggers on: job scrape, find jobs, search jobs, new jobs, job search, scrape jobs, /scrape" gives good natural-phrase coverage with search/find/scrape synonyms, but common user phrasings like "openings", "positions", or "vacancies" are missing, so it sits at 'good keyword coverage; a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The portal-search-CLI niche and "job scrape"/"/scrape" triggers are distinct, but generic phrases like "find jobs" and "new jobs" carry minor overlap risk with closely related job-application skills in the same ecosystem (job-application-assistant, /rank), fitting 'mostly distinct; minor overlap risk' rather than the clear-niche anchor.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

MadsLorentzen/ai-job-search

Path

.claude/skills/job-scraper/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.