#297 ForgeCat profiles for Vercel agent skills

Hi Vercel 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 Vercel agent skills useful for deployment, React/Next.js practices, and web design guidance workflows, so we created initial ForgeCat profiles for them here:

Profile repo: https://github.com/nota-america/forgecat-agent-profiles/tree/main/profiles/vercel-labs/agent-skills

Install example:

forgecat install @forgecat/vercel-labs_agent-skills_deploy-to-vercel
forgecat install @forgecat/vercel-labs_agent-skills_react-best-practices
forgecat install @forgecat/vercel-labs_agent-skills_web-design-guidelines

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?

The current ForgeCat profile is okay as-is.
Keeping the profile is okay, but some description, attribution, license, or supported platform notes should be corrected.
You’d prefer to publish or maintain the ForgeCat profile directly.
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/vercel-labs_agent-skills_deploy-to-vercel
forgecat install @forgecat/vercel-labs_agent-skills_react-best-practices
forgecat install @forgecat/vercel-labs_agent-skills_web-design-guidelines

Docs: https://forgecat.ai/docs

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