Skip to content
Skills Library
Education · Tool integration

progress

/progress

Updates and reports study progress in the GCP Certification Coach tracker. Marks courses, skill badges and modules completed from what the learner types or from their Google Skills or Coursera progress page in the built-in browser (always confirmed before writing), pauses and resumes the plan, changes mode, difficulty, weekly hours or exam date, and reports status, readiness per exam-guide section, the review queue and the study plan with an estimated finish date. Use when the learner says \"I finished module 4 of course 6\", \"mark course 2 done\", \"check my progress on the site\", \"status\

Licence
MIT
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Updates and reports study progress in the GCP Certification Coach tracker. Marks courses, skill badges and modules completed from what the learner types or from their Google Skills or Coursera progress page in the built-in browser (always confirmed before writing), pauses and resumes the plan, changes mode, difficulty, weekly hours or exam date, and reports status, readiness per exam-guide section, the review queue and the study plan with an estimated finish date. Use when the learner says \"I finished module 4 of course 6\", \"mark course 2 done\", \"check my progress on the site\", \"status\

Triggers from the description

I finished module 4 of course 6\mark course 2 done\check my progress on the site\
Original author description

Updates and reports study progress in the GCP Certification Coach tracker. Marks courses, skill badges and modules completed from what the learner types or from their Google Skills or Coursera progress page in the built-in browser (always confirmed before writing), pauses and resumes the plan, changes mode, difficulty, weekly hours or exam date, and reports status, readiness per exam-guide section, the review queue and the study plan with an estimated finish date. Use when the learner says \"I finished module 4 of course 6\", \"mark course 2 done\", \"check my progress on the site\", \"status\

How it works

  1. When to use
  2. Preconditions
  3. Workflow
  4. Output format
  5. Tracker access
  6. References
  7. Feedback
  8. Failure handling
Original SKILL.md headings · 66 lines, 966 words
SKILL.md preview
---
name: progress
description: "Updates and reports study progress in the GCP Certification Coach tracker. Marks courses, skill badges and modules completed from what the learner types or from their Google Skills or Coursera progress page in the built-in browser (always confirmed before writing), pauses and resumes the plan, changes mode, difficulty, weekly hours or exam date, and reports status, readiness per exam-guide section, the review queue and the study plan with an estimated finish date. Use when the learner says \"I finished module 4 of course 6\", \"mark course 2 done\", \"check my progress on the site\", \"status\", \"how am I doing\", \"what's my plan\", \"when will I finish\", \"pause my plan\", \"I'm back\", \"switch to full exam mode\" or \"make it harder\". Not for setting up a tracker (use init), practice questions (use quiz) or updating the tree from the live path (use sync)."
---

# Progress

Keep the tracker in step with what the learner actually studied, and tell them where they stand.

## When to use

- Marking completion, browser progress checks, pause and resume, settings changes, status and plan questions.
- Not for setup (init), the tree structure itself (sync) or practice (quiz, mock, challenge).

## Preconditions

- A tracker (see Tracker access). Without one, offer `/gcp-cert-coach:init`.
- The built-in browser only for site checks (Claude desktop app).

## Workflow

Pick the branch that matches the request; several can run in one turn.

```
- [ ] 1. Locate the tracker; read settings, then only what the branch needs
- [ ] 2. Run the branch: mark | browser check | pause/resume | settings | status and plan
- [ ] 3. Confirm before any write; write one batch
- [ ] 4. Report and suggest the next step
```

**Mark completion.** Course platforms number modules differently, so a number is never trusted on its own. Resolve what the learner names to ids: "course N" is the N-th activity in path order (`activities.order`), "module M" is the M-th module of that activity, skill badges count as activities. Then **always ask before writing**: "Do you mean course N <course title>, module(s) <module titles>?" and write nothing until a yes. On a "no", ask the learner to type the course and module names, match them by title, confirm the match again, then write. When the learner gives titles instead of numbers, match by title and write after one short confirmation. Then write one batch: `update modules/<id>` with `completed: true`, `completedAt` (today unless the learner gives a date). Marking a whole activity marks all its modules. Un-marking works the same way on request. Then suggest a quiz on the new module (or a re-test if a pre-test was taken on it).

**Browser check.** Follow [references/browser-progress-check.md](references/browser-progress-check.md): no browser → offer the desktop app or typed progress; sign-in page → ask the learner to sign in in the browser pane, then retry; unexpected page → show what was read and ask. Always show the proposed marks and wait for a yes before writing.

**Pause and resume.** Pause: `update meta/settings` with `paused: {since: today}`; explain that decay and the plan stop counting while paused and that any learning command (quiz, learn, challenge, mock) resumes it, with a warm-up if the break lasts more than `settings.scoring.session.warmupAfterPauseDays` days. Resume ("I'm back"): `paused: null`, `pausedDaysTotal` += paused days, append `{since, until: today}` to `pauseHistory`.

**Settings.** Mode (`course` or `full`), difficulty (`standard` or `hard`), `paceHoursPerWeek`, `examDate`, `language` (then also translate `settings.ui`, keeping keys and `{placeholders}`). State the effect in one line before writing (for example "Hard raises the ready threshold to level 85 and needs no open misconceptions"). One `update meta/settings` with `updatedAt`. The page's mode and difficulty toggles do the same.

**Status and plan.** Compute with [references/status-and-plan.md](references/status-and-plan.md) (the plan estimate is the single formula in [references/plan-estimate.md](references/plan-estimate.md), the same one the page and `init` use): readiness (labeled "Course readiness" in Course mode, "Exam readiness" in Full exam mode), section scores with official weights, module statuses, review queue (top 7), open misconceptions, calibration, last mock verdict, plan (remaining hours, pace, estimated finish date, or required pace and on-track status when an exam date is set). No writes.

## Output format

- Confirmation prompts list titles, not ids.
- Status: a short headline (readiness and label), a section table, the next three actions from the review queue, the plan line, and a pointer to the tracker page for detail.
- Prose in the learner's language; product names in English.

## 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.
- **Reads:** read `meta/settings` first. Marking and pause or settings changes need only `activities` and `modules`. Status and plan need `modules`, `concepts`, open `misconceptions` and the last 50 `log` entries; never list the whole `log`.
- **Writes:** one batch per confirmed change. Pass the version you read for each document you update; on a version conflict re-read once and redo; if it fails again, stop and report.
- **No data tool or database unavailable:** if the conversation contains a tracker export, use it read-only for status and plan. For changes, say that nothing was saved and show the batch you would have written as a JSON code block.

## References

- [references/status-and-plan.md](references/status-and-plan.md): readiness, statuses, queue, calibration
- [references/plan-estimate.md](references/plan-estimate.md): the plan estimate formula
- [references/browser-progress-check.md](references/browser-progress-check.md): reading Google Skills or Coursera

## Feedback

When the learner reports a problem or suggests a change, write `feedback/<timestamp>-<4 random letters>` with `{ts, source: "learner", kind: "bug" | "improvement" | "wrong_question", text, logId: null, pluginVersion: settings.pluginVersion, status: "new"}`, a neutral `text` without personal data, and tell the learner it was recorded.

## Failure handling

- Ambiguous course or module number: list the candidates with titles and ask. A learner's "no" to the resolved titles is never retried with a guess; ask for the names.
- A module title not in the tree: suggest `/gcp-cert-coach:sync` (the path may have changed).
- Browser check fails midway: keep the marks already confirmed, report what was not read, offer typed input.
Files in this package (4)
  • SKILL.md 7 KB
  • references/browser-progress-check.md 2 KB
  • references/plan-estimate.md 2 KB
  • references/status-and-plan.md 3 KB

Versions

RepositoryScoreLicence
This page · olehsov/gcp-certification-coach100MIT
Embassy-of-the-Free-Mind/sourcelibrary-v2100AGPL-3.0
builderio/agent-native100MIT
M-reza-kd/lead-flow-plugin100MIT
yarikleto/claude-teacher-plugin100MIT
avsm/ocaml-claude-marketplace100ISC
maludb/learn-claude100MIT
matteocervelli/llms100MIT
caidanw/skills86MIT

Database snapshot: 13.11.2026 · package version 0e6b761a75e3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sync
    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…
  • 100mock
    Use whenever a Google Cloud certification learner wants a mock exam, a full-length practice exam or an exam simulation (\"full mock exam\", \"practice exam like the real one\"), asks whether they are ready to book the exam, answers a question of a mock in progress (\"question 12…
  • 100study-plan-builder
    Builds an exam or learning plan from the goal, date, materials, weekly hours and current level: a knowledge framework of the syllabus, a week-by-week revision plan with daily tasks, spaced review slots, mock-test checkpoints and a progress tracker. Use when a student or learner…
  • 100exam-study-coach
    Turn a syllabus, notes, PDFs and past question papers into an evidence-ranked study plan, then teach, quiz, mark answers and track progress across sessions with spaced repetition and mock tests. Also gives important-topic lists, simple summaries of the material and study…
  • 90exam-coach
    Coaches a learner preparing for an Anthropic Claude certification exam (CCAO-F, CCDV-F, CCAR-F, CCAR-P) with the Cred Farmer tools. Use when someone asks to study, practise, drill, review flashcards, plan their weeks or check whether they are ready for a Claude certification exam.
  • 100ai901-study-planner
    Generates a personalized AI-901 study plan based on the learner's self-assessed confidence across the two AI-901 domains and their sub-areas, prioritizing weak areas with estimated hours, Microsoft Learn module links, and the matching Microsoft Press video lesson. Use when the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.