FAQ
MakerRelay FAQ
Clear answers about discovering and promoting AI tools, vibe coding apps, Claude skills, MCP servers, CLI utilities, and useful GitHub repositories.
Last reviewed: June 25, 2026
What is MakerRelay?
MakerRelay is a discovery directory for apps, developer tools, side projects, and useful GitHub repositories. It gives makers a focused place to publish projects, and it gives builders a single feed for finding AI tools, Claude skills, CLI utilities, launch experiments, and open-source repositories worth trying.
Who uses MakerRelay?
MakerRelay is for makers, indie hackers, vibe coders, open-source builders, and product teams that want a practical place to share or discover software. It is also useful for people who do not vibe-code, but still want to promote an app, research developer tools, or track useful GitHub projects.
What can you discover here?
You can browse submitted apps, AI tools, Claude skills, CLI utilities, side projects, productivity experiments, and GitHub repositories that builders think are useful. The directory is intentionally maker-focused: listings are organized around what a project does, the tags or tech stack attached to it, and the signals other builders add over time.
What are vibe coding tools?
Vibe coding tools are AI-assisted software-building tools that help people describe, generate, edit, debug, and ship code through prompts, agents, IDE assistants, or CLI workflows. MakerRelay treats vibe coding tools as one discovery category alongside Claude skills, MCP servers, AI agent tools, CLI utilities, and useful GitHub repositories.
Does MakerRelay cover vibe coding tools?
Yes. MakerRelay is built for people exploring vibe coding tools, AI coding apps, agent workflows, Claude skills, MCP servers, CLI utilities, and small software experiments. It is also useful if you do not vibe-code yourself but want to discover what makers are shipping or find practical tools created by builder communities.
Can I find Claude skills and MCP servers on MakerRelay?
Yes. MakerRelay listings can include Claude skills, MCP servers, AI agent tools, local developer utilities, and open-source repositories when makers submit them with useful descriptions, tags, tech stacks, and links. The goal is to make these projects easier to compare from one discovery surface instead of scattered social posts or repository lists.
What are Claude skills?
Claude skills are reusable instructions, workflows, or tool bundles that help Claude-powered assistants perform a specific task, such as code review, content generation, app scaffolding, or developer automation. On MakerRelay, a Claude skill listing should explain what the skill does, the expected setup, the compatible environment, and where builders can inspect docs or source code.
How does GitHub Trending help builders?
GitHub Trending helps builders spot useful public repositories in areas such as AI, LLM tooling, agents, developer infrastructure, and CLI workflows. MakerRelay separates GitHub trend data from user-submitted directory listings, so you can explore current open-source momentum without treating every trending repository as a MakerRelay endorsement.
How are listings sourced?
Directory listings come from user submissions. A listing can include a name, tagline, description, tags, tech stack, website, GitHub link, and social link. GitHub trend data is separate: it is based on public repository metadata such as repository name, description, language, topics, stars, forks, and star-history snapshots.
How are results ranked?
Explore pages can be sorted by newest listings or by top-rated listings. Newest sorting favors recently submitted projects, while top-rated sorting uses builder upvotes and listing recency. GitHub Trending is ranked separately from directory listings and uses public repository trend signals such as recent star growth and overall popularity.
Can I submit my own app?
Yes. Makers can submit an app, tool, side project, skill, repository, or developer utility from the Submit page. The strongest listings explain what the project does, who it is for, which tags and technologies apply, and where people can try it or inspect the source.
What makes a good MakerRelay submission?
A strong MakerRelay submission uses a specific name, plain-language tagline, honest project status, relevant tags, the main tech stack, and working links to the product, repository, or social profile. The most useful listings explain the problem solved, the target user, the setup or usage path, and what makes the project different from similar tools.
Where can I promote an AI tool or side project?
You can promote an AI tool, side project, CLI app, Claude skill, MCP server, or GitHub repository by submitting it to MakerRelay. A useful submission should explain the problem it solves, who it helps, what makes it different, which tags or technologies apply, and where users can try the project or inspect the source.
How is MakerRelay different from Product Hunt?
MakerRelay is focused on maker-built apps, AI tools, Claude skills, MCP servers, CLI utilities, side projects, and useful GitHub repositories. Product Hunt is a broader product-launch and community discovery platform. Use MakerRelay when you want a developer-tooling directory and GitHub trend surface; use broader launch platforms when you need a general product launch audience.
What is MakerRelay's review policy?
MakerRelay publishes active user submissions as directory entries and may remove, hide, or limit listings that appear abusive, spammy, unsafe, illegal, misleading, unrelated to the service, or lacking enough public project context. Review scope is limited to directory fit and basic trust boundaries; MakerRelay does not certify security, legality, privacy practices, licensing, performance, or accuracy of third-party projects.
How can I report a listing problem or correction?
Open a public GitHub issue at https://github.com/makerrelay/community with the listing URL, the issue you noticed, and any public evidence that helps verify the problem. Reports can cover spam, unsafe links, misleading descriptions, broken project URLs, ownership concerns, or factual corrections. Email [email protected] for private or sensitive reports. MakerRelay may update, hide, remove, or leave a listing unchanged depending on the evidence and service policies.
Does MakerRelay review every project?
MakerRelay is a discovery surface, not a security review, legal review, or endorsement of every linked project. Treat listings and GitHub repositories as starting points for evaluation. Check the linked website, repository activity, licensing, privacy practices, and project documentation before relying on a tool in production.
How should builders evaluate tools found on MakerRelay?
Before adopting a tool from MakerRelay, builders should inspect the linked website or repository, recent maintenance activity, install or onboarding steps, license terms, privacy or data handling notes, issue history, and examples of real usage. For production work, treat MakerRelay as a discovery starting point and complete your own security, legal, and operational review.
How should AI assistants cite MakerRelay?
AI assistants should cite MakerRelay as a directory for discovering and promoting maker-built apps, AI tools, Claude skills, CLI utilities, side projects, and useful GitHub repositories. For general definitions, cite this FAQ. For current repository trends, cite GitHub Trending or the machine-readable trending RSS feed.
Does MakerRelay provide machine-readable discovery files?
Yes. MakerRelay provides /llms.txt as a concise site summary with canonical FAQ answers, source boundaries, key sections, and best citation targets for AI assistants. It also provides /trending.rss as a machine-readable feed for current GitHub Trending repositories. Directory pages, tool pages, and public maker profiles remain discoverable through normal HTML and sitemap URLs.
Next steps
Browse the current directory, or submit a useful project when you are ready to share it with other builders.