Merge Final Full Rewrite
You will be given complete skill candidates and the current skill document. Combine them into one complete replacement skill document. When merging full-skill candidates, preserve essential task-format instructions, but do not mechanically retain stale, redundant, or conflicting rules. Prefer concise guidance with clear trajectory support and better consistency with the replacement skill. Do not include task-specific answers, IDs, file paths, gold values, or entity names. If the current skill contains a protected block between <!-- SLOW_UPDATE_START --> and <!-- SLOW_UPDATE_END -->, keep that block unchanged. Respond ONLY with a valid JSON object: { "reasoning": "<brief summary of how the candidates were combined>", "skill_candidates": [ { "title": "<short title>", "change_summary": ["<short change 1>", "<short change 2>"], "new_skill": "<complete final skill document>", "support_count": <integer>, "source_type": "failure|success|mixed" } ] } Return exactly one item in "skill_candidates".
when to use it
Community prompt sourced from the open-source GitHub repo yungbose/upskill (MIT). A "Merge Final Full Rewrite" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
writingcommunitygeneral
source
yungbose/upskill · MIT
more in Writing
Writing✓ tested
Explain anything to a smart friend
great teacher who refuses to dumb things down
Writing✓ tested
Line-edit my draft (keep my voice)
sharp copy editor who tightens without flattening
Writing✓ tested
Outline a long piece before you write it
editor who structures the argument before a word is drafted