skills

Skills for Real Engineers. Straight from my .claude directory. (by mattpocock)

Skills Alternatives

Similar projects and alternatives to skills

  1. zed

    286 skills VS zed

    Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.

  2. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  3. superpowers

    70 skills VS superpowers

    An agentic skills framework & software development methodology that works.

  4. agentskills

    64 skills VS agentskills

    Specification and documentation for Agent Skills

  5. skills

    55 skills VS skills

    Public repository for Agent Skills

  6. rtk

    37 skills VS rtk

    CLI proxy that reduces LLM token consumption by 60-90% on common dev commands. Single Rust binary, zero dependencies

  7. awesome-copilot

    Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.

  8. Fabric

    20 skills VS Fabric

    Fabric is an open-source framework for augmenting humans using AI. It provides a modular system for solving specific problems using a crowdsourced set of AI prompts that can be used anywhere.

  9. cmux

    20 skills VS cmux

    Ghostty-based macOS terminal with vertical tabs and notifications for AI coding agents

  10. open-infra-index

    Production-tested AI infrastructure tools for efficient AGI development and community-driven innovation

  11. awesome-agentic-patterns

    A curated catalogue of awesome agentic AI patterns

  12. compound-engineering-plugin

    Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more

  13. code-foundations

    Code Foundations: software engineering skills for AI

  14. fesh

    4 skills VS fesh

    An experiment building a new type of compression algorithm

  15. llm-council

    9 skills VS llm-council

    LLM Council works together to answer your hardest questions

  16. agent-skills

    9 skills VS agent-skills

    Production-grade engineering skills for AI coding agents.

  17. std_slop

    STD::SLOP An Sqlite/C++ Code CLI

  18. toad

    6 skills VS toad

    A unified interface for AI in your terminal.

  19. humanlayer

    6 skills VS humanlayer

    The best way to get AI coding agents to solve hard problems in complex codebases.

  20. aico

    3 skills VS aico

    A command-line tool for scripting AI-driven code edits.

  21. qrspi-plus

    A structured agentic development pipeline for Claude Code — extends QRSPI with worktree parallelization, tiered reviews, integration verification, acceptance testing, and replanning

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better skills alternative or higher similarity.

skills discussion

Log in or Post with

skills reviews and mentions

Posts with mentions or reviews of skills. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2026-06-09.
  • AI agentic workflows on large codebases
    2 projects | dev.to | 9 Jun 2026
    The workflow I use is largely based on Matt Pocock's skills with a few tweaks. There is a lot of great stuff in there, but the absolute minimum I use is four commands, run in order.
  • Turning Kiro Into a Leadership Coach With Meeting Transcripts
    2 projects | dev.to | 8 Jun 2026
    grill-me - forces the AI to challenge rather than agree
  • Skills for Real Engineers. Straight from my .claude directory
    1 project | news.ycombinator.com | 8 Jun 2026
  • I'm tired of LLM skill slop, so I built mine with regression tests
    2 projects | news.ycombinator.com | 8 Jun 2026
    Claude skills made by other people are typically useless. The exceptions I have found are https://github.com/EveryInc/compound-engineering-plugin which was like an early brainstorm -> plan -> write -> embed knowledge and best practices. Which is a common workflow now.

    I've recently experimented with more lightweight things like https://github.com/mattpocock/skills which are good.

    Most work is just the same 'ask questions step by step to define a spec' , 'make a plan', 'implement using TDD'

  • Alibaba/Open-Code-Review
    10 projects | news.ycombinator.com | 4 Jun 2026
    Thermonuclear suggested by someone below is good. Matt Poccock did a live demo/breakdown of that: https://www.youtube.com/watch?v=mh5XZ-L5SFQ. He has his own "improve-codebase-architecture" skill: https://github.com/mattpocock/skills/blob/main/skills/engine...

    Some of them are about general coding guidelines and code quality, not necessarily vetting your current PR against specs! There's AbsolutelySkilled with clean-code and clean-architecture. Linking to older version of repo because they seem to be no longer on trunk: https://github.com/AbsolutelySkilled/AbsolutelySkilled/tree/...

    I've been creating some rules to help with my Java coding:

  • Meet Deliberation: 400+ models is easy, knowing which ones earn a place is hard.
    4 projects | dev.to | 3 Jun 2026
    And none of this is a separate ritual you have to schedule. Call /ask-all or /consensus at any point in the work - while you are still scoping a feature, halfway through writing a plan, or in the middle of a /grill-me session when you want a real outside voice in the room instead of arguing with only yourself. The panel is available the whole time, not just at the review at the end. The earlier you pull in a dissenting model, the cheaper the disagreement is to act on.
  • Tools I'm Using in 2026 (and what I've stopped using from 2025)
    10 projects | dev.to | 26 May 2026
    Skills For Real Engineers
  • Using AI to write better code more slowly
    2 projects | news.ycombinator.com | 25 May 2026
    > This article doesn't address writing code with AI, just code review. My issue with agentic coding is that I make numerous micro-architectural decisions while programming. I almost never have a full spec up front and develop one as I consider what I am writing.

    working with AI forced me to write better specs but the way I write today is very different. I typically open Codex and have Linear MCP connected where my chat with the AI will end up writing the issue. Its a lot of back-end-forth where I tell what I want, the AI does all the code scanning, write something, I correct something, etc

    The value for me is exactly that I tell what I want, the AI verify in the actual code if that's the path that makes more sense or not. In the end I have a pretty detailed spec that I'm much more confident is the correct path.

    I find the spec easier to review than a huge PR so typically when executing is much faster and aligned with what I want.

    The grill-me skill from Matt Pocock is great for this (https://github.com/mattpocock/skills/blob/main/skills/produc...)

  • 4 GitHub Repos That Prove AI Agents Aren't Just for Coding Anymore
    2 projects | dev.to | 21 May 2026
    Repo: github.com/mattpocock/skills
  • More Than Skills, Frameworks
    1 project | news.ycombinator.com | 19 May 2026
  • A note from our sponsor - SaaSHub
    www.saashub.com | 9 Jun 2026
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic skills repo stats
19
118,308
6.3
6 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com

Did you know that Shell is
the 8th most popular programming language
based on number of references?