Skip to content
TrustedSkillsbeta
Back to all skills

Cron Helper

Checked
tclawde·vlatest·other

Cron Helper simplifies scheduling tasks via cron expressions—useful for automating repetitive operations without complex scripting.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tclawde/openclaw-skills-user --skill cron-helper -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tclawde

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tclawde/openclaw-skills-user at c649e85165.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c649e85165
Manifest
cron-helper/SKILL.md
Scanned
2 files, 270 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The cron-helper skill allows AI agents to schedule tasks and execute them at specific intervals. It provides functionality for creating, listing, and managing scheduled jobs using standard cron syntax. This enables automation of recurring actions like data backups, report generation, or system maintenance within the agent's environment.

When to use it

  • Automated Backups: Schedule regular backups of important files or databases.
  • Report Generation: Automatically generate and distribute daily/weekly reports.
  • System Maintenance: Run scripts for cleaning up temporary files or performing system checks on a schedule.
  • Data Synchronization: Synchronize data between different systems at predefined intervals.

Key capabilities

  • Create cron jobs using standard cron syntax.
  • List existing scheduled tasks.
  • Manage (start, stop) existing cron jobs.

Example prompts

  • "Schedule a backup of my documents folder every Sunday at 2 AM."
  • "List all currently scheduled cron jobs."
  • "Stop the daily report generation task."

Tips & gotchas

The skill requires familiarity with standard cron syntax (e.g., "0 2 * * Sun"). Incorrectly formatted cron expressions can lead to unexpected behavior or failed job executions.