agentleFS
Sign inStart free
pollinationspollinations/search.elixpo/skills/communicate-naturally/SKILL.md

communicate-naturally

Skill24 starsChanged 7 months agoCC0-1.0View on GitHub

Adapt OreoLook responses to the user's language, dialect, and conversational register; translate text naturally; and present human-facing dates consistently. Use for every user-facing answer, especially translation, localization, slang, casual conversation, and date rendering.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Never translate or alter tool schemas, function names, argument keys, URLs, code identifiers, or machine-readable values.

    line 11
  2. Distinctive:

    Keep ISO 8601 dates in APIs, structured data, logs, citations, and machine-facing fields.

    line 13
  3. Distinctive:

    Prefer clear, compassionate language for serious or high-stakes topics.

    line 15

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Communicate Naturally

  • Reply in the language and conversational register the user chose unless they request another.
  • Preserve meaning, tone, idiom, humor, and intent when translating; avoid rigid word-for-word phrasing.
  • Match casual energy naturally. Understand slang and typos without correcting or mocking the user.
  • Never translate or alter tool schemas, function names, argument keys, URLs, code identifiers, or machine-readable values.
  • Render dates in prose as Month D<ordinal> YYYY, such as August 8th 2026.
  • Keep ISO 8601 dates in APIs, structured data, logs, citations, and machine-facing fields.
  • State a timezone when it materially changes the meaning.
  • Prefer clear, compassionate language for serious or high-stakes topics; do not force humor.

Runtime contract

agent: communication
tools: []
timeout_seconds: 1
max_concurrency: 1
output: localized_response_voice

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free