Launch deal: $99 lifetime for your first always-on AI system.
Build Lean SaaS cube logoBuild Lean SaaS
Back to Blog
AI Development Workflows

Open-Source AI Agent Skills Directory: Submit Your Repo for Daily Highlights

BuildLeanSaaS is building a living directory of open-source AI agent skills, MCP servers, coding-agent workflows, and prompt libraries, with a submission path and daily X highlights for useful projects.

Austin Witherow
4 min read

AI agent builders do not need another vague list of tools.

They need a living map of repos worth studying, what each repo is good for, when to skip it, how to evaluate it, and what safe first task to try before handing it real credentials or production work.

That is why BuildLeanSaaS is building the open-source AI agent skills directory.

The directory covers practical categories like:

  • MCP servers for AI agents
  • Coding-agent workflows
  • Prompt libraries and reusable skill formats
  • Agent operating systems and command-center patterns
  • Repo packaging, browser QA, memory, and evaluation utilities

The goal is simple: help builders find useful source, compare it quickly, and avoid treating every agent repo like magic.

Why this should be a living directory

Open-source agent tooling changes fast.

Repos appear, get renamed, go stale, get absorbed into bigger stacks, or become useful in a category nobody expected. A static “best tools” post goes stale almost immediately.

A living directory lets us keep improving the map:

  • Add new high-signal repos.
  • Prune or flag stale projects.
  • Build category pages when a cluster becomes important.
  • Create comparison pages when builders are choosing between real options.
  • Link back to source so people can inspect before installing.

Start here:

Browse the open-source AI agent skills directory

What makes a repo worth adding?

We are looking for public projects that help builders do real agent work.

Good fits usually have at least one of these jobs:

  • Install: connect an agent to a tool, system, browser, repo, or workflow.
  • Study: learn a repeatable pattern for agent work.
  • Adapt: turn a public routine into a team-specific skill or operating loop.
  • Compare: help builders choose between tool stacks.
  • Evaluate: make agent output easier to test, review, or trust.

A strong submission should include:

  • Repo URL
  • Who it helps
  • What job it does
  • Suggested category
  • Safe first task
  • License, permissions, credential scope, and maintenance notes
  • Any relationship you have to the project

Submit here:

Submit an AI agent skill repo

Daily X highlights

We are also turning the directory into a daily discovery loop.

The plan is to highlight one useful AI agent skill, MCP server, coding-agent workflow, or prompt library each day on BuildLeanSaaS X.

Each highlight should give builders something useful even before they click:

  • What the repo is
  • Who should care
  • What job it helps with
  • One trust check
  • Link to the directory profile or category page
  • Link to submit another repo

Accepted projects may be listed in the directory, shared on X, and included in future blog roundups. Submission does not guarantee a feature, but clear projects with real utility are much easier to review and share.

Example highlight format

This keeps the post useful, repeatable, and easy for maintainers to share.

Where to start

If you are building AI agent workflows, start with the directory:

Open-source AI agent skills directory

If you maintain or know a useful repo, send it here:

Submit your repo for review

If you are comparing approaches, these are useful next reads:

The useful agent stack is not one model or one repo. It is the combination of source, skills, memory, review gates, tests, deployment, and daily operating habits.

That is the map this directory is meant to build.

Next action

Turn this guide into a working system

Start with the attached artifact when one exists, or use the template library to convert the workflow into a concrete implementation plan.

Keep building

Continue with related guides and implementation assets.

Continue Reading

Stay within the same pillar so the next article compounds the context from this one.

Apply It with Templates

Use a template when you want structure, a checklist, or a plan you can adapt immediately.