content-editor
Skill1 starsChanged 44 days agoMITView on GitHub
Use this skill to edit, polish, or quality-control content someone else (or an earlier draft) produced - "edit tulisan ini", "rapikan draft", "proofread", "perbaiki flow", "terlalu panjang, pangkas", fact-check request, tone adjustment, or final review before publishing. The quality gate. Do NOT use to create content from scratch (content-creator) or schedule it (social-media-specialist).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- felixgeelhaar/skillstheir own version, first seen Jun 4, 2026
- jjneely/skillstheir own version, first seen Mar 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- felixgeelhaar/skills★ 1same name
- jjneely/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accounting-coreSkill
- admin-opsSkill
- agent-skill-authorSkill
- code-review-hardeningSkill
- content-creatorSkill
- continuous-learningSkill
- coo-orchestratorSkill
- finance-analystSkill
- hr-adminSkill
- hr-officerSkill
- incident-debuggingSkill
- marketing-growthSkill
- prd-creatorSkill
- principal-engineeringSkill
- product-designerSkill
- project-auditSkill
- project-timeline-creatorSkill
- sales-pipelineSkill
- sdlc-masterSkill
- secure-deploy-opsSkill
- social-media-specialistSkill
- strategic-approachSkill
- tech-scoutSkill
- uiux-engineerSkill
The file
Files
Content Editor
Editing is triage in the right order: structure → clarity → style → correctness. Fixing commas in a paragraph that should be deleted is wasted work. The editor serves the reader, then the author's voice - in that order, and never the reverse.
Pass 1 - Structural edit (the big knife)
- Apa janji tulisan ini, dan apakah terbayar? Kalau tidak - masalahnya bukan di kalimat.
- Urutan: apakah tiap bagian mengalir dari sebelumnya? Bagian yang bisa dipindah tanpa ada yang rusak = sinyal struktur lemah.
- Pembukaan: nilai mulai di paragraf berapa? Semua sebelum itu → calon potong. Kebanyakan draft membaik dengan menghapus 1-2 paragraf pertama.
- Duplikasi ide: satu ide muncul 2× di tempat berbeda → gabung di tempat terkuat.
- Yang hilang: klaim besar tanpa contoh/bukti? Langkah yang lompat? Tandai, minta/isi.
Pass 2 - Clarity edit (per paragraph)
- Satu paragraf satu ide; kalimat > 25 kata dipecah kecuali ritmenya disengaja.
- Kata kerja aktif > pasif ("tim merilis fitur" > "fitur dirilis oleh tim") kecuali pelaku memang tak penting.
- Buang kata bantalan: "pada dasarnya", "sebenarnya", "cukup", "sangat", "tentu saja", "seperti yang kita ketahui".
- Jargon: pertahankan istilah teknis yang dibutuhkan audiens, terjemahkan sisanya. Uji: apakah target pembaca berhenti dan mengernyit?
- Angka & klaim: spesifik mengalahkan umum - "3 dari 5 klien" bukan "banyak klien" (kalau datanya ada; kalau tidak ada, jangan diciptakan).
Pass 3 - Style & voice
- Konsistensi register dari awal sampai akhir (formal ↔ santai tidak boleh loncat).
- Pertahankan suara penulis: edit yang membuat semua tulisan terdengar sama adalah edit yang gagal. Perbaiki kejelasan, jangan setrika kepribadian.
- Ritme: variasikan panjang kalimat; tiga kalimat berpola sama berturut = monoton, ubah satu.
- Buang AI-flavor & klise: pembuka "di era digital", penutup moral generik, "selain itu" beruntun, triplet sifat berulang.
Pass 4 - Correctness (last, line by line)
- Fakta: nama, angka, tanggal, klaim yang bisa diverifikasi - cek atau tandai
[VERIFIKASI: ...]. Jangan pernah meloloskan angka yang tak jelas sumbernya. - Ejaan & tanda baca (untuk ID: sesuai PUEBI - "di" awalan vs kata depan, "nya", huruf kapital gelar/nama).
- Link hidup, nama produk/orang benar ejaannya, format konsisten (tanggal, mata uang, kapitalisasi judul).
- Legal/etika: klaim berlebihan ("dijamin", "terbaik #1" tanpa dasar), testimoni tanpa izin, gambar tanpa hak - tandai, jangan loloskan.
Delivery format
Untuk edit ringan: kembalikan versi bersih + daftar singkat perubahan besar. Untuk edit berat:
## Verdict: [siap terbit / perlu revisi ringan / perlu restrukturisasi]
## Perubahan struktural yang kulakukan/usulkan (dengan alasan per item)
## Pertanyaan ke penulis (fakta yang harus diverifikasi, bagian ambigu)
## Versi tereditAturan emas: setiap perubahan substansial bisa dijelaskan alasannya dalam satu kalimat. "Kurasa lebih enak" bukan alasan; "janji judul tidak terbayar tanpa bagian ini" adalah alasan.
Kill criteria (when to reject, not edit)
Premis salah/menyesatkan · plagiarisme · data tak bisa diverifikasi dan penulis tak bisa menyediakan · isi tak sesuai audiens/brand meski ditulis bagus. Menolak dengan alasan jelas lebih murah daripada menerbitkan lalu menarik.
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.

