upload-watch-changes SKILL.md skillA
upload-watch-changes from atanasster/electionsbg is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atanasster/electionsbg/upload-watch-changes@git:20261012.1e27653Pins git:20261012.1e27653 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atanasster/electionsbg
- Path
.claude/skills/upload-watch-changes/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261012.1e27653, committed Oct 12, 2026
- First version recorded
- Aug 28, 2026
- Size
- 19,535 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Publish what /process-watch-report ingested — push the touched data/ subtrees to the GCS bucket and run the ordered db:load:*:cloud commands against Cloud SQL, timing every step into an append-only trace. Reads state/upload/pending.json (the manifest the ingest run wrote) so nothing is guessed. Use when the user says "upload the changes", "publish to cloud", "sync the bucket", "push the data live", "качи промените", or when /process-watch-report invokes it as the last step of a run that hit no…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Upload watch changes (publish skill) `/process-watch-report` is the INGEST half: it refreshes `data/`, reloads LOCAL Postgres and commits. Nothing it does reaches a reader. This skill is the PUBLISH half — the bucket the SPA fetches (`gs://data-electionsbg-com`) and the Cloud SQL instance `/api/db` serves. **Both targets are PRODUCTION.** That is why the publish is a separate skill with its own trace, its own gate and its own commit, rather than commands inlined into the orchestrator. It is reached two ways: the operator invokes it directly, or `/process-watch-report` invokes it as its step 14 after a run with no major issue — in which case the operator's yes to that run's plan (which names the publish) is the authorisation, and step 0 does not re-ask. ## Inputs - **`state/upload/pending.json`** — the manifest. The ingest run wrote it because it is the only thing that knows what moved: which `data/` subtrees it touched, which ordered `:cloud` loaders the changed datasets need, which skills ran, and the commit sha. - `state/perf/upload-watch-changes.jsonl` — the append-only publish trace this skill extends. …
Read the whole file at its exact version.
How to install
mdr add atanasster/electionsbg/upload-watch-changes@sha256:a30f64cbdfb04803The line at the top of this page pins the label git:20261012.1e27653, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ukzqqahdz3cfrk5l)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 28, 2026 and Oct 12, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.1e27653 latest | 2026-10-12 | 1e27653 | 19,535 B | A | view · diff |
| git:20260911.ee0592d | 2026-09-11 | ee0592d | 18,919 B | A | view · diff |
| git:20260828.d9b6d0b | 2026-08-28 | d9b6d0b | 18,364 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (19535 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
atanasster/electionsbg · 15 stars · license a license file GitHub does not identify · pushed 2026-10-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ukzqqahdz3cfrk5l GET https://markdownregistry.com/api/v1/resolve?ref=atanasster/electionsbg/upload-watch-changes GET https://markdownregistry.com/api/v1/blob/a30f64cbdfb048032ddd0097af00aa23736d0619d961c9caa657ca69e9b73dcb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.