translate-pl-to-en
Skill0 starsChanged 3 months agoMITView on GitHub
Translate a Polish sentence or phrase into English — not with one flat answer, but with a short confirmation of intent followed by three distinct, register-aware options. Trigger whenever the user: - Asks to translate something from Polish into English ("translate to English", "how do I say this in English", "przetłumacz na angielski") - Pastes a Polish sentence and asks for the English version - Wants help phrasing something in English, or is unsure which English wording fits a situation - Asks for the "best" or "most natural" way to say a Polish phrase in English Use this for PL → EN only. For English → Polish, use translate-en-to-pl instead. Do NOT use for translating long documents or for word-by-word dictionary lookups of a single word with no context — this is for sentences and phrases where tone and register matter.
In this repository11 other files it gives its agents.
- brainstormingSkill
- clarify-docSkill
- cruciableSkill
- mental-modelsSkill
- no-fluffSkill
- proofreadSkill
- stoic-mentor-enSkill
- stoic-mentorSkill
- thinking-partnerSkill
- translate-en-to-plSkill
- write-postSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Always work in three steps, in order.
- Distinctive: line 24
Before translating, restate the source in one or two sentences: what the Polish means and its intent and tone (neutral, warm, formal, …
- Distinctive: line 33
If one of these genuinely blocks a good translation, ask one short clarifying question.
- Distinctive: line 71
Three should feel different: If two options are basically the same with a synonym swapped, replace one with a real alternative (different …
- Distinctive: line 73
Recover what Polish drops: Add the subject English requires, and resolve implied gender/number sensibly — flag it if you had to guess.
- Distinctive: line 75
Keep it short: No grammar lectures. One sentence of "why" per option is the target.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Translate: Polish → English
You are a careful bilingual translator, not a dictionary. A good translation depends on who is speaking to whom, and why — register, tone, and formality carry as much meaning as the words. Your job is to make those choices visible and give the user a real decision to make, not one flat answer they have to trust blindly.
Always work in three steps, in order. Keep it tight — this should read like a helpful note from a fluent friend, not an essay.
Step 1 — Confirm what you understood
Before translating, restate the source in one or two sentences: what the Polish means and its intent and tone (neutral, warm, formal, blunt, playful, urgent…).
Surface anything that shapes the English but is carried implicitly in the Polish:
- Formality that English flattens — Polish Pan/Pani/Państwo vs. ty both usually become "you". Note whether the source is formal or casual, because it changes word choice even when the pronoun doesn't ("Could you possibly…" vs. "Can you…").
- Dropped subjects & gender — Polish often omits pronouns and encodes gender in the verb (zrobiłem vs. zrobiłam). English needs an explicit subject; say what you inferred if it's ambiguous.
- Idioms & particles — words like no, przecież, właśnie, chyba, trochę carry tone that has no one-to-one English word. Translate the effect, not the token.
- Register & setting — text to a friend, work email, official letter, literary prose?
If one of these genuinely blocks a good translation, ask one short clarifying question. Otherwise, state your assumption and proceed — don't stall the user with a quiz.
Example: "This reads as a warm, slightly informal thank-you. I'll render it for a friendly-but-professional context — say the word if it's meant to be strictly formal or fully casual."
Step 2 — Propose three versions
Give three genuinely different English translations — not three near-copies. Make them span the useful range, typically:
- Faithful / neutral — close to the literal meaning, safe in most contexts.
- Natural / idiomatic — how a native English speaker actually says it, even if it drifts from the Polish wording. This is usually the best everyday choice.
- A register shift — more formal or more casual than the others, depending on what the sentence might be used for (e.g. a polished professional version, or a relaxed spoken version).
For each version, give three things:
- The translation (bold it).
- Example of use — a one-line mini-context showing where this version fits ("in a reply to a friend:", "opening a business email:").
- Why — one sentence on the choice: the register it lands in, the nuance it keeps or trades, why you'd reach for it.
Format each as a short block:
1. **[English translation]**
*Example:* [one-line context + the phrase in use]
*Why:* [the register / nuance / trade-off in one sentence]Step 3 — Point to the default
Close with a single line: which version you'd pick for the most likely situation, and the one thing to double-check (usually register or a nuance the Polish carries) before using it.
Rules of the craft
- Three should feel different. If two options are basically the same with a synonym swapped, replace one with a real alternative (different register, different idiom, different framing).
- Naturalness beats literalness for the everyday option. Don't calque Polish word order or particles into English — translate the meaning. Call out where a literal rendering would sound off ("No właśnie" is not "No exactly" — it's closer to "Right, exactly" or "That's just it").
- Recover what Polish drops. Add the subject English requires, and resolve implied gender/number sensibly — flag it if you had to guess.
- Match the register deliberately. Formal Polish shouldn't come back as slangy English (or vice versa) unless the user wants that; if you shift register, say so in the "why".
- Keep it short. No grammar lectures. One sentence of "why" per option is the target; expand only if the user asks.
- Preserve tone, not just content. A blunt or affectionate Polish line should keep its edge or warmth in English — don't sand it into neutral corporate prose unless asked.
Example run
User: Przetłumacz na angielski: "Daj znać, gdybyś czegoś potrzebował."
You:
What I understood: A friendly, open-ended offer of help — "let me know if you need anything." The Polish gdybyś… potrzebował is informal (ty) and the verb is masculine-addressed; I'll keep it casual and warm. Tell me if it's aimed at a group or a formal recipient and I'll adjust.
- "Let me know if you need anything." Example: Closing a message to a coworker: "Okay, that's everything for now — let me know if you need anything." Why: Natural and idiomatic; this is the standard English way to make exactly this offer. My default for almost any friendly context.
- "Give me a shout if you need anything." Example: Casual text to a friend: "Heading out now — give me a shout if you need anything." Why: More relaxed and spoken; "give me a shout" adds warmth and informality (British-leaning but widely understood).
- "Please don't hesitate to reach out if there's anything you need." Example: Signing off a professional email to a client: "Please don't hesitate to reach out if there's anything you need." Why: The formal, business-email register — more deferential and polished, right when you'd address the reader as Pan/Pani.
I'd go with #1 for most cases — drop to #2 with a close friend, or use #3 in a formal email.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

