awesome-skills vs awesome-agent-skills

Apify workflow guides compared with a broad skills directory

awesome-skills is a collection of community-written guides for using Apify Actors in specific workflows. awesome-agent-skills is a curated index of skills from official developer teams and the community, organized to help users discover guidance across providers and tasks.

awesome-skillsawesome-agent-skills
LanguagePythonnot specified
LicenseApache-2.0MIT
Stars26035.2k
Forks773.8k
Last analyzedOct 3, 2026Oct 3, 2026

Key differences

  • awesome-skills focuses on Apify Actor workflows, while awesome-agent-skills indexes skills across development topics and providers.
  • awesome-skills packages its guides as SKILL.md files and supports installation with the skills CLI; awesome-agent-skills links to individual skill sources rather than providing a unified installer.
  • awesome-skills follows the Agent Skills specification; awesome-agent-skills describes compatibility across multiple coding agents, with support varying by linked skill.
  • awesome-skills is written in Python and licensed under Apache-2.0; awesome-agent-skills is licensed under MIT.
  • awesome-skills has 260 stars and 77 forks, while awesome-agent-skills has 35.2k stars and 3.8k forks.

Choose awesome-skills if you…

  • need task-specific guidance for using Apify Actors.
  • want to install a skill collection or select an individual Apify workflow guide.
  • plan to contribute repeatable Apify Actor instructions for community review.
Read the awesome-skills analysis →

Choose awesome-agent-skills if you…

  • want to browse skills from official developer teams and community sources by provider or task.
  • need to find guidance for topics such as testing, security, frameworks, or APIs across coding agents.
  • prefer to inspect and install individual skills from their linked sources.
Read the awesome-agent-skills analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.