agentleFS
Edzard9Edzard9/stash/skills/writing/proofread-id/SKILL.md

proofread-id

Skill0 starsChanged 8 days agoMITView on GitHub

Proofread formal Indonesian (Bahasa Indonesia) for assignments and reports: spelling (EYD/PUEBI), effective sentences, standard terms, punctuation, and the classic affix-spacing traps. Edits language only, never content. Use when the user asks to proofread or tidy Indonesian text, or says "proofread", "cek ejaan", "rapikan bahasa", "sunting tugas", "periksa bahasa laporan". Do NOT use to rewrite arguments, translate, or change what the text says.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Istilah baku: Prefer the standard term where the draft uses a colloquial one in a formal context (menggunakan, not memakai, where the …

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Proofread ID

A proofread that changes the argument is not a proofread; it is a rewrite wearing the wrong name. This skill edits the language of formal Indonesian text (assignments, practicum reports, academic writing) and touches nothing else: not the facts, not the numbers, not the structure the author chose, not their voice beyond making it correct.

What gets fixed

  1. Ejaan (EYD/PUEBI). Capitalization, standard spellings, loanword forms (sistem, kualitas, aktivitas), and punctuation, including the decimal comma in Indonesian numbers (3,60, not 3.60).
  2. The affix traps. The ones that appear in nearly every draft:
    • di- as a prefix (attached: ditulis, dipakai) versus di as a preposition (separate: di kelas, di atas).
    • ke-/-kan confusions, and pun spacing (apa pun, mana pun separate; walaupun, meskipun attached).
    • Redundant pairs: "agar supaya", "demi untuk", "seperti misalnya" (choose one).
  3. Kalimat efektif. Cut filler that adds no meaning ("pada dasarnya", "yang mana" chains), fix subjectless formal sentences, untangle doubled conjunctions ("karena ... maka ..."), and keep one idea per sentence in reports.
  4. Istilah baku. Prefer the standard term where the draft uses a colloquial one in a formal context (menggunakan, not memakai, where the register demands it), while leaving established technical terms (VLAN, router, server) untouched.
  5. Consistency. One spelling per term per document, one style for lists and numbering, one form for the identity block and headings.

What never gets touched

  • Facts, numbers, names, addresses, and results. A wrong number is the author's business; if one looks wrong, flag it in a note, do not silently correct it.
  • The author's structure and section order, unless they asked for restructuring.
  • Quoted material, commands, code, and anything inside them.

How the result is delivered

  • The cleaned text, complete, as a finished file or full text, never as fragments the user must reassemble.
  • A short change list grouped by type (ejaan, imbuhan, kalimat), with counts, not a line-by-line dump. Example: "di- terpisah diperbaiki 4x, koma desimal 2x, satu kalimat dipecah dua."
  • Anything flagged-but-not-changed (suspect facts, ambiguous terms) listed separately, so the author decides.

Tone

Formal Indonesian still sounds like a person. The target register is the relaxed academic Indonesian of a good practicum report: correct, clear, and short. Over-formalizing into stiff bureaucratic Indonesian is a failure mode of this skill, not its goal.

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.