Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Redacao de representacoes cautelares policiais e pedidos judiciais investigativos, com organizacao de fatos, indicios, fundamentos legais e pedidos delimitados. Use quando Codex precisar produzir peca para o Juizo envolvendo prisao preventiva, busca e apreensao, quebra de sigilo telefonico/telematico/bancario, medidas cautelares diversas, sequestro ou bloqueio de bens, sigilo processual, ou combinacao dessas medidas, a partir de autos, relatorios, PDFs, DOCX, TXT, planilhas e outros elementos da
.claude/skills/thomasmoreai-representacoes-cautelares/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-08 | ✗→✓ | ▲ Improved | 55% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 21% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 43% | 0% |
| case-20 | ✗→✓ | ▲ Improved | 42% | 0% |
| case-23 | ✗→✓ | ▲ Improved | 9% | 0% |
Redija pecas cautelares dirigidas ao Juizo, com foco em necessidade, adequacao, proporcionalidade e delimitacao objetiva dos pedidos. Use esta skill para pedir medida investigativa ou constritiva. Nao use como template de relatorio final de inquerito.
.docx, salvo se o usuario pedir expressamente apenas texto.references/modelo-prisao-busca-cautelares.md.references/modelo-quebra-sigilo.md.references/variantes.md.references/formatacao-docx.md.references/checklist-qualidade.md.references/pedidos-acessorios.md.Adote, em regra, esta sequencia:
Inclua capitulo autonomo de indiciamento apenas quando houver utilidade pratica para a peca, suporte probatorio suficiente e alinhamento com a estrategia do caso. Nao transforme toda representacao em mini-relatorio final.
Antes de redigir, confirmar pelo menos:
Se os autos forem volumosos, primeiro faca inventario de arquivos, linha do tempo e matriz simples de prova -> alvo -> medida -> pedido. So depois redija a representacao.
Entregue, conforme o caso:
Quando a representacao estiver suficientemente consolidada:
references/formatacao-docx.md;.docx por meio do script scripts/gerar_docx_representacao.py, salvo se houver ferramenta mais adequada ja disponivel no ambiente;| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | pass→pass | 40,436 | 27,416 | -32% | 1 | 1 | 0% | 3,450 | 5,760 | +67% | 0 | 0 | — |
case-02 | pass→pass | 16,896 | 21,109 | +25% | 1 | 1 | 0% | 2,931 | 5,226 | +78% | 0 | 0 | — |
case-03 | pass→pass | 20,548 | 24,722 | +20% | 1 | 1 | 0% | 3,891 | 5,653 | +45% | 0 | 0 | — |
case-04 | fail→fail | 51,875 | 31,748 | -39% | 1 | 1 | 0% | 5,224 | 7,312 | +40% | 0 | 0 | — |
case-05 | fail→fail | 24,338 | 27,670 | +14% | 1 | 1 | 0% | 4,566 | 5,943 | +30% | 0 | 0 | — |
case-06 | fail→fail | 28,948 | 28,021 | -3% | 1 | 1 | 0% | 4,977 | 7,390 | +48% | 0 | 0 | — |
case-07 | pass→pass | 18,129 | 26,511 | +46% | 1 | 1 | 0% | 3,363 | 5,509 | +64% | 0 | 0 | — |
case-08 | fail→pass | 16,155 | 18,438 | +14% | 1 | 1 | 0% | 2,629 | 4,065 | +55% | 0 | 0 | — |
case-09 | pass→pass | 19,631 | 21,747 | +11% | 1 | 1 | 0% | 3,295 | 5,292 | +61% | 0 | 0 | — |
case-10 | fail→fail | 15,043 | 20,496 | +36% | 1 | 1 | 0% | 2,771 | 4,727 | +71% | 0 | 0 | — |
case-11 | fail→pass | 18,595 | 17,811 | -4% | 1 | 1 | 0% | 3,572 | 4,318 | +21% | 0 | 0 | — |
case-12 | pass→pass | 12,062 | 10,022 | -17% | 1 | 1 | 0% | 2,100 | 2,902 | +38% | 0 | 0 | — |
case-13 | fail→fail | 25,155 | 24,060 | -4% | 1 | 1 | 0% | 3,824 | 5,289 | +38% | 0 | 0 | — |
case-14 | pass→pass | 16,106 | 17,561 | +9% | 1 | 1 | 0% | 2,972 | 4,245 | +43% | 0 | 0 | — |
case-15 | fail→fail | 75,155 | 21,072 | -72% | 1 | 1 | 0% | 6,189 | 4,831 | -22% | 0 | 0 | — |
case-16 | pass→pass | 14,353 | 17,023 | +19% | 1 | 1 | 0% | 2,576 | 4,126 | +60% | 0 | 0 | — |
case-17 | pass→pass | 13,959 | 17,891 | +28% | 1 | 1 | 0% | 2,327 | 4,179 | +80% | 0 | 0 | — |
case-18 | pass→pass | 12,701 | 17,885 | +41% | 1 | 1 | 0% | 2,028 | 3,294 | +62% | 0 | 0 | — |
case-19 | fail→pass | 12,695 | 12,128 | -4% | 1 | 1 | 0% | 2,152 | 3,072 | +43% | 0 | 0 | — |
case-20 | fail→pass | 16,076 | 15,192 | -5% | 1 | 1 | 0% | 2,592 | 3,684 | +42% | 0 | 0 | — |
case-21 | pass→pass | 13,097 | 12,511 | -4% | 1 | 1 | 0% | 2,156 | 3,265 | +51% | 0 | 0 | — |
case-22 | pass→pass | 24,295 | 24,139 | -1% | 1 | 1 | 0% | 3,501 | 4,499 | +29% | 0 | 0 | — |
case-23 | fail→pass | 22,256 | 17,095 | -23% | 1 | 1 | 0% | 3,675 | 4,001 | +9% | 0 | 0 | — |
case-24 | pass→pass | 19,045 | 16,864 | -11% | 1 | 1 | 0% | 2,964 | 3,740 | +26% | 0 | 0 | — |
case-25 | pass→pass | 13,807 | 11,540 | -16% | 1 | 1 | 0% | 2,015 | 3,222 | +60% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted. The headline lift of +20 percentage points is the difference between those two pass rates over the 25 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.