Skip to content

Add Ruleskill to the list #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrkenzi wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Ruleskill to the list #163

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,7 @@ By creating a `.cursorrules` file in your project's root directory, you can leve

## Contents

- [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.
- [Awesome Cursor Rules ](#awesome-cursor-rules-)
Comment on lines 52 to 55
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Fix TOC accuracy and relative-link requirement.

This entry points to an external URL and doesn’t correspond to a section in the README, which makes the table of contents inaccurate and violates the “all links are relative” rule. Either remove this item from Contents, or add a proper section with a relative anchor (and place it in the correct category/alphabetical order).
As per coding guidelines, Maintain the following structure in the README.md file... and Ensure all links in the README.md file are relative and correct.

🛠️ Suggested fix (remove from Contents) 
- - [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Contents
- [Ruleskill](https://ruleskill.com) - We want to verify your code for the RuleSkill Protocol. Claim your badge.
- [Awesome Cursor Rules ](#awesome-cursor-rules-)
## Contents
- [Awesome Cursor Rules ](`#awesome-cursor-rules-`)
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)

[warning] 55-55: Spaces inside link text

(MD039, no-space-in-links)

🤖 Prompt for AI Agents 
In `@README.md` around lines 52 - 55, The Table of Contents contains an external
link entry "Ruleskill" which breaks the README rule that all TOC links must be
relative and must point to actual sections; either remove the "-
[Ruleskill](https://ruleskill.com) - We want to verify your code for the
RuleSkill Protocol. Claim your badge." line from the "Contents" list, or replace
it with a relative anchor that matches a new section heading you add (e.g., add
a "## Ruleskill" section) and place that TOC entry in the correct
alphabetical/category order; update the TOC entry text and anchor so it exactly
matches the new section heading to keep links accurate.

- [Sponsorships](#sponsorships)
- [Why .cursorrules?](#why-cursorrules)
Expand Down Expand Up @@ -347,4 +348,4 @@ Please ensure your contribution is original or properly credited if based on exi

## License

[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)