Przejdź do treści
Biblioteka skilli
Edukacja · Przegląd i audyt

sync

/sync

Porównuje tracker certyfikacji GCP z aktualną ścieżką nauki Google i przewodnikiem egzaminu, pokazuje różnice i stosuje je po potwierdzeniu.

Licencja
MIT
Ostatnia zmiana repozytorium
11.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 11.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

Porównuje tracker certyfikacji GCP z aktualną ścieżką nauki Google i przewodnikiem egzaminu, pokazuje różnice i stosuje je po potwierdzeniu.

Wyzwalacze z opisu

sync\check for updates to the course or exam guide\the course changed\a module is missing\
Oryginalny opis (EN)

Checks the GCP Certification Coach tracker against the live Google Skills learning path and the official Google Cloud exam guide, shows a diff (added, removed and renamed activities, modules and concepts, exam-guide sections, weights and version), and applies it only after the learner confirms, taking a snapshot first, archiving removed items instead of deleting them and keeping all progress on renamed items. Use when the learner says \"sync\", \"check for updates to the course or exam guide\", \"the course changed\", \"a module is missing\", or when the tracker shows it was not synced for 30

Jak działa

  1. When to use
  2. Preconditions
  3. Workflow
  4. Output format
  5. Tracker access
  6. References
  7. Feedback
  8. Failure handling
Sekcje z nagłówków SKILL.md, w oryginale · 61 linii, 869 słów
Podgląd SKILL.md
---
name: sync
description: "Checks the GCP Certification Coach tracker against the live Google Skills learning path and the official Google Cloud exam guide, shows a diff (added, removed and renamed activities, modules and concepts, exam-guide sections, weights and version), and applies it only after the learner confirms, taking a snapshot first, archiving removed items instead of deleting them and keeping all progress on renamed items. Use when the learner says \"sync\", \"check for updates to the course or exam guide\", \"the course changed\", \"a module is missing\", or when the tracker shows it was not synced for 30 days. Not for marking modules completed (use progress), refreshing the tracker page code (use rebuild) or starting over (use reset)."
---

# Sync

Keep the tree current without losing progress. Destructive changes follow plan → show → confirm → snapshot → apply.

## When to use

- The path or exam guide may have changed, the page shows the stale-sync notice, or a module the learner sees is missing.
- Not for completion marks (progress), page code (rebuild) or resetting levels (reset).

## Preconditions

- A tracker (see Tracker access) with a working data tool; sync never runs in read-only mode except to show the diff.
- Web fetch for the exam guide; the built-in browser for Google Skills pages (they render with JavaScript). Without a browser, ask the learner to paste the current outline or to open the chat in the Claude desktop app.

## Workflow

```
- [ ] 1. Read the tracker tree and settings
- [ ] 2. Read the live learning path and exam guide
- [ ] 3. Build the diff
- [ ] 4. Show the diff and ask for confirmation
- [ ] 5. Snapshot the documents that will change
- [ ] 6. Apply in batches
- [ ] 7. Update lastSyncAt and report
```

1. **Read** `meta/settings`, `activities`, `modules`, `concepts` (archived included).
2. **Live sources.** Exam guide: `settings.examGuide.url` — section names and weights, objective ids and titles only. Path: `settings.path.url` and each activity page — activity titles, stated hours, optional marks, module titles and item titles (as in the generated-pack rules: drop quizzes, lab intros and reviews; skill-badge labs are modules). If the learner pasted an outline, use it instead and say so.
3. **Diff** with [references/diff-and-apply.md](references/diff-and-apply.md): match by id where the source gives one, else by order and title similarity; classify every difference as added, removed, renamed, moved, changed hours or optional flag, or section mapping change; and compare exam-guide version, sections and weights.
4. **Show** the diff grouped by activity, with counts and the effect on progress for each item ("renamed: keeps level and completion", "removed: archived, hidden from quizzes, data kept", "added: level 0, not completed"). For new modules, propose `sections`, `weight` and `examRelevant`. Ask for an explicit yes. Partial approval ("only the renames") is fine.
5. **Snapshot** before any change, following [references/snapshots.md](references/snapshots.md): id `sync-<YYYYMMDD-HHMM>`, full copies of every document that will be updated or archived, chunked, read back and verified (`status: "complete"`). No apply before the snapshot is complete.
6. **Apply** in batches of at most 50 writes: added items `set` with level 0 and not completed; renamed or moved items `update` title, order and fields while keeping id, level, answers, completion; removed items `update archived: true` (never delete); exam-guide changes `update meta/settings.examGuide`. New concepts get ids that do not collide with existing ones (next free `-k<N>`; new modules next free `-m<N>`).
7. **Finish:** `update meta/settings` with `lastSyncAt` (now) and `updatedAt`. Report what changed and what it means (for example "readiness may drop because a new core module was added"). With no differences, only update `lastSyncAt` and say the tracker is current.

## Output format

Diff tables per activity: change, item, before → after, effect on progress. A one-line summary with counts. Prose in the learner's language; titles as they appear on the source pages.

## Tracker access

- **Locate:** a line `GCP Cert Coach tracker: <URL> (certification: <id>)` in the Project instructions or this conversation; otherwise the learner's artifact list, titles ending in "Cert Coach" (one: use it; several: ask which certification; none: offer `/gcp-cert-coach:init`). Never create a tracker here.
- **Version:** Plugin version: 0.3.0. On the `meta/settings` read, compare versions. `schemaVersion` below 1: stop and offer `/gcp-cert-coach:rebuild` first; above 1: ask the learner to update the plugin. `templateVersion` (missing means `pluginVersion`) older than the plugin version: say once per session, in one line, "A new tracker page is available (x → y). Say 'rebuild' to update it."; never rebuild on your own. `latestPluginVersion` older than the plugin version: include it in the settings write this skill makes anyway; never write only for this.
- **Writes:** batches as above. Pass the version you read for each document you update; on a version conflict re-read once and redo; if it fails again, stop, report what was applied and point to the snapshot.
- **No data tool or database unavailable:** show the diff and the apply plan in order (snapshot of the affected documents first, then the changes, archived not deleted), say nothing was applied, and say that confirmation will be asked in a session that can write.

## References

- [references/diff-and-apply.md](references/diff-and-apply.md): matching, change types, example diff
- [references/snapshots.md](references/snapshots.md): snapshot format and restore

## Feedback

When the learner reports that the path or pack is wrong, write `feedback/<timestamp>-<4 random letters>` with `{ts, source: "learner", kind: "bug" | "improvement", text, logId: null, pluginVersion: settings.pluginVersion, status: "new"}` (neutral text, no personal data) and tell the learner it was recorded.

## Failure handling

- Live page unreadable or signed out: ask the learner to sign in or paste the outline; never treat an unreadable page as "everything removed".
- More than a third of the tree would be removed: stop and ask the learner to confirm the source is correct before showing an apply option.
- Apply fails midway: report applied and pending items; the snapshot holds the previous state.
Pliki w paczce (3)
  • SKILL.md 6 KB
  • references/diff-and-apply.md 2 KB
  • references/snapshots.md 3 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · olehsov/gcp-certification-coach100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
makenotion/notion-cookbook100MIT
wookiya1364/scv-claude-code100MIT
biliboss/skills100MIT
lucastamoios/skills100MIT
enzo-thuilliez/my-starter-kit100MIT

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

  • 100progress
    Aktualizuje postęp nauki w trackerze GCP Certification Coach, oznacza ukończone moduły po potwierdzeniu i raportuje gotowość do egzaminu.
  • 100rebuild
    Aktualizuje stronę trackera certyfikacji GCP do bieżącej wersji wtyczki, bez zmiany danych ucznia.
  • 100exam-prep-app
    Buduje offline aplikację do nauki certyfikatu Microsoft z lekcjami, bankiem pytań, symulacją egzaminu i powtórkami rozłożonymi w czasie.
  • 100study-plan-builder
    Układa plan nauki do egzaminu: ramy wiedzy z sylabusa, tygodniowy harmonogram powtórek, testy kontrolne i tracker postępu.
  • 100mock-exam
    Przeprowadza pełnowymiarowy, mierzony czasowo egzamin próbny do certyfikacji Claude Certified Architect (CCA-F), w warunkach zbliżonych do prawdziwego egzaminu.
  • 86exam-help
    Pokazuje na jednym ekranie, jak działa coach egzaminacyjny: tryby nauki, typy zadań, pliki i zasady źródeł.

Uwagi i zgłoszenia

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