TokenPad
Prompts

System Prompt to Skills Splitter

Find the conditional instructions you are paying for on every request.

Your input

418 characters9 lines0 tokensor drop a file

Prompt SplitterExact
0Token change
Token change0no change
Input tokens0what you pasted
Output tokens0what you would send
Token cost of this result
Output tokens0
As input$0.00
× 100K requests$0.00

Everything on this page runs in your browser. Nothing you paste is transmitted, because there is no server here to transmit it to.

Result

The rule underneath

Instructions in a system prompt are paid for on every request forever. Instructions in a skill are paid for only when the skill triggers. So anything needed on most requests belongs in the prompt, and anything conditional belongs in a skill.

Teams get this backwards constantly, because the system prompt is the obvious place to put a fix when something goes wrong.

How the split is decided

Sections beginning with "when", "if" or "for" describe conditional behaviour, and those above the size threshold are flagged as extraction candidates. It is a heuristic, not a judgement — read the output and disagree with it where it is wrong.

The saving shown is per request. Multiply it by your monthly volume before deciding whether the restructuring is worth doing at all.

Frequently asked questions

Should every conditional instruction become a skill?
No. Small ones are cheaper left in place than paid for as a separate load, and splitting has its own overhead in maintenance. The size threshold exists for exactly that reason.
What if a section is needed on half of requests?
Leave it in the prompt. A skill that triggers half the time costs its description on every request plus its body on half of them, which is worse than simply keeping it.

More prompts tools