Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

site-launch

/site-launch

Prowadzi od gołego repozytorium do opublikowanego katalogu: pyta o rzeczy, które zna tylko użytkownik, i zleca resztę innym krokom.

Repozytorium
reposhowcase ↗
Licencja
MIT
Ostatnia zmiana repozytorium
01.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
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

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

Prowadzi od gołego repozytorium do opublikowanego katalogu: pyta o rzeczy, które zna tylko użytkownik, i zleca resztę innym krokom.

Wyzwalacze z opisu

set this uppublish my repositorieswalk me through itbuild me a catalogue sitelaunch the sitestart from scratch
Oryginalny opis (EN)

Drives Repo Showcase from a bare repository to a published catalogue, by asking the user what only they can answer and delegating everything else to the other skills. Use when the user says "set this up", "publish my repositories", "walk me through it", "build me a catalogue site", "launch the site", or "start from scratch". Do NOT use for a single change to an already-configured site — call the specific skill instead.

Jak działa

  1. When to use
  2. Inputs
  3. Procedure
  4. Where it must stop and hand control back
  5. Scripts used
  6. How to tell it worked
Sekcje z nagłówków SKILL.md, w oryginale · 103 linii, 698 słów
Podgląd SKILL.md
---
name: site-launch
description: Drives Repo Showcase from a bare repository to a published catalogue, by asking the user what only they can answer and delegating everything else to the other skills. Use when the user says "set this up", "publish my repositories", "walk me through it", "build me a catalogue site", "launch the site", or "start from scratch". Do NOT use for a single change to an already-configured site — call the specific skill instead.
---

# site-launch

The orchestrator. It owns no config key of its own: every decision belongs to
the skill that owns it, and this one only sequences them and stops where no
credential reaches.

## When to use

- A repository with no `site.config.json` yet, or one whose `brand.name` is
  still a placeholder.
- The user wants the whole journey rather than a change.
- A previous run was interrupted (a dashboard visit, a certificate wait).

Do not use it to answer "sort them by stars" on a site that already exists.
That is `catalogue-sort`, and going through the orchestrator would make the
user answer five questions to change one value.

## Inputs

Nothing. It reads the current state and asks for what is missing.

## Procedure

Run the phases in order. After each, print what is done, what is blocked, and
what is needed — never encouragement, and never "published" before a URL has
been fetched and the catalogue seen in it.

**Phase 0 — read state.** Load `site.config.json` if it exists. Check whether
the Pages project exists and whether the hostnames serve. Resume at the first
thing that is not done; do not restart a finished phase.

**Phase 1 — the four questions.** Ask them in this order and do not invent an
answer to any of them:

| Question | Default offered |
|---|---|
| Which GitHub account? | the one `gh api user` reports |
| What is the site called? | none — it must be told |
| Which repositories belong? | all public, non-fork |
| Publish to GitHub Pages, and add Cloudflare later? | yes, GitHub Pages with no domain |

The fourth question is last and pre-answered on purpose. GitHub Pages with no
custom domain is the only mode that needs neither a second account nor a domain,
so the journey can finish before it is asked. A user who ignores it still
publishes; a user who wants Cloudflare answers, and `site-deploy` takes them
through it as a follow-up.

Hand answers 1–3 to `site-identity`, `catalogue-curate` and `catalogue-sort`.
Question 4 becomes `deploy.targets`.

**Never ask for a token in the conversation.** When Cloudflare is enabled, say
which key is needed, tell the user to write it into `.env`, and run
`npm run secrets:check` to confirm it is there. It prints whether the key
exists, never the value.

**Phase 2 — build the catalogue.** `catalogue-curate` applies the rules, then
`npm run refresh` fetches. Report the three counts it returns: kept, empty,
unnoticed. If kept is zero, stop: the rules are wrong, not the network.

**Phase 3 — tag.** Ask whether the repositories carry `purpose-*`,
`platform-*` and `language-*` topics. If not, run `catalogue-tag`. If the user
declines, say plainly that the filter will be absent, and continue.

**Phase 4 — sort.** `catalogue-sort`, from whatever the user said, or leave
`sort.default`.

**Phase 5 — publish.** `site-deploy`.

**Phase 6 — verify.** Fetch every hostname, count the cards, compare against
the number the catalogue says. Report the URL only after that.

## Where it must stop and hand control back

1. Creating a Cloudflare API token in the dashboard, when the user chose to
   paste one.
2. Deleting a forwarding Page Rule. Page Rules are invisible to account-owned
   tokens, so no script here can see one, let alone remove it.
3. Waiting for a certificate. A freshly attached hostname fails until the
   certificate issues; that is minutes of doing nothing, and saying so is
   better than retrying.
4. Creating disposable repositories, when the smoke test is being run.
5. Anything destructive: `--overwrite-dns`, deleting a project, revoking a
   token. Ask explicitly. Never infer consent from an earlier yes.

## Scripts used

None directly. It calls `site-identity`, `catalogue-curate`, `catalogue-tag`,
`catalogue-sort` and `site-deploy`, and uses their acceptance steps rather
than restating them.

## How to tell it worked

```bash
npm run build && npx astro check          # clean
node scripts/check-config.mjs             # both loaders agree
curl -s https://<domain>/ | grep -c 'class="card"'   # matches the catalogue count
```

And the judgement that matters: the user answered five questions and typed no
code. If anything in the journey needed an edit to `src/`, the skill is not
finished, whatever the checks say.

Wersje

W bazie nie ma innych skilli o nazwie site-launch.

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

  • 100catalogue-curate
    Decyduje, które repozytoria trafią do katalogu, zapisuje reguły w site.config.json i podaje, co zostało wykluczone i dlaczego.
  • 100catalogue-sort
    Ustawia domyślne sortowanie katalogu, zapisując jeden klucz w site.config.json, na przykład według gwiazdek lub daty.
  • 90wp-site
    Prowadzi przez budowę strony WordPress od pustego folderu do działającej witryny i wskazuje, który etap jest następny.

Uwagi i zgłoszenia

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