cursor / cursor/plugins

ForgeCat profiles for Cursor plugins

Open
#139 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8.2k
Forks
751
Avg merge
12h 1m
Merged PRs (30d)
43

Description

Hi Cursor team,

I’m working on ForgeCat, a tool for making agent profiles such as skills, agents, rules, commands, hooks, and MCP configs easier to install across different agent tools.

We found the Cursor plugins collection useful for reusable agent workflows, so we created initial ForgeCat profiles for a few plugins here:

Profile repo: https://github.com/nota-america/forgecat-agent-profiles/tree/main/profiles/cursor/plugins

Install example:

forgecat install @forgecat/cursor_plugins_continual-learning
forgecat install @forgecat/cursor_plugins_ralph-loop
forgecat install @forgecat/cursor_plugins_team-kit

ForgeCat currently supports Claude Code, Cursor, and Codex, and we’re also planning support for OpenClaw, Hermes, and other agent runtimes. The goal is to help people reuse useful agent workflows across tools while keeping attribution and links back to the original repository.

I wanted to check with you before we continue maintaining this profile.

Which option best matches your preference?

  1. The current ForgeCat profile is okay as-is.
  2. Keeping the profile is okay, but some description, attribution, license, or supported platform notes should be corrected.
  3. You’d prefer to publish or maintain the ForgeCat profile directly.
  4. You’d prefer that we remove this ForgeCat profile.

If you prefer removal, we can take it down.

Getting Started:

npm install -g forgecat
forgecat search <keyword>
forgecat install @forgecat/cursor_plugins_continual-learning
forgecat install @forgecat/cursor_plugins_ralph-loop
forgecat install @forgecat/cursor_plugins_team-kit

Docs: https://forgecat.ai/docs

Thanks, and happy to adjust anything that doesn’t represent the original project accurately.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository file, test, or entry point; start by reviewing the linked ForgeCat profile repository and the Cursor plugins collection. Done would require an explicit project decision about whether the profiles may remain and any attribution, license, description, or platform corrections.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.