Przejdź do treści
Biblioteka skilli
Finanse i księgowość · Przegląd i audyt

data-room

/data-room

Buduje i sprawdza data room do due diligence: standardowe kategorie, indeks, luki i listę uprawnień, bez zmiany ustawień udostępniania.

Repozytorium
shotos ↗
Licencja
MIT
Ostatnia zmiana repozytorium
10.11.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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
3
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 10.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

Buduje i sprawdza data room do due diligence: standardowe kategorie, indeks, luki i listę uprawnień, bez zmiany ustawień udostępniania.

Oryginalny opis (EN)

Builds and audits a due-diligence data room: standard categories, index, gaps, and who can see what. Use when preparing for a funding round, sale or audit, or asked what is in the data room. Changes no sharing settings.

Jak działa

  1. Context and handoff
  2. Start here
  3. When not to use this
  4. Standard categories
  5. Steps
  6. Output
  7. Checks
Sekcje z nagłówków SKILL.md, w oryginale · 59 linii, 669 słów
Podgląd SKILL.md
---
name: data-room
description: "Builds and audits a due-diligence data room: standard categories, index, gaps, and who can see what. Use when preparing for a funding round, sale or audit, or asked what is in the data room. Changes no sharing settings."
---

# Data room

Make it easy for a reviewer to find what they need, and make sure nobody sees what they should not.

Stage: Own. Rules served: 1 (stop at the boundaries), 4 (claim only what you can show) and 3 (read back the real result).

## Context and handoff

Read the diligence request, approved source locations, intended recipients and document owners. Check date, version and sensitivity before listing each item.

Use `public-exposure-check` before external access. Maintain one index with access and missing items.

## Start here

**Minimum to start:** the purpose (round, sale, audit), the reader, the source folder and the owner's list of who may see what. **First output:** the index, then the gaps, access and exposure findings, in the order of the template. **Uncertain:** files you could not read, or settings you could not see, are listed as unchecked, not as clear. **Handoff:** give the owner a short list of changes only they can authorise, each with the evidence, the suggested change and the risk of leaving it.

## When not to use this

Skip it for a single document request. Do not use it to decide what the company should disclose; that is for the owner and legal adviser. Do not move, copy, delete or re-share files without the owner's yes.

## Standard categories

1. Company: incorporation, constitution or articles, structure chart, registers.
2. People: team list, contracts, option or equity records, policies, advisers.
3. Finance: accounts, management accounts, budget, tax filings, bank, debt, grants received.
4. Legal: material contracts, disputes, insurance, licences, compliance.
5. Intellectual property: ownership, assignments, trademarks, licences in and out, open-source use.
6. Product: description, roadmap, architecture summary, security.
7. Customers: customer list (redacted where needed), contracts, retention, feedback.
8. Commercial: market, pricing, pipeline, partners.
9. Data protection: register of processing, privacy notices, data processing agreements, breaches log, safeguarding where relevant.
10. Governance: board papers, minutes, advisory board.

Adapt to the situation; say what was added or dropped and why.

## Steps

1. **Define the purpose and the reader.** Round, sale, audit or grant. Who will see it, and what do they usually ask for. Ask the owner for a list of who is allowed in.
2. **Inventory.** Read the folder or index the owner points to. For each file: path, category, date, owner, version and sensitivity (public, restricted, confidential, personal data). Do not open files beyond what the task needs; for personal data, record that it exists, not its content.
3. **Build the index.** One line per file in category order, with a one-line description, date and status (current, draft, superseded). Mark duplicates and out-of-date versions.
4. **List what is missing.** Compare with the category list and the reader's likely requests. For each gap: what, why it matters, who holds it and whether it exists at all. Do not fabricate documents.
5. **Record access.** For each category or file: the people or groups allowed, from the owner's list. Show the intended access against the actual sharing settings where you can read them.
6. **Run the exposure check.** Flag anything confidential or personal that is visible to more people than intended: link sharing on, wide groups, public links, external editors, files containing personal data or credentials, and counterparties' confidential terms. Do not change a setting. Report each with the evidence and the suggested change.
7. **Report to the owner** with the index, gaps, access table and exposures. The owner or an authorised person makes the changes.
8. **Stop.** Do not share, move, rename or delete files, or invite anyone.

## Output

Use [template.md](template.md): purpose, index, gaps, access table and exposure findings. Save outside the room itself, for example `.work/data-room/audit.md`.

## Checks

- Every file in the index has a category, date and sensitivity.
- Gaps are listed and none filled with an invented document.
- Access is compared with the owner's intended list.
- Every exposure finding has evidence and a suggested change; no change was made.
- Personal data and credentials were recorded as present, not copied into the report.
Pliki w paczce (3)
  • README.md 3 KB
  • SKILL.md 4 KB
  • template.md 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · SHOTClubhouse/shotos100MIT
Maudeunfledged834/startup-founder-skills100MIT
andreworia/claude-finance-skills100MIT
LLM-preneur/skills90MIT
LLM-preneur/skills90MIT
galyarderlabs/galyarder-framework90MIT
galyarderlabs/galyarder-framework90MIT

Migawka bazy z 13.11.2026 · wersja paczki 497bbbd1c481 (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

  • 90data-room-builder
    Przygotowuje materiały do due diligence inwestorów: buduje uporządkowany, etapowy data room i listę kontrolną diligence, który przyspiesza proces i buduje zaufanie.
  • 100data-room-diligence
    Przegląda cały data room due diligence: sprzeczności między dokumentami, sygnały ostrzegawcze, brakujące pliki i listę wymaganych dokumentów z cytowanymi źródłami.
  • 100data-room-prep-checklist
    Generuje listę kontrolną data roomu dla danego etapu rundy, strukturę folderów i listę braków dla inwestora, przy przygotowaniu do due diligence.
  • 100vc-diligence
    Prowadzi due diligence techniczne i finansowe z wirtualnej data room przed zakupem udziałów lub rundą.
  • 100prepare-data-room
    Zbiera dokumenty do data roomu startupu na potrzeby due diligence inwestorów, z listą według sekcji i uwagami, co dołączyć, a co zanonimizować.
  • 95due-diligence-prep
    Przygotowuje firmę do due diligence inwestora: data room, modele finansowe, dokumenty prawne, cap table i odpowiedzi na pytania.

Uwagi i zgłoszenia

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