Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/generate-translations
Use when new translation keys are added to packages to generate new translations strings
Passed 17 of 22 test cases with the skill, and 8 of 22 without it.
and 15 more in the full report
9 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm adding a frontend-accessible string to Payload core translations. Should I format the key as `authentication.newFeature` with dot notation in `packages/translations/src/clientKeys.ts` or is a different delimiter required?
| Checked | Without skill | With skill |
|---|---|---|
| specifies colon notation such as authentication:newFeature for client keys | Missed | Passed |
| specifies packages/translations/src/clientKeys.ts as the file location | Passed | Passed |
The instructions your model reads when the skill loads.
Payload has two separate translation systems:
When to use: Adding translations to core Payload packages (packages/ui, packages/payload, packages/next)
Add the English translation to packages/translations/src/languages/en.ts
authentication, general, fields, etc.)export const enTranslations = {
authentication: {
// ... existing keys
newFeature: 'New Feature Text',
},
}
Add client key (if needed for client-side usage) to packages/translations/src/clientKeys.ts
'authentication:newFeature'test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.