Skip to content

feat: improve skill scores for react-email#3053

Open
popey wants to merge 1 commit intoresend:canaryfrom
popey:improve/skill-review-optimization
Open

feat: improve skill scores for react-email#3053
popey wants to merge 1 commit intoresend:canaryfrom
popey:improve/skill-review-optimization

Conversation

@popey
Copy link

@popey popey commented Mar 11, 2026

Hullo @resend 👋 - me again! :D

As with resend/email-best-practices#10 and resend/resend-skills#30 I ran your skills through tessl skill review at work and found some targeted improvements.

Here's the before/after for this repo:

Skill Before After Change
react-email 79% 93% +14%
Changes made
  • Expanded frontmatter description — added explicit capability verbs ("Creates, previews, and sends responsive HTML email templates") so agents can better identify when to activate the skill
  • Consolidated installation section — collapsed four separate package manager listings across three steps (~60 lines) into a single concise block with a note about alternatives, resolving the line-count warning (530 → 463 lines)
  • Added STYLING.md reference — linked the existing but unreferenced references/STYLING.md from the styling section for better progressive disclosure
  • Resolved validation warning — SKILL.md now passes all checks with 0 errors and 0 warnings

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @popey - if you hit any snags.

Thanks in advance 🙏


Summary by cubic

Improves the react-email skill docs to make activation and setup clearer, raising the skill review score from 79% to 93%. Simplifies installation, clarifies capabilities, and links styling docs; validation now passes with no warnings.

  • Refactors
    • Expanded frontmatter with capability verbs (create, preview, send responsive HTML emails).
    • Consolidated install/start steps into a single create-email flow with notes for yarn/pnpm/bun; trimmed 67 lines and removed the line-count warning; clarified the preview at localhost:3000.
    • Linked references/STYLING.md from the styling section; SKILL.md now validates with 0 errors and 0 warnings.

Written for commit 85083a5. Summary will update on new commits.

Hullo @resend 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| react-email | 79% | 93% | +14% |

<details>
<summary>Changes made</summary>

- **Expanded frontmatter description** — added explicit capability verbs ("Creates, previews, and sends responsive HTML email templates") so agents can better identify when to activate the skill
- **Consolidated installation section** — collapsed four separate package manager listings across three steps (~60 lines) into a single concise block with a note about alternatives, resolving the line-count warning (530 → 463 lines)
- **Added STYLING.md reference** — linked the existing but unreferenced `references/STYLING.md` from the styling section for better progressive disclosure
- **Resolved validation warning** — SKILL.md now passes all checks with 0 errors and 0 warnings

</details>

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@popey](https://github.com/popey) - if you hit any snags.

Thanks in advance 🙏
@vercel
Copy link

vercel bot commented Mar 11, 2026

@popey is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot
Copy link

changeset-bot bot commented Mar 11, 2026

⚠️ No Changeset found

Latest commit: 85083a5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant