Skip to main content
skill CX Codex

crontap-quickstart — Claude Code skill: what it does, how to install

Selects the right Crontap resource, inspects plan limits, and verifies IANA timezones before provisioning jobs.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Crontap/skills --skill crontap-quickstart -a claude-code
Open on GitHub

What crontap-quickstart does

The skill helps an agent decide between outbound HTTP schedules, URL availability monitors, and heartbeat check-ins. It inspects remaining quotas by calling get_account_usage and comparing usage.combined against caps.combined. To prevent scheduling errors caused by static UTC offsets, it looks up official IANA timezone identifiers via list_timezones.

Connection is handled through the remote MCP server at https://mcp.crontap.com/mcp with OAuth or via the raw REST API using $CRONTAP_CLIENT_ID and $CRONTAP_API_KEY. Raw REST API access strictly requires an Ultra tier, meaning Starter and Pro accounts must connect through MCP.

What it helps with

  • decide between an HTTP schedule, an uptime monitor, and a heartbeat
  • inspect Crontap account usage and combined capacity limits
  • resolve standard IANA timezone strings for local-time execution
  • verify whether the workspace requires remote MCP or Ultra REST credentials

Example prompts for the agent

  • Check my Crontap quota and recommend whether to use an uptime monitor or a heartbeat
  • Find the accepted IANA timezone identifier for Copenhagen in Crontap
  • Inspect my active Crontap plan features before scheduling a recurring webhook

How to install crontap-quickstart

1Skills CLI (Vercel)

npx skills add Crontap/skills --skill crontap-quickstart -a claude-code

2Manually: put the files in place

~/.claude/skills/crontap-quickstart/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/crontap-quickstart/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about crontap-quickstart

How to install crontap-quickstart in Claude Code?

Run npx skills add Crontap/skills --skill crontap-quickstart -a claude-code. The skill file will be stored at ~/.claude/skills/crontap-quickstart/SKILL.md.

What does crontap-quickstart do?

It guides the agent in selecting between schedules, monitors, and heartbeats while validating account caps and local timezones.

Does crontap-quickstart require an Ultra subscription?

No, remote MCP access is supported across all Crontap tiers. Ultra is only needed if you choose raw REST API access with client credentials.

Source text

SKILL.md · MIT
---
name: crontap-quickstart
description: >
  Choose the right Crontap resource, inspect account limits, and verify an IANA
  timezone before making changes. Use when a user is new to Crontap or needs to
  decide between schedules, uptime monitors, and heartbeats.
license: MIT
metadata:
  version: "1.0.0"
  group: main
  order: 1
  title: Choose the right Crontap resource
  summary: Pick the right Crontap resource for the job, understand account limits, and connect with the correct timezone.
  bestFor: First setup, account limits, and timezones
  guide: https://crontap.com/mcp
  guideTitle: Connect Crontap MCP
  tools: get_account_usage,list_timezones
---

# Crontap quickstart

Crontap provides three related resources:

- A schedule sends an HTTP request on a cron or plain-English cadence.
- An uptime monitor probes a URL and records availability.
- A heartbeat expects an existing job to ping after it runs.

MCP lets the current agent manage these resources. Crontap owns HTTP scheduling
and observability, not the lifecycle of the MCP client.

## Prerequisites

Before using the required tools, check whether they are available. If any are
missing, stop and offer the user exactly two choices:

1. Connect Crontap MCP at `https://mcp.crontap.com/mcp`. MCP access works on
   every Crontap tier.
2. Configure `$CRONTAP_CLIENT_ID` and `$CRONTAP_API_KEY` for the raw API. Raw
   API access requires Ultra.

Do not silently choose a path or continue until the user selects one.

- Connect the remote MCP server at `https://mcp.crontap.com/mcp` and complete
  OAuth in the target Crontap account.
- Know the intended endpoint, local timezone, and desired failure signal.
- Treat endpoint authorization values and heartbeat ping URLs as secrets.

## Workflow

1. Call `get_account_usage` before creating resources when capacity is
   uncertain.
2. Compare `usage.combined` with `caps.combined` and inspect feature flags.
3. Choose a schedule for outbound execution, a monitor for endpoint
   availability, or a heartbeat for missed check-ins.
4. Call `list_timezones` when the exact IANA timezone is uncertain.
5. Hand off to the focused skill for creation and verification.

## MCP examples

Inspect the active tier, usage, caps, features, and plan options:

```json
{
  "tool": "get_account_usage",
  "arguments": {}
}
```

Find accepted timezone names:

```json
{
  "tool": "list_timezones",
  "arguments": {
    "query": "Copenhagen"
  }
}
```

Use the exact returned timezone, such as `Europe/Copenhagen`. Do not substitute
a fixed UTC offset for a local-time business schedule.

## REST fallback

The public API is a fallback only for accounts with Ultra API access. MCP is
not Ultra-only.

```bash
curl --fail-with-body https://api.crontap.com/v1/account \
  -H "ClientId: $CRONTAP_CLIENT_ID" \
  -H "ApiKey: $CRONTAP_API_KEY"
```

Keep both values in environment variables or a secret manager. Never put them
in a repository, agent transcript, URL, or example output.

## Safety and plan limits

- Starter, Pro, and Ultra use one combined cap for schedules, monitors, and
  heartbeats. Some resource-specific caps and cadence floors also apply.
- Treat the returned account object as authoritative. Do not hard-code prices
  or assume a feature from the tier name.
- If a tool returns a structured plan-limit error, present its ordered
  four-option ladder and identify the smallest viable option. Do not invent a
  fifth option or hide the all-plans URL.
- Confirm the target account before any write operation.

## Troubleshooting

- If OAuth fails, reconnect the MCP server in the client and retry once.
- If a timezone search returns no match, try a city or region substring.
- If REST returns `API_REQUIRES_ULTRA`, continue through MCP or let the user
  choose an Ultra option.
- If `MAX_ITEMS_REACHED` appears, do not retry the same create call unchanged.

## References

- [Crontap Agent Skills catalogue](https://crontap.com/skills)
- [Crontap MCP](https://crontap.com/mcp)
- [Crontap pricing](https://crontap.com/pricing)
- [Live REST API reference](https://api.crontap.com/docs/)
- [Crontap machine-readable product reference](https://crontap.com/llms.txt)

© Crontap · MIT · Crontap/skills

Similar skills

All skills for DevOps and infrastructure →

From the same set12

crontap-supabase-edge-function-cron This skill schedules recurring HTTP calls to Supabase Edge Functions using Crontap. It brings observable delivery, failure history, and retries. CX Codex +1 886installs crontap-replace-vercel-cron Moves a Vercel Cron schedule to Crontap while keeping the deployed HTTP route, timezone intent, and rollback plan. Use it for external scheduling. CX Codex +1 883installs crontap-heartbeat-for-cron Adds a Crontap dead-man's-switch ping to a recurring job, so you hear about a crash or a silent stop. Built for unattended cron work. CX Codex +1 883installs crontap-uptime-monitor Configures Crontap HTTP endpoint monitoring from Claude Code. It sets up health checks, defines failure thresholds, pauses monitors during releases, and inspects probe logs. CX Codex +1 882installs crontap-retries-and-idempotency Sets up Crontap retry policy and helps make a scheduled endpoint idempotent, so a repeated request does not create a second side effect. CX Codex +1 881installs crontap-ai-built-apps Configures recurring HTTP jobs and heartbeat monitoring for apps created in Lovable, Bolt, Replit, or v0. It offloads scheduling to Crontap after deployment. CX Codex +1 881installs crontap-recurring-agent-endpoint Puts an app-owned HTTP endpoint on a Crontap schedule and tracks completion with a heartbeat. Useful when your agent runtime already exists but has no clock of its own. CX Codex +1 880installs crontap-replace-github-actions-cron Replaces GitHub Actions cron triggers with Crontap HTTP dispatches with IANA timezone support. Eliminates schedule drift while keeping workflows and logs on GitHub. CX Codex +1 880installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor