Skip to content

Better prompting #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jasonzbao merged 1 commit into from
Jul 31, 2026
Merged

Better prompting #146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions plugins/shared/skills/crons/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,14 @@ Scheduled work on Major is handled by **workflows**: graphs of steps run by the

The legacy `cron.json` system is retired — the file is no longer read on deploy, and existing crons were migrated to workflows automatically. If the project still has a `cron.json`, it has no effect and can be deleted.

## Your job: implement the route
## Building a scheduled job

From a coding session you build the app side only — an HTTP route that performs the work:
Both halves are yours to build:

1. **The route** — implement an HTTP route in the app that performs the work (see below), and deploy it: workflows call the deployed app.
2. **The workflow** — invoke the **`workflow-builder`** skill and follow it to build the workflow itself: create the workflow, define a cron trigger and an `app_call` node targeting the route's method and path, then save, test, and publish through that skill's lifecycle.

## The route

```typescript
// app/api/jobs/cleanup/route.ts
Expand All @@ -23,17 +28,12 @@ export async function POST() {

How workflow calls reach the route:

- Calls go to the **deployed** app, so the app must be deployed before a workflow can call the route.
- Calls go to the **deployed** app, so the app must be deployed before the workflow can call the route.
- Requests arrive authenticated as the Major user the workflow runs as (via a platform-signed app-call JWT) — the route needs no webhook access and the app does not need to be public.
- The step's configured input arrives as query params for GET/DELETE and as a JSON body for POST/PUT/PATCH.
- The response body becomes the step's output, available to later steps in the workflow.

## Creating the schedule

Workflows are created and managed in the Major web app, not from this coding session. After building the route:

1. Tell the user to deploy so the route exists on the deployed app.
2. Point them to the **Workflows** page in the Major dashboard to create (or update) a workflow with a cron trigger and an `app_call` step targeting the route's method and path.
## Cron schedules

Cron triggers use a 5-field cron expression (`minute hour day-of-month month day-of-week` — no seconds field) with an IANA timezone. Common schedules:

Expand Down
Loading