Agent skill

Scheduler Change

by gocronx-team in gocronx-team/gocron

Safely implement, diagnose, or review changes to gocron scheduling and task execution.

MITAuto-check passedProductivity & Automation

Install Scheduler Change

skills CLI
$ npx skills add gocronx-team/gocron --skill scheduler-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gocronx-team/gocron scheduler-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gocronx-team/gocron.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/scheduler-change .claude/skills/scheduler-change && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scheduler-change
GitHub stars
801
Token cost
~1.1k tokens
SKILL.md length
543 words
Files
2
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Safely implement, diagnose, or review changes to gocron scheduling and task execution.

  • Cron registration
  • SKILL.md covers Compatibility invariants, Performance invariants, Define invariants and Inspect the whole execution path, plus 1 more section
  • Calls go
  • Leader election

What it does

Scheduler Change is an agent skill from gocronx-team/gocron. Safely implement, diagnose, or review changes to gocron scheduling and task execution. Use for cron registration, leader election, task dispatch, concurrency queues, manual runs, retries, timeouts, cancellation, task logs, agent execution, failover, or shared scheduler state.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Productivity & Automation, covering Scheduled and recurring tasks and Backup and disaster recovery. The repository describes itself as: distributed scheduled task management system. The licence is MIT.

When your agent uses it

  • Cron registration
  • Leader election
  • Concurrency queues
  • Agent execution

Example prompts

  • “/scheduler-change”

What it can do on your machine

Read from SKILL.md and the folder at commit e76e9da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scheduler Change loads about 1.1k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 543 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gocronx-team/gocron at commit e76e9da, republished under its MIT licence (© gocronx-team). 543 words, ~1,139 tokens.

Download SKILL.mdSave it as .claude/skills/scheduler-change/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
scheduler-change
description
Safely implement, diagnose, or review changes to gocron scheduling and task execution. Use for cron registration, leader election, task dispatch, concurrency queues, manual runs, retries, timeouts, cancellation, task logs, agent execution, failover, or shared scheduler state.

Change the gocron scheduler

Assume scheduler bugs can duplicate, lose, or overlap production jobs. Make the execution semantics explicit before editing.

Compatibility invariants

  • When wire behavior changes, test N gocron with N-1 gocron-node and the reverse. Preserve execution, output, cancellation, and terminal status.
  • Evolve protobuf/gRPC additively: never renumber or reuse field numbers, remove a supported field, or change an existing RPC's semantics. Reserve removed identifiers.
  • Keep the previous RPC/execution path during the compatibility window. Check capability and use a deterministic fallback before invoking new behavior.
  • Never retry or reroute after an ambiguous remote acceptance; that can run a user's job twice. Preserve retry counts and status transitions on fallback.
  • When distributed ownership or state changes, verify temporary N/N-1 HA mixtures do not duplicate dispatch, stick in Running, or falsely cancel.

Performance invariants

  • Establish a baseline for materially affected hot paths with representative task/node counts and measure applicable scheduler metrics.
  • Bound goroutines, queues, retries, log buffers, streams, timers, and retained execution state. Define backpressure and overload behavior explicitly.
  • Do not hold locks during database/network/filesystem/command/notification I/O or serialize unrelated tasks behind one global lock.
  • Batch or coalesce high-frequency status/log writes when semantics permit. Verify SQLite concurrent read/write and busy/lock behavior separately.
  • Add a benchmark or deterministic load regression test for material hot-path changes. Compare before/after under the same workload and report the result.

Define invariants

Write down which behavior the change must preserve:

  • whether execution is at-most-once, at-least-once, or best-effort;
  • what happens during leader loss, restart, network timeout, or agent retry;
  • how scheduled and manual runs interact;
  • whether the same task may overlap and how queue limits behave;
  • when task counts, instance maps, logs, and final status are updated;
  • who owns cancellation and how resources are released.

If the intended behavior is ambiguous and different choices change user-visible execution, ask before implementing.

Show full SKILL.md (243 more words)Show less

Inspect the whole execution path

Trace from route or cron callback through internal/service/task.go, scheduler state, models, RPC/agent code, task logs, and notifications. Search every read and write of changed global state. Identify goroutine ownership, locks, channel capacity, blocking sends, callbacks, timers, and cleanup paths.

Do not:

  • hold a mutex while performing database, network, command, or notification I/O;
  • start an unbounded goroutine per event;
  • close a channel from a receiver or from multiple owners;
  • use check-then-act state without the same lock or atomic operation;
  • treat a timeout as proof that remote execution did not start;
  • silently drop queued work or overwrite the terminal task status.

Keep refactors incremental. Extracting a component is useful when it creates a test seam; moving globals without defining ownership is not.

Test adversarial sequences

Add deterministic tests for the changed invariant, including the relevant subset of:

  • simultaneous triggers for one task;
  • queue full, cancellation, timeout, and shutdown;
  • disable/remove while queued or running;
  • repeated callback or retry;
  • leader handoff and stale leader behavior;
  • remote execution accepted but response lost;
  • N-1 protocol doubles in both client/server directions and fallback paths;
  • panic/error cleanup and counter consistency.

Avoid sleep-based assertions where a channel, fake clock, barrier, or polling condition can make the test deterministic.

Run focused tests first, then:

bash
go test -race ./internal/service/... ./internal/modules/... ./internal/rpc/...
go test -race -count=10 <changed-package>

Adapt package paths if the changed execution path differs. Invoke $verify before committing. Report the promised execution semantics, race-sensitive state touched, failure cases tested, performance evidence when relevant, and any behavior that remains best-effort.

© gocronx-team, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/scheduler-change of gocronx-team/gocron.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e76e9da

Compare with similar skills

Scheduler Change next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scheduler Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scheduler Change this skillgocronx-team/gocron801—~1.1kAutomated safety check: PassMIT
ScheduleTinyAGI/tinyagi3.6k—~1.4kAutomated safety check: PassMIT
Send User MessageTinyAGI/tinyagi3.6k—~829Automated safety check: PassMIT
Cron Opsczl9707/build-your-own-openclaw1.9k—~593Automated safety check: PassMIT
X Bookmarkssharbelxyz/x-bookmarks289—~2kAutomated safety check: NotesNone
Wp Wpcli And OpsAutomattic/agent-skills2112 repos~988Automated safety check: PassNone

Similar skills

  • Schedule

    TinyAGI/tinyagi

    Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.

    3.6k GitHub stars~1.4k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check passed
  • Send User Message

    TinyAGI/tinyagi

    Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp).

    3.6k GitHub stars~829 tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check passed
  • Cron Ops

    czl9707/build-your-own-openclaw

    Create, list, and delete scheduled cron jobs. An agent skill from czl9707/build-your-own-openclaw.

    1.9k GitHub stars~593 tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed
  • X Bookmarks

    sharbelxyz/x-bookmarks

    Fetch, summarize, and manage X/Twitter bookmarks via bird CLI or X API v2.

    289 GitHub stars~2k tokensUpdated 7 mo ago
    Productivity & AutomationAuto-check: notes
  • Wp Wpcli And Ops

    Automattic/agent-skills

    A skill your agent uses when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and…

    211 GitHub starsUsed in 2 repos~988 tokens
    Productivity & AutomationAuto-check passed
  • Ohdear

    ohdearapp/ohdear-cli

    Manage Oh Dear website monitoring using the ohdear CLI. An agent skill from ohdearapp/ohdear-cli.

    141 GitHub stars~1.1k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from gocronx-team/gocron

All 8 skills in this repo
  • Migration

    gocronx-team/gocron

    Create, review, or verify gocron database migrations across SQLite, MySQL, and PostgreSQL.

    801 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Security Check

    gocronx-team/gocron

    Audit or harden gocron security across Go, pnpm workspaces, containers, authentication, authorization, secrets, command execution, SSRF, and dependency vulnerabilities.

    801 GitHub stars~690 tokensUpdated yesterday
    Auto-check passed
  • Dependency Update

    gocronx-team/gocron

    Review, apply, verify, or merge gocron dependency updates from Dependabot or manual requests.

    801 GitHub stars~891 tokensUpdated yesterday
    Auto-check passed
  • API Feature

    gocronx-team/gocron

    Implement or review an end-to-end gocron HTTP API change. An agent skill from gocronx-team/gocron.

    801 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Release

    gocronx-team/gocron

    Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag.

    801 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Release

    gocronx-team/gocron

    Cut a gocron release — bump AppVersion, align the migration version id, run the full CI check locally, and tag only when everything is green.

    801 GitHub stars~586 tokensUpdated yesterday
    Auto-check passed

Questions about Scheduler Change

What does Scheduler Change do?

Safely implement, diagnose, or review changes to gocron scheduling and task execution. Scheduler Change is an agent skill from gocronx-team/gocron. Safely implement, diagnose, or review changes to gocron scheduling and task execution.

When should I use Scheduler Change?

Scheduler Change fits situations like: cron registration; leader election; concurrency queues; agent execution.

How do I install Scheduler Change in Claude Code?

Run `npx skills add gocronx-team/gocron --skill scheduler-change -a claude-code`. Or copy the skill folder (.agents/skills/scheduler-change in gocronx-team/gocron) into .claude/skills/scheduler-change in your project. Claude Code loads it when a task matches its description.

How do I install Scheduler Change in Codex?

Run `npx skills add gocronx-team/gocron --skill scheduler-change -a codex`. Or copy the skill folder (.agents/skills/scheduler-change in gocronx-team/gocron) into .agents/skills/scheduler-change in your project. Codex loads it when a task matches its description.

Can I use Scheduler Change in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gocronx-team/gocron --skill scheduler-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scheduler-change, .gemini/skills/scheduler-change, .github/skills/scheduler-change and .opencode/skills/scheduler-change in your project.

What does Scheduler Change need to run?

Going by SKILL.md and its folder, Scheduler Change needs the command-line tools its instructions call (go).

Does Scheduler Change access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Scheduler Change safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scheduler Change use?

Scheduler Change is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scheduler Change use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scheduler Change?

Skills that share tags, products or a category with Scheduler Change: Schedule (TinyAGI/tinyagi, 3.6k stars), Send User Message (TinyAGI/tinyagi, 3.6k stars), Cron Ops (czl9707/build-your-own-openclaw, 1.9k stars) and X Bookmarks (sharbelxyz/x-bookmarks, 289 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scheduler Change?

gocronx-team (a GitHub organization) maintains it in gocronx-team/gocron, which has 801 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

Source: gocronx-team/gocron on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.