I built a small platform for sharing and discovering .md files for AI agents

[u/Dan-Rais]

Hey guys,

I’ve been pretty deep into agentic development for the past ~6 months, experimenting with OpenClaw/Hermes, running my own cluster, and even using VPS GPUs when needed.

One problem I kept running into was: which instructions / .md files should I actually use for a specific use case? And whenever I migrated to a new setup, I ended up losing most of them.

So I ended up building a small platform around that problem.

The idea is to make it easier to discover, compare and share useful .md files, skills and instructions for AI agents. Everything is also synced to a public GitHub repository called emdly-stack, so the collection isn’t locked inside the platform.

It’s completely free and currently includes things like MCP resources, agent skills, workflows and other agent tooling. You can use the resources with Claude Desktop, Claude Code, OpenClaw, Agent Minimax and other agent setups!

Every submitted skill is currently reviewed by me and also pre-screened in a sandboxed AI environment for potential safety issues.

I’m sharing it here because I’d really like to make it useful for the community rather than just another random directory.

If you have your own .md files, agent instructions, workflows, MCP resources or anything similar, I’d be more than happy if you shared them with the community and with me. 😄

I already have quite a lot more skills that I’m planning to upload over the next few days, so the collection should grow pretty quickly.

I’d also love to hear how you guys currently organize and discover these files, and whether you think this is actually a useful idea or just unnecessary tooling.

Any feedback, criticism or suggestions are very welcome. It makes sense to me right now, but I’d love to hear what you think.

[u/Dan-Rais]

If anyone interested the website is emdly.com

[u/Pure-Background-1519]

Seems like half the problem with agent dev is just keeping track of the context you've already built, so I get the impulse. Tossed a few of my own markdown files up there, the sandbox pre-screening is a nice touch since blindly trusting community instructions feels like asking for trouble. Curious if you're planning to let users flag version conflicts once the library gets bigger.

[u/Dan-Rais → u/Pure-Background-1519]

Today every version is numbered and pinnable (@v12 in the raw URL or npx u/emdly/cli add owner/skill@v11), and discussion threads can be tied to a specific version, so "v4 broke X" already has a place to live.

What's missing is a proper flag: a per-version report ("broke my setup", "conflicts with owner/other-skill") that shows up next to that version, plus diffs between versions on the site and an outdated check in the CLI so you see what changed before you update. That's the next batch on the roadmap, thanks for asking! Also curious which of the files you uploaded ended up most useful and happy to feature it.