chore(skills): register recoup-platform-email-helper as a default sandbox skill

[sweetmantech]

What

One-line registration of the new recoup-platform-email-helper skill in lib/skills/defaultGlobalSkillRefs.ts, so installGlobalSkills provisions it into every session sandbox at create time (~/.agents/skills/recoup-platform-email-helper/).

Why

The helper (a zero-dep Node send-email.mjs) replaces agents' fragile hand-built curl … -d "{…}" email sends, the cause of the empty footer-only "Message from Recoup" emails. It isn't available in sandboxes until it's in this default set.

Merge order

Land recoupable/skills#67 first. installGlobalSkills runs npx skills add recoupable/skills --skill recoup-platform-email-helper, which throws on an unknown name (per the comment in this file / recoupable/chat#1815).

Part of recoupable/chat#1829. Base test per repo convention.

🤖 Generated with Claude Code

---

Summary by cubic

Registers recoup-platform-email-helper as a default global skill so installGlobalSkills provisions it into every session sandbox at create time. Pairs with recoup-platform-api-access to send email via a tested Node helper instead of fragile curl payloads. Also adds a test to assert the email helper is included in defaults.

^{Written for commit 96ce178. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api	Ready	Preview	Jul 1, 2026 12:17am

[coderabbitai]

Warning

Review limit reached

@sweetmantech, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2caa28f4-9e8e-4c7b-a6df-6dd0e2057a95

📥 Commits

Reviewing files that changed from the base of the PR and between f8d5dc2 and 96ce178.

⛔ Files ignored due to path filters (1)

• lib/skills/__tests__/defaultGlobalSkillRefs.test.ts is excluded by !**/*.test.*, !**/__tests__/** and included by lib/**

📒 Files selected for processing (1)

• lib/skills/defaultGlobalSkillRefs.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/register-email-helper-skill

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 5/5

• In lib/skills/defaultGlobalSkillRefs.ts, the tests currently don’t assert that recoup-platform-email-helper is included, so a future refactor could accidentally drop this default ref without CI catching it; add an explicit assertion for this skill before merging to close the coverage gap.

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[sweetmantech]

Rebased onto main + verified — 96ce1784

Rebased onto latest main (was BEHIND by the #729/#731 merges; no conflict — #730 only touches lib/skills/defaultGlobalSkillRefs.ts). Added a test asserting recoup-platform-email-helper is in DEFAULT_GLOBAL_SKILL_REFS (the entry previously had no assertion covering it). Skills suite green (49); tsc + eslint clean.

Roll-over from the merged PRs — none needed. #730 only registers the skill slug; it doesn't touch the email endpoint (#729/#731) or the DB (#37/#38). The one hard dependency is skills#67 — the helper must exist so the install resolves — which is merged and verified below.

Verification approach. This change is exercised at sandbox-provision time: installGlobalSkills runs, per ref, npx skills add recoupable/skills --skill <name> … --copy and throws on the first failure. So the real risk #730 introduces is purely whether that exact command now resolves the new skill. Ran it against the live registry:

$ npx skills add recoupable/skills --skill recoup-platform-email-helper --agent amp -g -y --copy
◇  Found 32 skills
◇  Installation complete
✓ recoup-platform-email-helper (copied) → ~/.agents/skills/recoup-platform-email-helper
└  Done!

Resolves and installs cleanly → sandbox provisioning won't throw, and every new sandbox now ships the email helper next to recoup-platform-api-access.

Preview: https://api-fumropx26-recoup.vercel.app — Ready, built from 96ce1784. Note: the registration only manifests when a sandbox is actually provisioned (a background / agent-run path), so there's no single preview HTTP request that surfaces it — the exact npx skills add above is the meaningful proxy for what the preview build will run.

[sweetmantech]

End-to-end verified in a live preview sandbox 🎯

Fired a real task run against the preview deployment (POST /api/chat/runs, built from 96ce1784) under the personal account, recipient sweetmantech@gmail.com only. This provisions a sandbox from this PR's code — so the registration is actually exercised.

The agent, with no curl fallback, ran:

RECOUP_API_BASE=https://api-fumropx26-recoup.vercel.app \
node /home/vercel-sandbox/.agents/skills/recoup-platform-email-helper/scripts/send-email.mjs \
  --to sweetmantech@gmail.com --subject "HelloWorld-PVW-…" …

What this proves, in order:

• chore(skills): register recoup-platform-email-helper as a default sandbox skill #730 registration works — the helper was present at ~/.agents/skills/recoup-platform-email-helper/ in the freshly-provisioned sandbox (it's in DEFAULT_GLOBAL_SKILL_REFS, so installGlobalSkills installed it at startup without throwing).
• The agent used the helper (node …/send-email.mjs), zero hand-rolled curl — the exact behavior the helper exists to enforce.
• Send succeeded → email_send_log sent row (resend_id 023f977f…, full correctly-serialized raw_body), delivered only to the owner. (feat(emails): log every POST /api/emails attempt (email_send_log, 7-day observability) #731 observability + fix(emails): reject empty/unparseable POST /api/emails bodies (no silent footer-only sends) #729 guard both in the loop.)

Control: a run fired against prod (no #730) with the same preview-base-URL instruction produced rejected (401) rows for the preview attempts — confirming the effect is specific to the preview build carrying this PR. All test rows deleted.

tl;dr: register → install-at-provision → agent picks up the helper → reliable send, verified in a real sandbox. Ready to merge.