AI tool comparison
Awesome Agent Skills vs Ferretlog
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Awesome Agent Skills
1,100+ hand-curated skills for every major AI coding agent
75%
Panel ship
—
Community
Paid
Entry
Awesome Agent Skills is a curated repository of over 1,100 agent skills from official development teams and the open-source community, organized for use with Claude Code, Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, OpenCode, and more. Maintained by VoltAgent, the collection explicitly rejects AI-generated filler — everything is hand-picked. The library spans every corner of the modern developer stack: frontend frameworks (React, Next.js, Angular, React Native), cloud platforms (Cloudflare Workers, Netlify, Vercel, Google Cloud), databases (PostgreSQL, ClickHouse, MongoDB, Firebase), infrastructure (Terraform, HashiCorp), CMS (Sanity, WordPress), APIs (Stripe, Composio, Firecrawl), AI/ML (Replicate, Gemini, OpenAI), and design (Figma, Remotion). Skills from Stitch, Remotion, and dozens of official vendor teams are included. As agent-native development becomes the default workflow, having the right skills loaded into your agent is as important as having the right VS Code extensions was in 2020. This is becoming the npm registry of agent capabilities — 18k+ stars and still climbing.
Developer Tools
Ferretlog
git log for your Claude Code agent runs — local, zero dependencies
50%
Panel ship
—
Community
Free
Entry
Ferretlog is a zero-dependency pure Python CLI that treats your Claude Code session logs like a git repository. It parses the raw JSONL logs in `~/.claude/projects/` and gives you git-style history browsing, diff between runs, per-tool-call breakdowns, and cost/token stats — entirely locally, with no network calls and no configuration required. If you've been using Claude Code heavily, you've likely experienced the frustration of losing track of what changed across sessions, what tools were called how many times, and how much each session actually cost across sub-agent calls. Ferretlog makes that history explorable and comparable the same way `git log` makes code history explorable. This is an indie solo project from Eitan Lebras, submitted as a Show HN. It's genuinely useful as a power-user tool for anyone doing serious Claude Code work, especially those managing multi-session agent pipelines where debugging "what did the agent do last time?" is a real pain. The zero-dependency, local-only design means there's no trust surface and no setup friction.
Reviewer scorecard
“This is the package registry equivalent for agent skills. Instead of hunting across 30 different repos, everything is here and organized. The fact that official vendor teams like Stripe and Cloudflare are contributing their own skills means quality stays high.”
“If you run Claude Code daily, you need this immediately. Being able to diff two sessions like git commits and see exactly which tools fired and what they cost is something that should have existed from day one. Zero-dependency Python means it just works.”
“1,100 skills sounds impressive but quantity isn't quality. Keeping skills current as APIs evolve is a massive maintenance burden — today's Stripe skill becomes tomorrow's broken context blob. Absent a strong contributor community, this risks becoming stale fast.”
“This is a niche tool for a niche user (heavy Claude Code power users) and the session log format Anthropic uses is undocumented and could change at any update. Tying workflows to internal log parsing is fragile infrastructure — treat it as a convenience, not a dependency.”
“The aggregation layer for agent tooling will be enormously valuable. Whoever owns the canonical skills registry wins developer distribution the way npm and pip did before — Awesome Agent Skills has first-mover positioning in a winner-take-most market.”
“Agent observability tooling built by the community, not the vendor, is how this ecosystem will mature. Ferretlog is primitive but it points at a real gap: we need git-style versioning and auditability for agent sessions, not just for code.”
“Having Figma and Remotion skills officially in here means designers can plug into agentic workflows without translating their tools into developer language. Exactly the kind of cross-discipline thinking that makes agent tooling accessible beyond pure coders.”
“Terminal-only, Claude Code-specific, no visuals — this tool exists entirely outside my workflow. The underlying insight (session replay and cost tracking) is useful, but it needs a UI before it reaches anyone outside the developer community.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.