Would you accept an infrastructure-category skill in awesome_agent_skills?

[eyal-gor]

Hi — quick scoping question before I open a PR.

All 16 entries in awesome_agent_skills/ today are domain skills (python-expert, deep-research, editor, debugger…). Categories: Coding / Research / Writing / Planning / Data Analysis.

I'd like to add cerver — but it's an infrastructure skill, not a domain one. It gives agents:

• Persistent memory — every session is an append-only transcript that survives restarts; sibling agents on the same account can read it
• Sandboxed compute — POST a task and it runs on a local relay / Vercel sandbox / E2B
• Unified secrets — secret_fetch(name) over Infisical; the agent never sees raw API keys

It ships in the standard SKILL.md format already, so it'd drop into a new folder cleanly. The mismatch is conceptual, not structural — would you accept a PR that:

1. Adds awesome_agent_skills/cerver/SKILL.md
2. Introduces a new section in awesome_agent_skills/README.md (something like "### 🧩 Infrastructure" or "### 🛠️ Tools & State") with cerver as the first entry, leaving room for future infra-style skills?

If the answer is "yes, but use this section name instead" or "yes but skip the README change and just add the folder" — happy to follow whichever shape works for you. If it's a no (out of scope), no problem, won't waste anyone's review time.

Thanks!

[Shubhamsaboo]

Thanks for asking first, that's appreciated. cerver is a hosted commercial infrastructure product, so adding it would amount to a link to an external service rather than a self-contained skill with its own runnable content in this repo. That puts it out of scope for awesome_agent_skills, so it's a no on this one. Thanks for understanding, and for not spending review time before checking.

---

Generated by Claude Code