Crontap Agent Skills

Install Crontap skills in your AI editor.

Skills are plain instruction files your editor reads when a task matches. MCP is the live connection to your Crontap account. They work best together.

npx skills add Crontap/skills
A Crontap skill gives an AI editor the steps and tool names for a scheduling task.

Built for your project

Put repeatable steps next to the code.

Your editor can load the right instructions without guessing how this project schedules or monitors work.

Keep it with the project
A project install gives your editor the right instructions for the code you are working on.
Open it whenever you want
Each skill is plain Markdown, so you can review the steps and examples before using them.

Install and manage

Install skills in the right folder.

Run the picker in your project. It detects supported agents, chooses the right folder, and lets you select the skills you need.

Choose skills for this project.

Keep the default project scope, select an editor, then choose from the 12 Crontap skills.

npx skills add Crontap/skills

Share across projects.

Use a global install when you want the same skills everywhere.

npx skills add Crontap/skills --global

Install every skill.

Skip the picker and add the full collection to detected agents.

npx skills add Crontap/skills --all

Manage installed skills.

List what is installed, pull updates, or remove skills you no longer need.

List installed skills

npx skills list

Update installed skills

npx skills update

Remove installed skills

npx skills remove

Commands checked with skills CLI 1.5.26 on 15 September 2026. Run npx skills add --help for current options.

Connect MCP for live account access.

Crontap has verified the setup guides below. Each one connects your editor to your schedules, monitors, and heartbeats.

Other MCP clients

Not verified by Crontap

Using something else? See the generic setup for other MCP clients.

Open generic setup

Skills + MCP

Skills teach the steps. MCP makes the change.

The skill tells your editor what to do and what to verify. MCP gives it approved access to your Crontap account.

Connect Crontap MCP
  1. 1

    Your editor

    Loads the matching skill from your project.

  2. 2

    The skill

    Teaches the steps and how to check the result.

  3. 3

    Crontap MCP

    Makes the change you approve in your account.

Start here · 6 skills

6 skills most projects need.

Pick the job you need to do. Each skill gives your editor clear steps, examples, and a way to check the result.

Start 01

Choose the right Crontap resource

v1.0.0

Pick the right Crontap resource for the job, understand account limits, and connect with the correct timezone.

Best for

First setup, account limits, and timezones

MCP tools

  • get_account_usage
  • list_timezones
npx skills add Crontap/skills --skill crontap-quickstart

Start 02

Schedule an HTTP job

v1.0.0

Turn any API endpoint, webhook, or cloud function into a recurring request with timing verified before launch.

Best for

Webhooks, API calls, and cloud functions

MCP tools

  • create_schedule
  • update_schedule
  • preview_schedule
  • get_schedule_history
npx skills add Crontap/skills --skill crontap-schedule-http-job

Start 03

Turn plain English into a safe schedule

v1.0.0

Translate everyday scheduling language into reviewed cron, timezone, and next-run details before anything is saved.

Best for

Business-time schedules, ambiguity, and DST

MCP tools

  • preview_schedule
npx skills add Crontap/skills --skill crontap-natural-language-schedules

Start 04

Monitor an HTTP endpoint

v1.0.0

Watch an HTTP endpoint with clear failure thresholds, deploy pauses, and probe history for every check.

Best for

Uptime checks, failure thresholds, and deploy pauses

MCP tools

  • create_monitor
  • update_monitor
  • get_monitor_probes
npx skills add Crontap/skills --skill crontap-uptime-monitor

Start 05

Add a heartbeat to a recurring job

v1.0.0

Add reliable check-ins to an existing recurring job and receive an alert when expected reports stop.

Best for

Missed jobs, grace periods, and explicit failures

MCP tools

  • create_heartbeat
  • get_heartbeat_pings
  • rotate_heartbeat_token
npx skills add Crontap/skills --skill crontap-heartbeat-for-cron

Start 06

Debug failed schedule runs

v1.0.0

Trace failed runs through status, timing, and authentication evidence, then confirm the fix on the next attempt.

Best for

HTTP errors, timeouts, auth, and run history

MCP tools

  • get_schedule_history
  • get_schedule
npx skills add Crontap/skills --skill crontap-debug-failed-runs

Playbooks · 6 patterns

Playbooks for recurring work.

Use these for safe retries, migrations, AI-built apps, and recurring endpoints your app owns.

07

Make retries safe

Keep retries bounded and side effects idempotent, with the final delivery outcome visible in schedule history.

Best for · v1.0.1

Backoff policies, duplicate prevention, and recovery

  • update_schedule
  • get_schedule_history
npx skills add Crontap/skills --skill crontap-retries-and-idempotency
08

Replace Vercel Cron

Move a Vercel cron to a protected endpoint with finer timing, pause controls, and searchable run history.

Best for · v1.0.0

Protected routes, faster cadences, and safe cutovers

  • create_schedule
  • pause_schedule
  • resume_schedule
npx skills add Crontap/skills --skill crontap-replace-vercel-cron
09

Replace GitHub Actions cron

Replace drifting repository schedules with a protected dispatch endpoint and evidence for every triggered run.

Best for · v1.0.0

Repository dispatch, drift, and timezone-safe triggers

  • create_schedule
  • pause_schedule
  • resume_schedule
npx skills add Crontap/skills --skill crontap-replace-github-actions-cron
10

Schedule a Supabase Edge Function

Call a Supabase Edge Function on a dependable cadence without exposing service credentials in logs.

Best for · v1.0.0

Protected Edge Functions, RPCs, and database jobs

  • create_schedule
npx skills add Crontap/skills --skill crontap-supabase-edge-function-cron
12

Schedule an app-owned agent endpoint

Run recurring agent work behind an endpoint the app owns, then monitor completion through a heartbeat.

Best for · v1.0.0

Recurring workflows with explicit HTTP boundaries

  • create_schedule
  • create_heartbeat
  • get_heartbeat_pings
npx skills add Crontap/skills --skill crontap-recurring-agent-endpoint

Review before installing

Read every skill before you install it.

GitHub shows the same plain Markdown files the skills CLI adds to your project.

01Review the instructions
Open any SKILL.md on GitHub and read the full steps before you add it to your editor.
02Install what you inspected
The public GitHub repository mirrors the same skill files that the CLI installs.
03Checked and versioned
Tool names and examples are checked against real schemas. Checks also catch secrets and broken links, and every card shows its version.

FAQ

Crontap Agent Skills, answered.

What does an Agent Skill install?
It installs local instruction files that a compatible AI editor can read when a task matches. A skill does not execute code, grant permissions, or connect an account.
Do Crontap skills require MCP?
No. Skills teach your editor the steps. MCP lets it make approved changes in your Crontap account on every tier. The raw REST API option requires Ultra credentials.
Which agents can install these skills?
The skills CLI detects supported agents and puts skills in their expected folders. Run npx skills add --help for the current compatibility list.
Which MCP clients has Crontap verified?
Crontap has verified live account access for Cursor, Claude, Claude Code, ChatGPT, Codex CLI, VS Code, Devin Local, and Gemini CLI. Other MCP clients have a separate generic setup that is not verified by Crontap. See the generic MCP setup.
Should I install skills globally or in a project?
Start project-local so the guidance travels with the relevant codebase and stays scoped to that work. Use --global only when you intentionally want the same skills across projects.
How do I update or remove a skill?
Run npx skills update to update installed skills, or npx skills remove to choose skills to remove. Add --global only when you want to manage the global install.
Can I inspect a skill before installing it?
Yes. Every catalogue card links to its SKILL.md on GitHub, where you can read the same instructions the CLI installs.

Ready to install?

Put the right Crontap workflow in your editor.

Open the picker in your project and choose the skills that match the work your app runs.