ForgeCat profiles for Claude plugins

Hi Anthropic 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 official Claude plugin workflows useful for reusable agent setup, so we created initial ForgeCat profiles for them here:

Profile repo: https://github.com/nota-america/forgecat-agent-profiles/tree/main/profiles/anthropics/claude-plugins-official
Install example: `forgecat install @forgecat/anthropics_claude-plugins-official_agent-sdk-dev`

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:

```bash
npm install -g forgecat
forgecat search
forgecat install @forgecat/anthropics_claude-plugins-official_agent-sdk-dev
```

Docs: https://forgecat.ai/docs

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

Review the linked ForgeCat profile repository and its install example, then compare them with the official Claude plugin workflows in this repository. The issue is asking for a maintainer decision about accuracy, attribution, licensing, platform notes, publication, or removal; it is done when that preference is recorded and any requested follow-up is identified.

Escrito por el modelo de indexación a partir del texto del issue.