Przejdź do treści
Biblioteka skilli
Prawo i compliance · Pisanie

case-report

/case-report

Pisze raport z dochodzenia w sprawie śledzenia przepływów kryptowalut: podsumowanie, schemat środków, tabelę skoków i źródła, z eksportem do PDF.

Repozytorium
hopchase ↗
Licencja
MIT
Ostatnia zmiana repozytorium
07.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pisze raport z dochodzenia w sprawie śledzenia przepływów kryptowalut: podsumowanie, schemat środków, tabelę skoków i źródła, z eksportem do PDF.

Wyzwalacze z opisu

write the case reportwrite up the investigationcase reportHopChase reportinvestigation report
Oryginalny opis (EN)

Writes a HopChase case report for a crypto tracing investigation (incident summary, compromise analysis, fund-flow diagram, hop table with confidence marks, operator profile, action pack for issuers/bridges/police, reproducibility, sources) as an editable doc with optional PDF export. Use when the user asks to "write the case report", "write up the investigation", "case report", "HopChase report", "investigation report", or after trace-funds finishes.

Jak działa

  1. Where it goes
  2. Lead paragraph
  3. Sections (fixed order; drop a section only when empty)
  4. Style
  5. After publishing
Sekcje z nagłówków SKILL.md, w oryginale · 35 linii, 613 słów
Podgląd SKILL.md
---
name: case-report
description: Writes a HopChase case report for a crypto tracing investigation (incident summary, compromise analysis, fund-flow diagram, hop table with confidence marks, operator profile, action pack for issuers/bridges/police, reproducibility, sources) as an editable doc with optional PDF export. Use when the user asks to "write the case report", "write up the investigation", "case report", "HopChase report", "investigation report", or after trace-funds finishes.
---

# HopChase case report

The case report is written for lawyers, victim-support volunteers, exchange/issuer compliance and police — readers who will act on it, not re-derive it. Every claim carries a confidence mark and a way to reproduce it.

## Where it goes

Create it as a Claude Doc (Docs artifact type) titled `HopChase — Incident trace <first 4>…<last 4 of seed hash>` (translate the title and all headings into the user's language). Land the skeleton first (title, byline, lead, one pending block per section), then fill one section per call so the reader watches it build. Export to PDF (A4) with the docs `export` tool when asked; check one page renders before sending.

## Lead paragraph

One paragraph, the answer first: amount + asset, date, **whether the stolen funds have moved**, the endpoint, and the freeze window ("90,540.81 USDC … have not moved as of this report: they sit at … and can be frozen by Circle. The operator's route is Solana → Bridgers → USDT (TRON), where 197,351 USDT has accumulated.").

## Sections (fixed order; drop a section only when empty)

1. **Incident summary** — table: network/asset, amount, time UTC + slot/block, seed tx link, victim wallet, recipient owner **and token account**, status of stolen funds *as of* check time, incident type, scheme endpoint. Close with the freeze-window sentence and last operator activity.
2. **Seed transaction and compromise analysis** — what the tx is, what is excluded (poisoning, approve) with the evidence, client-fingerprint table (tx / who / CU limit / CU price), confidence of the compromise call, **urgent advice to the victim** (rotate seed, move remainder, ignore memo phishing).
3. **Fund-flow map** — one diagram: victims on the left → collector (accent) → bridges → EVM twin → endpoint (critical colour); edge labels = amounts; one sentence of reading under it. Draw with the docs diagram widget (`guide topic.diagram`).
4. **Hop table** — `# | date UTC | chain | from | to | amount (in → out) | channel / orderId | status | confidence`. Hop 0 = the theft. Include pre-theft hops of the same operator when they show the route. List bridge payout wallets under the table.
5. **Operator profile** — table of operator addresses (chain, role, marks) + table of probable other victims (date, address, amount, "our case" marked) + total scheme damage estimate.
6. **Action pack** — checklist ordered by urgency, each item with the exact address/token-account/orderId to quote. Use `references/action-pack.md` for contacts and wording. Always include: issuer freeze(s), police report (and why it is needed), bridge/aggregator data requests + blocklist ask, wallet-app abuse report if a channel is known, monitoring, victim hygiene.
7. **Reproducibility** — table `fact → how to verify` with exact endpoints and request bodies (Solana RPC methods, Bridgers API body, Blockscout/TronGrid URLs); state when each check was run; list limitations (amount/time-matched links, hypothesis lists).
8. **Sources** — explorer links for every hash and address, bridge docs, APIs queried with dates.

## Style

- Numbers with units and thousands separators; UTC everywhere; addresses in backticks, shortened `A9a6…KmdB` after the first full mention in a table.
- Confidence marks ⭐/⭐⭐/⭐⭐⭐ in the hop table and on the compromise call; "hypothesis" spelled out for ⭐ items.
- No speculation about identity of the operator; no victim personal data beyond addresses; no API keys or internal paths.
- Sentences short; the reader is skimming between phone calls.

## After publishing

Say in one line what the doc is; offer PDF export and an hourly monitor (`scripts/recheck.py` with a `case.json`) as the next step. If the user asks for letters (police statement, issuer freeze request, bridge data request), draft them from `references/action-pack.md` templates as separate docs.
Pliki w paczce (2)
  • SKILL.md 4 KB
  • references/action-pack.md 4 KB

Wersje

W bazie nie ma innych skilli o nazwie case-report.

Migawka bazy z 13.11.2026 · wersja paczki eed0fc0ed93d (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100incident-report-writing
    Pisze raporty z incydentów dla różnych odbiorców: podsumowanie dla zarządu, raport techniczny i szkic zawiadomienia dla regulatora lub klienta.
  • 100prompt-pack-workplace-investigation-report
    Pomaga przygotować formalny raport z wewnętrznego postępowania wyjaśniającego w miejscu pracy: zarzuty, metodyka, przesłuchania świadków, dowody, ustalenia faktyczne, ocena wiarygodności, naruszenia polityk i rekomendacje.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.