I'm Jelly of Python (Cops) What does &quot;jelly&quot; mean in the title?. Robber's thread
Jelly has an &quot;Evaluate the argument as Python 3&quot; atom, ŒV which takes a string as an argument as evaluates that string as Python 3 code: Try it online!.
It also has compressed strings, delimited with “...» that can compress any string containing printable ASCII (plus newlines), which can reduce the size of such programs. For example, a Hello, World! program using ŒV
Now, this is much longer that Jelly's normal Hello, World! program, by 9 bytes. But is this always the case?
Cops, you are to choose an code-golf challenge; write a Python solution to this challenge; compress that solution into Jelly and submit that as your answer.
The challenge you choose must meet these criteria:

It is open
It it unlocked
It has a net score of 5 or more
Its winning criteria is code-golf and only code-golf
All languages are open to compete in it (so no python-only challenges etc.)
It is not a tips question
It was posted before the 28th of March, 2021

This is a search query that should return (mostly) valid challenges. There's no way to filter challenges on the 4th and 5th criteria, so double check the challenges you choose from this search.
Your answer should contain:

A piece of Jelly code in the format “...»ŒV, where the ... may be any string of characters from Jelly's code page, aside from “”‘’«»
A link to the challenge you solved
The length of your &quot;Python to Jelly&quot; code, in bytes

Note that your program must follow any and all rules stated in the challenge you solve, including builtin bans, strict I/O formats and whatever else. To fully cover all edge cases: Your program must be able to be posted as a valid answer to the challenge. The only exception to this rule is that if the challenge scores in characters, you should instead score in bytes.
Jelly currently is written in Python 3.7.4 (Try it online!, the same version that TIO's Python 3 uses), so your program must work in that version of Python.
You may not edit the rules of the challenge you've chosen. You may not simply compress an existing Python answer to the challenge and submit that as your own work. However, you are allowed to attempt to modify existing users' code in order to improve your score, so long as you provide proper attribution to the original answerer. Alternative wording.
Your answer is &quot;cracked&quot; if a Robber finds a Jelly program shorter than your &quot;Python to Jelly&quot; program, that completes the same task. Note that a Robber's crack is valid even if it's of the same form (compressed Python eval'ed by Jelly), so long as it's shorter.
Your answer is &quot;safe&quot; if it is uncracked after 2 weeks. You must mark your answer as safe to be considered so. The shortest safe answer, in bytes, wins
This is, as far as we know, the most optimal Jelly compressor which might help you
Example submission
# 17 bytes, solves https://codegolf.stackexchange.com/questions/55422/hello-world

    “¤ṙẋȯ½Ġ&lt;rŻ£ƤḤO»ŒV

[Try it online!][TIO-kmrxghbo]

[TIO-kmrxghbo]: https://tio.run/##ASsA1P9qZWxsef//4oCcwqThuZnhuovIr8K9xKA8csW7wqPGpOG4pE/Cu8WSVv// &quot;Jelly – Try It Online&quot;
21 bytes, solves Shortest code to throw SIGILL (safe)
“A{gœỴ¹⁻ėe⁾÷ỤḞḂ4ḷ$»ŒV

Try it online!
This decompresses to the following Python 3 code (which is 22 bytes long, only one byte longer than the compressed version):
import os
os.kill(0,4)

Try it online!
The basic idea is to pick a task that's completely out of scope for Jelly; in this case, we're interacting with the OS, something that Jelly doesn't have builtins for (short of ŒV). So this probably isn't solvable in Jelly without shelling out to Python, and hopefully isn't solvable any more tersely than this.
(In case you're wondering how it works: 4 is the signal number for SIGILL, and os.kill appears to just copy its arguments to the kill(2) system call literally. 0 means &quot;send this signal to every process in my process group&quot;, which if the program is run from a shell, will raise a SIGILL in the Python/Jelly program and nothing else. On TIO, the program is being run from TIO's runner, so the SIGILL happens in the runner rather than in the program itself, but there's still a SIGILL being raised.)