Linkedin Thread Monitor
sergebulaev/linkedin-skills
Track which of your LinkedIn comments earned author replies.
Lead qualification engine with conversational intake. An agent skill from gooseworks-ai/goose-skills.
$ npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills lead-qualification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lead-generation/capabilities/lead-qualification .claude/skills/lead-qualification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lead-qualification" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualification into .claude/skills/lead-qualification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-qualification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills lead-qualification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lead-generation/capabilities/lead-qualification .agents/skills/lead-qualification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lead-qualification" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualification into .agents/skills/lead-qualification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-qualification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills lead-qualification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lead-generation/capabilities/lead-qualification .cursor/skills/lead-qualification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lead-qualification" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualification into .cursor/skills/lead-qualification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-qualification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gooseworks-ai/goose-skills.git --path skills/lead-generation/capabilities/lead-qualification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills lead-qualification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lead-generation/capabilities/lead-qualification .gemini/skills/lead-qualification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lead-qualification" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualification into .gemini/skills/lead-qualification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-qualification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gooseworks-ai/goose-skills lead-qualificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lead-generation/capabilities/lead-qualification .github/skills/lead-qualification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lead-qualification" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualification into .github/skills/lead-qualification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-qualification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills lead-qualification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lead-generation/capabilities/lead-qualification .opencode/skills/lead-qualification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lead-qualification" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/lead-generation/capabilities/lead-qualification into .opencode/skills/lead-qualification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-qualification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
lead-qualificationLead qualification engine with conversational intake. An agent skill from gooseworks-ai/goose-skills.
Lead Qualification is an agent skill from gooseworks-ai/goose-skills. Lead qualification engine with conversational intake. Asks structured questions to understand your qualification criteria, generates a reusable qualification prompt, then batch-enriches leads via Apify LinkedIn scraping and scores them with parallel processing. Outputs qualified/disqualified verdicts with confidence scores and reasoning to CSV or whatever output format the user prefers. Supports calibration mode for prompt refinement.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `qualification-prompts/ai-event-attendees-gtm.md`, `qualification-prompts/juicebox-linkedin-commenters.md` and `scripts/enrich_leads.py`).
It sits in Data & Analytics, covering Web scraping and Performance reviews. It works with Apify and LinkedIn. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
linkedin.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
APIFY_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Lead Qualification loads about 3.8k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 1,543 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 1,543 words, ~3,794 tokens.
.claude/skills/lead-qualification/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Qualify leads against custom criteria through a structured intake process, then score lead lists in parallel with confidence ratings and reasoning.
No existing qualification prompt. Run intake to build one, save it, then qualify leads.
Trigger: User provides no qualification prompt file.
User references an existing qualification prompt file — skip intake, go straight to scoring.
Trigger: User tags or references a file in skills/lead-qualification/qualification-prompts/.
User has seen results and wants to adjust criteria. Update the saved prompt, re-run.
Trigger: User says something like "refine", "adjust", "that's wrong", or provides feedback on qualification results.
The goal is to build a complete picture of who the user considers qualified vs disqualified. Present questions in bulk rounds so the user can answer efficiently.
Present these questions as a numbered list. Tell the user: "Answer what's relevant, skip what's not. I'll follow up on anything I need to clarify."
Product & Campaign Context:
Company-Level Criteria: 4. What company sizes are you targeting? (e.g., 1-10, 11-50, 51-200, 201-1000, 1000+) 5. What industries or verticals are a good fit? 6. Any industries or company types to explicitly EXCLUDE? 7. Geographic targets? Or is this global? 8. Geographic exclusions? 9. Does company stage matter? (e.g., seed, Series A, Series B+, public) 10. Any revenue range or funding range that matters?
Person-Level Criteria: 11. What job titles or roles are your ideal buyers? 12. What titles are explicitly disqualified? 13. Does seniority level matter? (e.g., must be Director+, VP+, C-level) 14. What departments should they be in? (e.g., growth, marketing, sales, engineering) 15. Minimum tenure at current company? (e.g., 6+ months to have buying power) 16. Does total years of experience matter?
Behavioral & Situational Signals: 17. Are there tech stack signals that qualify or disqualify? (e.g., "uses Salesforce" = good fit) 18. Does recent company activity matter? (e.g., hiring spree, funding round, product launch) 19. Are there content/posting signals? (e.g., "posted about AI" = relevant) 20. Any other signals that indicate high intent or good fit?
Dealbreakers & Instant Qualifiers: 21. What are your HARD DISQUALIFIERS — things that instantly make someone a "no" regardless of other factors? 22. What are your STRONGEST QUALIFIERS — things that make someone an almost certain "yes"?
Based on the user's answers, ask 5-10 targeted follow-ups to resolve ambiguity. Examples:
Present 3-5 hypothetical lead profiles that test boundary cases. Ask "Would you qualify this person?"
Example scenarios to construct (adapt based on the user's criteria):
This round catches implicit criteria the user hasn't articulated.
After intake is complete, synthesize all answers into a structured qualification prompt. Save it to:
skills/lead-qualification/qualification-prompts/[campaign-name].mdThe saved prompt MUST follow this structure:
# Qualification Prompt: [Campaign Name]
Generated: [date]
## Campaign Context
- **Product:** [one-liner]
- **Campaign Angle:** [specific angle]
- **Problem Solved:** [what and for whom]
## Hard Disqualifiers (Instant No)
- [list each with explanation]
## Hard Qualifiers (Instant Yes)
- [list each with explanation]
## Company Criteria
| Criterion | Qualified | Disqualified | Notes |
|-----------|-----------|--------------|-------|
| Size | [range] | [range] | |
| Industry | [list] | [list] | |
| Geography | [list] | [list] | |
| Stage | [list] | [list] | |
| Funding/Revenue | [range] | [range] | |
## Person Criteria
| Criterion | Qualified | Disqualified | Notes |
|-----------|-----------|--------------|-------|
| Titles | [list] | [list] | |
| Seniority | [level+] | [below level] | |
| Department | [list] | [list] | |
| Tenure | [minimum] | [below minimum] | |
| Experience | [range] | [range] | |
## Behavioral & Situational Signals
- [list signals that boost qualification]
- [list signals that reduce qualification]
## Confidence Rules
- **High Confidence:** Enough data available for company size, title, tenure, and at least one signal.
- **Medium Confidence:** Missing one or two non-critical data points but core criteria are clear.
- **Low Confidence:** Missing critical data points (e.g., no company size, unclear title). Still make a yes/no call but flag it.
## Edge Case Guidance
- [specific guidance derived from Round 3 scenarios]
- [any nuanced rules from the intake conversation]
## Qualification Reasoning Instructions
When evaluating a lead, structure your reasoning as:
1. Check hard disqualifiers first — if any match, immediately disqualify.
2. Check hard qualifiers — if any match, lean strongly toward qualifying.
3. Evaluate company criteria against thresholds.
4. Evaluate person criteria against thresholds.
5. Factor in behavioral/situational signals as tiebreakers.
6. Assign confidence based on data completeness.
7. Write 2-3 sentence reasoning summarizing the decision.Accept any of these input formats:
Detect the format automatically based on what the user provides.
When: The input contains a linkedin_url column (or LinkedIn URLs are available).
Skip when: No LinkedIn URLs are present, or the user explicitly says to skip enrichment.
Before LLM qualification, batch-enrich all leads to gather structured profile data. This is MUCH faster and cheaper than per-lead web searches during qualification.
Run the enrichment script:
python3 skills/lead-qualification/scripts/enrich_leads.py INPUT_CSV \
--output ENRICHED_CSV \
--cache-hours 24Use --dry-run first to show the cost estimate without calling Apify.
What this does:
enriched_title, enriched_company, enriched_industry, enriched_location, enriched_connections, enriched_education, enriched_experience_years, enriched_headline, enriched_about, enrichment_statusAfter enrichment, use the enriched CSV as input for Steps 2-4. The enriched data lets the LLM qualification step work from structured fields instead of doing web searches, dramatically improving speed and consistency.
If enrichment fails for some profiles: They'll have enrichment_status: failed in the output. The LLM qualification step should fall back to web search for those leads only.
Before processing the full list, run the first 5-10 leads and present results to the user in a table.
If batch enrichment was run (Step 1.5), use the enriched columns (enriched_title, enriched_company, etc.) as the primary data source. Only fall back to web search for leads where enrichment_status is failed or no_url.
| # | Name | Title | Company | Qualified | Confidence | Reasoning |
|---|------|-------|---------|-----------|------------|-----------|
| 1 | ... | ... | ... | Yes | High | ... |
| 2 | ... | ... | ... | No | Medium | ... |
| ... |Ask: "Do these look right? Should I adjust any criteria before processing the full list?"
If the user flags issues:
Repeat until the user approves.
Once calibration is approved, process ALL remaining leads using parallel subagents. You MUST parallelize — do NOT process leads sequentially.
Parallelization protocol (mandatory):
Calculate batch count:
Prepare batch inputs: For each batch, create a self-contained context package:
qualification-prompts/ file)enrichment_status=failed or no_url, do a quick web search. Spend no more than 30 seconds per lead on search."Launch parallel Task agents: Use the Task tool to launch ALL batches simultaneously in a single message with multiple tool calls:
Task: "Qualify leads batch 1/N"
Context: [qualification prompt] + [batch 1 lead rows]
Task: "Qualify leads batch 2/N"
Context: [qualification prompt] + [batch 2 lead rows]
... (launch ALL at once — do NOT wait for batch 1 before launching batch 2)Collect and merge results:
Validate completeness:
Per-lead processing (within each batch agent):
enrichment_status: success or cached): use enriched_title, enriched_company, etc.enrichment_status: failed or no_url): do a quick web search (max 30 seconds)Default: CSV
Qualified — Yes / NoConfidence — High / Medium / LowReasoning — 2-3 sentence explanationIf the user prefers Google Sheets or another destination:
After output is complete, present a summary:
## Qualification Results: [Campaign Name]
**Total leads processed:** X
**Qualified:** X (Y%)
**Disqualified:** X (Y%)
**Confidence breakdown:**
- High: X leads
- Medium: X leads
- Low: X leads (may need manual review)
**Top disqualification reasons:**
1. [reason] — X leads
2. [reason] — X leads
3. [reason] — X leads
**Output:** [Google Sheet link or CSV path]
**Qualification prompt saved to:** skills/lead-qualification/qualification-prompts/[campaign-name].mdThe qualification agent should have access to:
scripts/enrich_leads.py for batch profile enrichment before qualificationharvestapi~linkedin-profile-scraper Apify actor ($3/1k profiles, no cookies)APIFY_API_TOKEN environment variable--dry-run first to preview costQualify leads for our outbound campaign. Here's the lead list: leads.csv→ Agent detects no saved prompt, starts intake, builds prompt, then qualifies.
Qualify these leads using @skills/lead-qualification/qualification-prompts/series-a-founders.md
— lead list: leads.csv→ Agent skips intake, goes straight to calibration + qualification.
Using the series-a-founders qualification prompt, qualify these people:
- https://linkedin.com/in/person1
- https://linkedin.com/in/person2
- https://linkedin.com/in/person3Those results look off — also disqualify anyone at a consulting firm, and lower the
tenure minimum to 3 months for Director+ titles.→ Agent updates the saved prompt and re-runs.
© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (scripts) in skills/lead-generation/capabilities/lead-qualification of gooseworks-ai/goose-skills.
Open the folder on GitHubat commit c650c6d
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.
Lead Qualification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lead Qualification this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Linkedin Thread Monitorsergebulaev/linkedin-skills | 4.4k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Apify Google Maps Leadsapify/awesome-skills | 265 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Apify Job Boardsapify/awesome-skills | 265 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Coffee ChatLeoYeAI/openclaw-master-skills | 2.2k | — | ~6.6k | Automated safety check: Pass | MIT | |
| Apify Jobs Dataapify/awesome-skills | 265 | — | ~5.5k | Automated safety check: Pass | Apache-2.0 |
sergebulaev/linkedin-skills
Track which of your LinkedIn comments earned author replies.
apify/awesome-skills
Build a local-business lead database from Google Maps in one Apify pipeline: search by target audience + geography, enrich each place with company contacts from its website, leads enrichment (names…
apify/awesome-skills
Pull job postings from many boards in one run and prepare one validated, deduplicated table.
LeoYeAI/openclaw-master-skills
Generate a personalized coffee chat playbook for networking conversations.
apify/awesome-skills
Extract clean, de-noised job-posting data from LinkedIn, Indeed, Glassdoor, and 20+ boards in one Apify run — deduplicated across boards, with likely ghost jobs and reposts flagged (heuristic, not…
apify/agent-skills
Scrapes public data from social, maps, search and review platforms by choosing from about a hundred Apify Actors and running them through the Apify CLI.
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Categories
Lead qualification engine with conversational intake. An agent skill from gooseworks-ai/goose-skills. Lead Qualification is an agent skill from gooseworks-ai/goose-skills. Lead qualification engine with conversational intake.
Lead Qualification fits situations like: tasks that involve Web scraping; tasks that involve Performance reviews.
Run `npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a claude-code`. Or copy the skill folder (skills/lead-generation/capabilities/lead-qualification in gooseworks-ai/goose-skills) into .claude/skills/lead-qualification in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a codex`. Or copy the skill folder (skills/lead-generation/capabilities/lead-qualification in gooseworks-ai/goose-skills) into .agents/skills/lead-qualification in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill lead-qualification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lead-qualification, .gemini/skills/lead-qualification, .github/skills/lead-qualification and .opencode/skills/lead-qualification in your project.
Going by SKILL.md and its folder, Lead Qualification needs Python for the scripts in its folder, the command-line tools its instructions call (python3) and credentials named APIFY_API_TOKEN. Our summary lists: Python 3.
SKILL.md names 1 domain. In commands or code: linkedin.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Lead Qualification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Lead Qualification: Linkedin Thread Monitor (sergebulaev/linkedin-skills, 4.4k stars), Apify Google Maps Leads (apify/awesome-skills, 265 stars), Apify Job Boards (apify/awesome-skills, 265 stars) and Coffee Chat (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,239 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.