pkslisted

<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 ```bash 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 penandatang