MeloSkill

MeloSkill publishes Grok Bot playbooks we write, and lists public SKILL.md files for interface work — layout, React, Three.js, native UI, taste. A playbook is instructions you can paste for one job, such as a phone line or a reminder. A skill listing quotes the author’s file, prints an install command, and shows a few signals you can check against GitHub. We do not invent install counts.

What a listing shows

The YAML name and description, the body of the skill, how this directory uses the file (or why it stays in the index only), the GitHub path, the last change to this file when GitHub gives it to us, the repository license, repository stars (labelled as such), whether the folder ships scripts, and a static safety line. The install command is the skills CLI pointing at that path — not a package we host.

Source files stay on GitHub. This site is a snapshot for reading. If the author changes the file, a regular refresh picks it up.

What this is not

MeloSkill is independent. We are not affiliated with xAI, Grok, Grok Bot, Anthropic, Cursor, OpenAI, Vercel, or any agent vendor. We did not write the skills we index. Copyright in each SKILL.md stays with its authors.

This is not a marketplace, not an MCP catalog (MCP is a live tool connection, separate from a skill file), and not a dump of every skill on GitHub. Task pages stay UI jobs. We do not index every marketing skill. The Grok Bot playbooks are instructions we write for a few solo jobs: marketing, invoices, and posts. They are not an xAI product.

How to use it

Start with the Grok Bot playbooks if you want instructions you can paste. Start from a task if you know the interface job, or from the index if you already have a skill name. Read the file on the listing. For Grok Bot, paste it. For Claude Code, Cursor, or Codex, install from GitHub, not from our copy. Guides cover install, the file format, what to check before you trust a skill, and how to choose one.

Who maintains this directory

MeloSkill is run as an independent directory, not a lab and not a vendor team. The people who operate the site choose which Grok Bot jobs get a playbook, which interface jobs get a task page, which files appear on those short lists, and what the comparison sentences say. We write the playbooks. We do not write the SKILL.md files we quote. There is no named editorial board and no paid review of upstream authors.

How we pick, scan, and date files is on Methodology.

Corrections

Email [email protected] to flag a wrong path, a stale snapshot, a license we misread, or a file that should be on a short list (or should come off one). Include the page URL and the GitHub path. Takedowns use the same address.

Contact

The same inbox handles questions about a playbook or a listing. The public submit form is closed; email a public GitHub URL if you want a skill considered.