Skip to content

Add XVARY Stock Research (Claude Code skill) #210

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
SenSei2121 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add XVARY Stock Research (Claude Code skill) #210

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
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -309,6 +309,11 @@ By creating a `.cursorrules` file in your project's root directory, you can leve
4. Select and download the `.cursorrules` file that suits your needs.
5. Customize the rules as needed for your specific project requirements.

## XVARY Stock Research

- [XVARY Stock Research](https://github.com/xvary-research/claude-code-stock-analysis-skill) — Claude Code skill for public SEC EDGAR + market data: `/analyze`, `/score`, `/compare`. MIT.

Comment on lines +312 to +315
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Mar 24, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Move this entry into an existing section and align with README conventions.

This new top-level section breaks the prescribed README order, leaves the table of contents outdated, and introduces an absolute link where the guideline requires relative links. Please place this item under the appropriate existing section (likely ## Utilities or ## Directories), keep alphabetical order there, and update TOC accordingly.

As per coding guidelines, “Maintain the following structure in the README.md file: 1. Title and Awesome badge 2. Logo 3. Short description 4. "Why .cursorrules?" section 5. Table of Contents 6. Rules section (with subcategories) 7. How to Use section 8. Contributing section 9. License section”, “Ensure all links in the README.md file are relative and correct”, and “When updating the README.md, ensure the table of contents remains accurate.”

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 312 - 315, Move the "XVARY Stock Research" entry out
of the top-level and into the appropriate existing section (e.g., the "##
Utilities" or "## Directories" subsection) and insert it in alphabetical order
among that section's items; convert the absolute URL to a relative repository
link (use ./ or appropriate relative path), update the Table of Contents to
reflect the moved section if needed, and ensure the entry formatting matches
other items in the README (same bullet style and link format).


## Contributing

Contributions are welcome! If you have a great `.cursorrules` file to share:
Expand Down