Agent skill

Trigger Scheduled Tasks

How to write and use scheduled Trigger.dev tasks. An agent skill from trycompai/comp.

AGPL-3.0Auto-check passedProductivity & Automation

Install Trigger Scheduled Tasks

skills CLI

$ npx skills add trycompai/comp --skill trigger-scheduled-tasks -a claude-code

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

GitHub CLI

$ gh skill install trycompai/comp trigger-scheduled-tasks --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/trycompai/comp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/trigger-scheduled-tasks .claude/skills/trigger-scheduled-tasks && 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/

Paste into Claude Code

Install the "trigger-scheduled-tasks" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks into .claude/skills/trigger-scheduled-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-scheduled-tasks", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add trycompai/comp --skill trigger-scheduled-tasks -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install trycompai/comp trigger-scheduled-tasks --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/trigger-scheduled-tasks .agents/skills/trigger-scheduled-tasks && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "trigger-scheduled-tasks" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks into .agents/skills/trigger-scheduled-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-scheduled-tasks", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add trycompai/comp --skill trigger-scheduled-tasks -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install trycompai/comp trigger-scheduled-tasks --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/trigger-scheduled-tasks .cursor/skills/trigger-scheduled-tasks && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "trigger-scheduled-tasks" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks into .cursor/skills/trigger-scheduled-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-scheduled-tasks", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/trycompai/comp.git --path .agents/skills/trigger-scheduled-tasks

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add trycompai/comp --skill trigger-scheduled-tasks -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install trycompai/comp trigger-scheduled-tasks --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/trigger-scheduled-tasks .gemini/skills/trigger-scheduled-tasks && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "trigger-scheduled-tasks" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks into .gemini/skills/trigger-scheduled-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-scheduled-tasks", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install trycompai/comp trigger-scheduled-tasks

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add trycompai/comp --skill trigger-scheduled-tasks -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/trigger-scheduled-tasks .github/skills/trigger-scheduled-tasks && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "trigger-scheduled-tasks" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks into .github/skills/trigger-scheduled-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-scheduled-tasks", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add trycompai/comp --skill trigger-scheduled-tasks -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install trycompai/comp trigger-scheduled-tasks --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/trigger-scheduled-tasks .opencode/skills/trigger-scheduled-tasks && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "trigger-scheduled-tasks" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/trigger-scheduled-tasks into .opencode/skills/trigger-scheduled-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-scheduled-tasks", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: trigger-scheduled-tasks
GitHub stars: 2k
Token cost: ~768 tokens
SKILL.md length: 103 words
Files: 1
Skills in repo: 31
Repo updated: Oct 2, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

How to write and use scheduled Trigger.dev tasks. An agent skill from trycompai/comp.

Tasks that involve Scheduled and recurring tasks
SKILL.md covers Define a scheduled task, Attach schedules, Cron syntax (no seconds) and When schedules won't trigger, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Trigger Scheduled Tasks is an agent skill from trycompai/comp. How to write and use scheduled Trigger.dev tasks

Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Scheduled and recurring tasks. The repository describes itself as: AI Native platform to get companies compliant - Vanta & Drata Alternative. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve Scheduled and recurring tasks

Example prompts

“/trigger-scheduled-tasks”

What it can do on your machine

Read from SKILL.md and the folder at commit 1bf4d52. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
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

Trigger Scheduled Tasks loads about 768 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 103 words of instructions outside code blocks.

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

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 trycompai/comp at commit 1bf4d52, republished under its AGPL-3.0 licence (© trycompai). 103 words, ~768 tokens.

Download SKILL.mdSave it as .claude/skills/trigger-scheduled-tasks/SKILL.md (or your agent's skills folder).

name: trigger-scheduled-tasks
description: How to write and use scheduled Trigger.dev tasks

Source Cursor rule: .cursor/rules/trigger.scheduled-tasks.mdc. Original file scope: **/trigger/**/*.ts. Original Cursor alwaysApply: false.

Scheduled tasks (cron)

Recurring tasks using cron. For one-off future runs, use the delay option.

Define a scheduled task

import { schedules } from "@trigger.dev/sdk";

export const task = schedules.task({
  id: "first-scheduled-task",
  run: async (payload) => {
    payload.timestamp; // Date (scheduled time, UTC)
    payload.lastTimestamp; // Date | undefined
    payload.timezone; // IANA, e.g. "America/New_York" (default "UTC")
    payload.scheduleId; // string
    payload.externalId; // string | undefined
    payload.upcoming; // Date[]

    payload.timestamp.toLocaleString("en-US", { timeZone: payload.timezone });
  },
});

Scheduled tasks need at least one schedule attached to run.

Attach schedules

Declarative (sync on dev/deploy):

schedules.task({
  id: "every-2h",
  cron: "0 */2 * * *", // UTC
  run: async () => {},
});

schedules.task({
  id: "tokyo-5am",
  cron: { pattern: "0 5 * * *", timezone: "Asia/Tokyo", environments: ["PRODUCTION", "STAGING"] },
  run: async () => {},
});

Imperative (SDK or dashboard):

await schedules.create({
  task: task.id,
  cron: "0 0 * * *",
  timezone: "America/New_York", // DST-aware
  externalId: "user_123",
  deduplicationKey: "user_123-daily", // updates if reused
});

Dynamic / multi-tenant example

// /trigger/reminder.ts
export const reminderTask = schedules.task({
  id: "todo-reminder",
  run: async (p) => {
    if (!p.externalId) throw new Error("externalId is required");
    const user = await db.getUser(p.externalId);
    await sendReminderEmail(user);
  },
});

// app/reminders/route.ts
export async function POST(req: Request) {
  const data = await req.json();
  return Response.json(
    await schedules.create({
      task: reminderTask.id,
      cron: "0 8 * * *",
      timezone: data.timezone,
      externalId: data.userId,
      deduplicationKey: `${data.userId}-reminder`,
    })
  );
}

Cron syntax (no seconds)

* * * * *
| | | | └ day of week (0–7 or 1L–7L; 0/7=Sun; L=last)
| | | └── month (1–12)
| | └──── day of month (1–31 or L)
| └────── hour (0–23)
└──────── minute (0–59)

When schedules won't trigger

Dev: only when the dev CLI is running.
Staging/Production: only for tasks in the latest deployment.

SDK management (quick refs)

await schedules.retrieve(id);
await schedules.list();
await schedules.update(id, { cron: "0 0 1 * *", externalId: "ext", deduplicationKey: "key" });
await schedules.deactivate(id);
await schedules.activate(id);
await schedules.del(id);
await schedules.timezones(); // list of IANA timezones

Dashboard

Create/attach schedules visually (Task, Cron pattern, Timezone, Optional: External ID, Dedup key, Environments). Test scheduled tasks from the Test page.

Files

Just SKILL.md in .agents/skills/trigger-scheduled-tasks of trycompai/comp.

Open the folder on GitHubat commit 1bf4d52

Compare with similar skills

Trigger Scheduled Tasks 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.

Trigger Scheduled Tasks compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Trigger Scheduled Tasks this skilltrycompai/comp	2k	—	~768	Automated safety check: Pass	AGPL-3.0	5 days ago
ScheduleTinyAGI/tinyagi	3.6k	—	~1.4k	Automated safety check: Pass	MIT	6 mo ago
Send User MessageTinyAGI/tinyagi	3.6k	—	~829	Automated safety check: Pass	MIT	6 mo ago
Cron Opsczl9707/build-your-own-openclaw	1.9k	—	~593	Automated safety check: Pass	MIT	3 mo ago
Wp Wpcli And OpsAutomattic/agent-skills	211	2 repos	~988	Automated safety check: Pass	None	8 mo ago
Ohdearohdearapp/ohdear-cli	141	—	~1.1k	Automated safety check: Pass	MIT	1 mo ago

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
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
Jobs
physiclaw/PhysiClaw
A skill your agent uses when the task involves scheduling future work — any "remind me at …", "every weekday …", "check again in 30 min", or closing a fired cron job.
386 GitHub stars~1.1k tokensUpdated 2 days ago
Productivity & AutomationAuto-check passed

Questions about Trigger Scheduled Tasks

What does Trigger Scheduled Tasks do?

How to write and use scheduled Trigger.dev tasks. An agent skill from trycompai/comp. Trigger Scheduled Tasks is an agent skill from trycompai/comp.

When should I use Trigger Scheduled Tasks?

Trigger Scheduled Tasks fits situations like: tasks that involve Scheduled and recurring tasks.

How do I install Trigger Scheduled Tasks in Claude Code?

Run `npx skills add trycompai/comp --skill trigger-scheduled-tasks -a claude-code`. Or copy the skill folder (.agents/skills/trigger-scheduled-tasks in trycompai/comp) into .claude/skills/trigger-scheduled-tasks in your project. Claude Code loads it when a task matches its description.

How do I install Trigger Scheduled Tasks in Codex?

Run `npx skills add trycompai/comp --skill trigger-scheduled-tasks -a codex`. Or copy the skill folder (.agents/skills/trigger-scheduled-tasks in trycompai/comp) into .agents/skills/trigger-scheduled-tasks in your project. Codex loads it when a task matches its description.

Can I use Trigger Scheduled Tasks 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 trycompai/comp --skill trigger-scheduled-tasks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trigger-scheduled-tasks, .gemini/skills/trigger-scheduled-tasks, .github/skills/trigger-scheduled-tasks and .opencode/skills/trigger-scheduled-tasks in your project.

What does Trigger Scheduled Tasks need to run?

SKILL.md names no scripts, command-line tools or credentials: Trigger Scheduled Tasks is instructions for the agent only.

Does Trigger Scheduled Tasks 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 Trigger Scheduled Tasks 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 Trigger Scheduled Tasks use?

Trigger Scheduled Tasks is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Trigger Scheduled Tasks use?

About 768 tokens (SKILL.md is roughly 3.1k 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 Trigger Scheduled Tasks?

Skills that share tags, products or a category with Trigger Scheduled Tasks: 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 Wp Wpcli And Ops (Automattic/agent-skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Trigger Scheduled Tasks?

trycompai (a GitHub organization) maintains it in trycompai/comp, which has 2,016 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 2, 2026.

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

Trigger Scheduled Tasks

Install Trigger Scheduled Tasks

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Scheduled tasks (cron)

Define a scheduled task

Attach schedules

Dynamic / multi-tenant example

Cron syntax (no seconds)

When schedules won't trigger

SDK management (quick refs)

Dashboard

Files

Compare with similar skills

Similar skills

Schedule

Send User Message

Cron Ops

Wp Wpcli And Ops

Ohdear

Jobs

More from trycompai/comp

API Endpoint Contract

Check Results Service

Data

Diagnose Generation Failure

Forms

Code

Questions about Trigger Scheduled Tasks

Install Trigger Scheduled Tasks

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Scheduled tasks (cron)

Define a scheduled task

Attach schedules

Dynamic / multi-tenant example

Cron syntax (no seconds)

When schedules won't trigger

SDK management (quick refs)

Dashboard

Files

Compare with similar skills

Similar skills

More from trycompai/comp

Related

Questions about Trigger Scheduled Tasks