What is google-sync-debug?

A diagnostic workflow for Google Calendar synchronisation in Compass. It traces failures across the browser, Compass backend, sync service, Google, and stored data to identify the first broken boundary.

Use it when events are stale, imports or watches fail, reconnect is needed, sync jobs stop, or browser updates do not reflect backend changes.

It replaces guesses across multiple systems with evidence from the correct layer. It also prevents credentials, tokens, and private configuration from appearing in logs or reports.

How KeepSoftwareSimple/compass-calendar configures Claude Code and Cod

Reuse

Borrowing it

Nothing to install: this file belongs to KeepSoftwareSimple/compass-calendar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/KeepSoftwareSimple/compass-calendar/main/.agents/skills/google-sync-debug/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/KeepSoftwareSimple/compass-calendar

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/keepsoftwaresimple/compass-calendar/google-sync-debug/github.svg)](https://agentmods.dev/skills/keepsoftwaresimple/compass-calendar/google-sync-debug)

Your own site

<a href="https://agentmods.dev/skills/keepsoftwaresimple/compass-calendar/google-sync-debug"><img src="https://agentmods.dev/badge/skills/keepsoftwaresimple/compass-calendar/google-sync-debug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/keepsoftwaresimple/compass-calendar/google-sync-debug"><img src="https://agentmods.dev/badge/skills/keepsoftwaresimple/compass-calendar/google-sync-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 989 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00066	$0.00989
Opus 5.5	$0.00026	$0.00396
Sonnet 5.5	$0.00013	$0.00198
Haiku 4.5	$0.00007	$0.00099

Measured yesterday against content hash ebbc26521dae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

google-sync-debug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/google-sync-debug/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When

Google events are stale, watches fail, reconnect is required, or SSE is quiet.

Steps

Classify symptom → local prerequisites → trace the boundary → narrowest test.

Output

The failing layer (browser, backend, sync, provider, storage) plus evidence.

Pass

A named boundary and a command or log that shows it.

Anti-patterns

Do not guess across layers. See anti-patterns.md.

Escalate

OAuth grant, production data repair, or missing Google client secrets.

Debug Google sync

Find the failing boundary before changing code. Read:

docs/features/google-sync-and-sse-flow.md
docs/development/local-development.md
docs/development/testing-playbook.md#testing-realtime-and-sync-changes

Never print credentials, refresh tokens, internal auth tokens, notification tokens, or the contents of compass.yaml.

1. Classify the symptom

Identify the first observable failure:

OAuth cannot start or complete
provider connection is missing, revoked, or requires reconnect
initial import or repair does not finish
Compass changes do not reach Google
Google changes do not reach Compass
backend changes arrive but the browser stays stale
sync jobs remain pending, leased, or retrying
health/readiness reports attention

Record user state, environment, effective service URLs, calendar/provider, and the last successful step without collecting sensitive payloads.

2. Verify local prerequisites

Follow docs/development/local-development.md for incomplete setup.

Backend, sync service, MongoDB, and web must use the current worktree's effective ports.
Google OAuth credentials and redirect URIs must match the selected port.
Browser API and SSE traffic can remain local.
Google watch notifications require a public HTTPS sync.callbackBaseUrl (proxied as /sync/*).
A local HTTP backend can support OAuth and initial import but not inbound Google webhook delivery.

Check backend and sync liveness/readiness before debugging domain logic.

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 135 lines · 66 tokens per session scan A ebbc26521dae

Subscribe to this mod's changes

google-sync-debug is a skill published in the GitHub repository KeepSoftwareSimple/compass-calendar (226 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 989 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-07.

Backend and APIs Debugging React TypeScript calendar google google-calendar nodejs

google-sync-debug next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
google-sync-debugKeepSoftwareSimple/compass-calendar	Skill	226	today	MIT	A	66	Claude Code, Codex
analyzing-experiment-query-performancePostHog/posthog	Skill	41k	today	none	A	141	Claude Code, Codex
webiny-api-cms-content-modelswebiny/webiny-js	Skill	8.0k	yesterday	none	A	313	Claude Code, Codex
triaging-warehouse-sync-ticketsPostHog/posthog	Skill	41k	today	none	B	213	Claude Code, Codex
webiny-form-modelwebiny/webiny-js	Skill	8.0k	yesterday	none	A	93	Claude Code, Codex
webiny-api-architectwebiny/webiny-js	Skill	8.0k	yesterday	none	A	93	Claude Code, Codex
webiny-v5-to-v6-migrationwebiny/webiny-js	Skill	8.0k	yesterday	none	A	75	Claude Code, Codex

compass-calendar: Skill for Claude Code