linkedin-scraper

Get LinkedIn profiles, company pages, and posts

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/social/capabilities/linkedin-scraper/SKILL.md

Quality

Content

67%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 skill body is well-structured and actionable with concrete YAML operation specs and clear error-handling guidance. Its main weakness is redundancy around the URL-as-query-parameter instruction and a slightly vague runtime-selection step in Setup.

Suggestions

State the 'full LinkedIn URL as the query parameter' rule once (e.g. in Parameters) and remove the duplications in the Note and Tips to improve conciseness.

Make the runtime-selection step concrete by showing the actual MCP/CLI invocation or naming the exact command, rather than describing three options abstractly.

Show a trimmed example of the parsed response fields inline so the Response section reads as actionable output rather than a description.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the 'use full LinkedIn URLs as the query parameter' instruction is repeated in the Note, the Usage examples, and the Tips, and the Setup runtime-selection paragraph plus the redundant 'Scrape public LinkedIn data...' line add padding that could be trimmed, matching anchor 3 rather than 4.	3 / 5
Actionability	Each operation has a concrete, copy-paste YAML spec with provider, method, path, and a real example URL, covering the three common cases; it falls just short of anchor 5 only because response-shape details are described rather than shown as parseable output.	4 / 5
Workflow Clarity	The read-only single-call workflow is clearly laid out (read scrapecreators-api, pick a runtime, call the endpoint) with an Error Handling section giving retry guidance; since these are non-destructive, non-batch GETs the missing-validation cap does not apply, but the runtime-selection branching is left slightly implicit, holding it at 4 rather than 5.	4 / 5
Progressive Disclosure	The body is well-organized into clearly labeled sections and points one level deep to the sibling scrapecreators-api skill rather than nesting references; with no bundle files present this is good structure with minor organization gaps (anchor 4), not the lean overview-plus-references that would earn 5.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is specific and well-targeted to a clear LinkedIn niche, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Tightening the action verbs and adding a 'Use when...' clause would raise the score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about a LinkedIn profile, company page, or post.'

Replace the generic 'Get' with more concrete verbs (e.g. 'Retrieve and parse LinkedIn profiles, company pages, and posts') to lift specificity.

Include a natural synonym such as 'look up' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the LinkedIn domain and three concrete targets ("profiles, company pages, and posts"), but relies on a single generic action verb ("Get") rather than listing multiple distinct concrete actions, so it sits at the 3-anchor (not comprehensive) rather than 4.	3 / 5
Completeness	It gives a clear 'what' ("Get LinkedIn profiles, company pages, and posts") but includes no 'Use when...' trigger clause, so per the missing-trigger cap it cannot exceed anchor 3.	3 / 5
Trigger Term Quality	"LinkedIn profiles, company pages, and posts" covers the natural terms users say, but a few common phrasings (e.g. "look up", "LinkedIn profile") are absent, placing it at good-but-not-comprehensive coverage (anchor 4) rather than 5.	4 / 5
Distinctiveness Conflict Risk	The LinkedIn-specific niche with distinct object types (profiles, company pages, posts) gives minimal overlap with other skills, matching the anchor 5 example of a clear niche with distinct triggers.	5 / 5
	Total	15 / 20 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: gooseworks-ai/goose-skills
Path: skills/social/capabilities/linkedin-scraper/SKILL.md
Commit: 2523432

Reviewed: 5 days 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.