gooseworks-ai/goose-skills / skills/shared/linkedin-profile-post-scraper
linkedin-profile-post-scraper
VerifiedScrape 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.
LinkedIn Profile Post Scraper
Scrape recent posts from specific LinkedIn profiles using the Apify harvestapi/linkedin-profile-posts actor.
Quick Start
Requires APIFY_API_TOKEN env var (or --token flag). Install dependency: pip install requests.
# Scrape recent posts from a profile
python3 skills/linkedin-profile-post-scraper/scripts/scrape_linkedin_posts.py \
--profiles "https://www.linkedin.com/in/example-person" --max-posts 10
# Multiple profiles with keyword filtering
python3 skills/linkedin-profile-post-scraper/scripts/scrape_linkedin_posts.py \
--profiles "https://www.linkedin.com/in/person1,https://www.linkedin.com/in/person2" \
--keywords "AI,growth" --days 30
# Summary table
python3 skills/linkedin-profile-post-scraper/scripts/scrape_linkedin_posts.py \
--profiles "https://www.linkedin.com/in/example-person" --output summary
CLI Reference
| Flag | Default | Description |
|---|---|---|
--profiles | required | LinkedIn profile URL(s), comma-separated |
--max-posts | 20 | Max posts to scrape per profile |
--keywords | none | Keywords to filter (comma-separated, OR logic) |
--days | 30 | Only include posts from last N days |
--output | json | Output format: json or summary |
--token | env var | Apify token (prefer APIFY_API_TOKEN env var) |
--timeout | 300 | Max seconds to wait for the Apify run |
Cost
~$2 per 1,000 posts scraped. The script prints a cost estimate before running.
Notes
- No native date filtering — dates are filtered client-side on
postedAt/postedDate - Profile URLs must be full LinkedIn URLs (e.g.
https://www.linkedin.com/in/username)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |