linkedin-commenter-extractor

Extract commenters from LinkedIn posts via Apify. Returns commenter names, titles, LinkedIn profile URLs, and comment text. Use to find warm leads engaging with relevant discussions. No LinkedIn cookies required.

Quality

81%

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

76%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 highly actionable and well-structured, with executable commands and a clear output schema. Its main weakness is workflow clarity: a batch extraction skill should include explicit validation/error-recovery checkpoints around the Apify run.

Suggestions

Add an explicit validation/feedback step to "How It Works" (e.g., check the Apify run status, retry on timeout, verify non-empty output before dedup) so batch operations include error-recovery checkpoints.

Consolidate the five Quick Start bash blocks into one canonical invocation plus the CLI Reference table to reduce repeated command-path verbosity.

Add a brief "see scripts/extract_commenters.py" pointer so the one-level-deep reference to the implementation is explicitly signaled rather than only implied by the command path.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no padding about concepts Claude already knows, though the Quick Start repeats the full command path across five near-identical bash blocks that could be tightened into a single example with a flag table.	4 / 5
Actionability	Copy-paste-ready bash invocations with real flags, a complete CLI reference table with defaults, and a concrete JSON output schema give fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	"How It Works" lists a clear 5-step sequence, but this batch operation (multiple posts, dedup) has no explicit validation or verification checkpoints for Apify run failures or empty/partial results, so the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Content is split into well-organized sections with the implementation detail held in a single real one-level-deep script (scripts/extract_commenters.py, verified to exist) referenced via executable paths, leaving only minor signaling gaps since there is no explicit "see the script for internals" pointer.	4 / 5
	Total	16 / 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.

The description is concise, third-person, and answers both what the skill does and when to use it with a concrete trigger phrase. It is distinctive and largely free of fluff, with only minor room to broaden trigger-term synonyms.

Dimension	Reasoning	Score
Specificity	"Extract commenters from LinkedIn posts via Apify" and "Returns commenter names, titles, LinkedIn profile URLs, and comment text" name the domain plus several concrete outputs, but the action set is essentially one operation (extract) with its returned fields rather than a broad multi-action catalog.	4 / 5
Completeness	It clearly states the "what" (extract commenters and which fields are returned via Apify) and an explicit "Use to find warm leads engaging with relevant discussions" trigger for the "when", satisfying the anchor for concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "LinkedIn posts", "commenters", and "warm leads engaging with relevant discussions" match what a user would say, though common synonyms or variants (e.g. "who commented on") are not fully covered.	4 / 5
Distinctiveness Conflict Risk	"Extract commenters from LinkedIn posts via Apify" carves out a clear niche with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	18 / 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/lead-generation/capabilities/linkedin-commenter-extractor/SKILL.md
Commit: 2523432

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