linkedin-profile-post-scraper

Scrape recent posts from LinkedIn profiles using Apify. Use when you need to monitor what specific people are posting on LinkedIn, track founder/exec activity, or gather LinkedIn content for competitive intelligence.

Quality

88%

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

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

Excellent, tight content for a simple single-purpose skill: executable commands, a complete CLI reference, cost transparency, and honest caveats, with the implementation properly externalized to the bundled script. The only gap is the absence of verification guidance for batch multi-profile runs (empty results, timeouts, token failures).

Dimension	Reasoning	Score
Conciseness	The ~44-line body is lean and assumes Claude's competence: three executable commands, a CLI flag table, a one-line cost note, and two caveats — no padding and no explanation of concepts Claude already knows. Nothing could be cut without losing information.	5 / 5
Actionability	Fully executable, copy-paste-ready commands covering the common cases (single profile, multi-profile with keyword/date filtering, summary output), plus a complete flag reference with defaults and a cost estimate. The referenced script exists in the bundle and its flags match the documented CLI.	5 / 5
Workflow Clarity	The single action (run the script) is unambiguous with concrete commands, but the skill supports batch runs over multiple profiles with no verification guidance — nothing on handling empty results, timeouts, or partial profile failures. It is not a 3 because the one-step workflow is clear and the operation is read-only; it is not a 5 because those minor validation gaps exist.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references; well-organized sections (Quick Start, CLI Reference, Cost, Notes) and the implementation correctly split into scripts/scrape_linkedin_posts.py, which is referenced by real paths. Per the rubric's simple-skill guidance this earns a 5.	5 / 5
	Total	19 / 20 Passed

Description

82%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 that clearly states what the skill does and when to use it, with natural trigger phrases and a distinct niche. Its main weaknesses are the second-person phrasing in the trigger clause and capability details (keyword/date filtering, summary output) that appear in the body but not the description.

Suggestions

Rewrite the trigger clause in third person to match the good examples, e.g. "Use when monitoring what specific people are posting on LinkedIn, tracking founder/exec activity, or gathering LinkedIn content for competitive intelligence" instead of "Use when you need to...".

Mention the filtering capabilities in the description (e.g. "filter posts by keywords and date") since they are key features documented in the body but absent from the description.

Add a few natural synonyms such as "scrape LinkedIn activity" or "LinkedIn feed" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ("Scrape recent posts", "monitor what specific people are posting", "track founder/exec activity", "gather LinkedIn content") which fits anchor 4, but the trigger clause "Use when you need to..." is second-person voice, which the judging guidelines penalize by reducing specificity by 1. It is not a 2 because the actions and domain (LinkedIn, Apify) are specific rather than generic.	3 / 5
Completeness	Explicitly answers both: what ("Scrape recent posts from LinkedIn profiles using Apify") and when ("Use when you need to monitor what specific people are posting..., track founder/exec activity, or gather LinkedIn content for competitive intelligence") with concrete trigger phrases. Anchor 4 would require the 'when' to be less explicit than it is here.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — "LinkedIn profiles", "posts", "what specific people are posting", "track founder/exec activity", "competitive intelligence" — giving good keyword coverage. It falls short of anchor 5 because common variations like "LinkedIn activity", "scrape posts", or "social feed" are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche (LinkedIn profile post scraping via Apify) with distinct triggers (LinkedIn, profiles, posts, exec activity) and minimal overlap risk with other skills. No generic phrasing that would fire the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: gooseworks-ai/goose-skills
Path: skills/social/capabilities/linkedin-profile-post-scraper/SKILL.md
Commit: a9f4676

Reviewed: 32 minutes 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.