pks
Skill4 starsChanged 6 months agoMITView on GitHub
Generate PKS (Cooperation Agreement / Perjanjian Kerja Sama) DOCX by filling the official UPI template's partner placeholders
In this repository5 other files it gives its agents.
- initSkill
- laporan-compileSkill
- laporanSkill
- logbookSkill
- penilaian-penyeliaSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 19
Only the partner side (PIHAK KEDUA) and the date are variable — exactly the fields highlighted yellow in the source template.
- Distinctive: line 38
If missing → "Jalankan /rpl-magang:init dulu." Stop.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
<objective>
Generate a PKS (Perjanjian Kerja Sama) DOCX by filling ONLY the partner-specific placeholders in the official UPI template — mirroring the manual workflow of replacing the yellow-highlighted fields in the reference PKS. The legal text (all pasal) and the PIHAK KESATU / UPI side stay verbatim. Output: PKS_[Company].docx
</objective><workflow-note>
This skill does NOT regenerate the agreement text. It fills a tokenized
copy of the official template (`~/.claude/magang-tools/templates/pks_template.docx`).
Only the partner side (PIHAK KEDUA) and the date are variable — exactly the
fields highlighted yellow in the source template. PIHAK KESATU (UPI / KARIM
SURYADI / Direktur) and every pasal are fixed in the template; never ask for
them.
</workflow-note><constants>
CONFIG_PATH = ~/.claude/magang-tools/config.json
PYTHON = ~/.claude/magang-tools/venv/bin/python
PKS_SCRIPT = ~/.claude/magang-tools/scripts/generate_pks.py
</constants><steps>Step 1 — Check config
test -f ~/.claude/magang-tools/config.json && echo "ok" || echo "missing"If missing → "Jalankan /rpl-magang:init dulu." Stop.
Config pks_template_path (null = bundled official template, the default).
Step 2 — Collect partner (PIHAK KEDUA) information
Jika config.json punya student_identity.mitra, pakai sebagai default nama
perusahaan (PIHAK KEDUA) — konfirmasi, jangan tanya ulang dari nol.
Ask:
- Nama perusahaan/instansi lengkap (mis. PT/CV/Yayasan ...)
- Nama penandatangan pihak perusahaan (nama lengkap, biasanya HURUF KAPITAL)
- Jabatan penandatangan (mis. Direktur / Kepala Divisi ...)
- Alamat lengkap perusahaan
- Nomor telepon (ketik "-" kalau tidak ada)
- Fax (ketik "-" kalau tidak ada)
- Wilayah/kota perusahaan (untuk frasa "di wilayah ___", contoh: Jakarta)
Step 3 — Agreement date (terbilang + numeric)
The template spells the date out in words AND digits. Ask the student for each part (manual, no auto-conversion):
- Hari (contoh: Senin)
- Tanggal terbilang (contoh: Satu — atau "Dua Puluh Tiga")
- Bulan (contoh: Juni)
- Tahun terbilang (contoh: Dua Ribu Dua Puluh Enam)
- Tanggal numerik dd-mm-yyyy (contoh: 01-06-2026)
Step 4 — Generate DOCX
Build the data JSON with these exact keys, then write to a temp file
/tmp/pks_data_[timestamp].json:
{
"partner_org_upper": "<NAMA PERUSAHAAN HURUF KAPITAL>",
"partner_org_sub": "",
"partner_org": "<Nama Perusahaan Title Case>",
"partner_rep_name": "<NAMA PENANDATANGAN>",
"partner_rep_title": "<Jabatan penandatangan>",
"partner_address": "<Alamat lengkap>",
"partner_phone": "<Telepon>",
"partner_fax": "<Fax>",
"partner_email": "<Email>",
"partner_region": "<Wilayah/kota>",
"date_hari": "<Hari>",
"date_tgl_word": "<Tanggal terbilang>",
"date_bulan": "<Bulan>",
"date_tahun_word": "<Tahun terbilang>",
"date_numeric": "<dd-mm-yyyy>"
}partner_org_upper= all-caps (header).partner_org= title case (inline + signature).partner_org_sub= usually "" (only for a sub-unit line; leave blank).
Output path: --output-dir if given, else current dir. Filename
PKS_[NamaPerusahaan_tanpa_spasi].docx.
Run:
~/.claude/magang-tools/venv/bin/python ~/.claude/magang-tools/scripts/generate_pks.py \
--data /tmp/pks_data_[timestamp].json \
--output "[output_path]"(The generator uses the bundled official template automatically; pass
--template [pks_template_path] only if config sets a custom one.)
Parse output JSON → final path (auto-versioned). Cleanup temp file.
Step 5 — Summary
✅ PKS berhasil dibuat dari template resmi!
File : [output_path]
Pihak 1: KARIM SURYADI (Direktur, UPI Cibiru) — tetap dari template
Pihak 2: [rep_name] ([rep_title], [company])
Tanggal: [hari], [date_numeric]
Next steps:
1. Buka DOCX, sisipkan logo UPI + logo perusahaan secara manual
2. Isi nomor dokumen kedua pihak (NOMOR: ___)
3. Print 2 rangkap, tempel materai, tanda tangan kedua pihak
4. Scan → simpan sebagai PKS_[NamaPerusahaan].pdf</steps>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.

