Skip to content

reply-team/jason-ai / skills/runtime/quick-start

quick-start

Verified

Use when a person has just had Jason installed and wants to be taken to their first campaign, when an install prompt says to start the quick-start skill, or when somebody with no campaign yet asks where to begin. It asks one question, reads which channels are routed instead of asking, and says the plan in one message.

Quick start

You take a person from a ready installation to a first campaign in a few minutes. Do not explain Jason first: begin with step 1. Status: draft. Its commands parse against this build.

1. One question

Send this, with nothing before it, as free text and not through a question tool:

What do you sell, and who should buy it? One sentence is enough, and a link to your site works too.

If you like, add a line about yourself and how you write. You can also do that later.

A no, or silence about the second part, is an answer. Do not ask for it again while sends are manual.

2. Read the channels, never ask for them

Make a project named from what the person sells, or take the one that already holds it, and make the campaign in it, under a name drawn from what the campaign is for, with the offer and the audience in their own words as its context (managed-campaign-work says how). Neither is asked about. Then ask the runtime which provider each channel goes through. Never ask for them: the person is not asked which channels they have. Make each idempotency key new per run.

jason project list --query payroll
jason project create --name "Payroll for Latin America"
jason campaign create --name "Seed-stage owners in Mexico and Colombia" --project prj_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --context '{"offer":"payroll for startups hiring in Latin America","audience":"owners of seed-stage startups in Mexico and Colombia"}' --idempotency-key payroll-latam-owners-20261114-1530
jason route resolve --campaign cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --operation message.send --channel email
jason route resolve --campaign cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --operation message.send --channel linkedin

A channel with a route has a provider, which the answer names; one with no route is not connected. A route does not prove that an account is connected, so read the accounts of each channel with a route now, before "go": a draft campaign's accounts are read on request, and nothing is recorded or started.

jason sender list --campaign cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --channel email --owners own --limit 100
jason sender list --campaign cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --channel linkedin --owners own --limit 100

The channels decide the form of the first message: email only; LinkedIn only, where it is an invitation and not a letter; or both, and then several channels together. Draft nothing before they are known.

3. One message, one stop

Send one message that holds the plan: the goal, who Jason will look for, the channel or channels, how it will write ("short, plain, in your name"), and the state of the channels. Say in passing what was made, as a draft: the project and the campaign, and that both names are the person's to change. Say once, as a fact and never as a question, how messages go: "Every message waits for your yes. Later you can let messages go on their own, for people who have not answered yet and for people who have; in Jason Desktop that is Settings, "How messages go", and anywhere else tell me when you want it." It is a statement the person need not answer, and it is said in this message only. End it with exactly: "Say what to change, or say go." It carries no list of questions and uses no question tool; only when the person asks to change something do you use the question tool, with the recommended choice first.

  • The accounts of a channel are said only for the provider its sends go through. This guard governs the first bullet below, the firm "holds no account" sentence included: a channel's count is said, and a channel is said to hold no account, only where the plugin_id of its sender list answer is the provider route resolve named for that channel's sends; an empty page from any other plugin says nothing about the channel's accounts.
  • A channel has a route. Say: "Email goes out through {provider}." and "LinkedIn goes out through {provider}.", or one sentence when both go through the same provider. Then say what the read found, in one line: "{N} mailboxes and {M} LinkedIn accounts are connected; you can add more at any time." With one channel routed, name only that channel's accounts. Count the accounts whose status is active, and the others apart; where a channel's answer says has_more, say its count as "{N} or more", as the skill reads one page and no further. A routed channel that holds no account is said firmly: not one message leaves on it until an account is connected, and name the one step as the last item of this list does.
  • A channel's accounts were read at another provider. Where the plugin_id of a channel's sender list answer is not the provider route resolve named for that channel's sends, say only the provider its sends go through, and no number for it.
  • A read that fails or is slow. The count never holds the person up: a read that fails or is slow leaves the line without numbers, and the message goes on. Each channel's read stands alone: a channel whose read fails or does not answer drops only its own number, and the other channel's number is still said. The CLI waits up to about 90 seconds for an answer; past that, go on without the number and do not wait for a second try.
  • A channel has no route. Say: "{Channel} is not connected."
  • Neither has a route. Say it firmly: no channel is connected, connecting your provider now is recommended and is one step, and until it is done not one message leaves. That step is the person's one act, "connect your provider". With Reply it is one sign-in only they can do: in a terminal reply auth login (on Windows PowerShell, reply.cmd auth login), and you do the rest (the CLI, the plugin, its grant and its route: the Reply CLI section and steps 3 to 5 of docs/golden-path.md); in the window, the Accounts page. Then say: "It can be done later."

4. A sample only on request

If the person puts the channels off, answer in a reply of its own and offer, in one sentence, to show what a first message would look like. Never put the offer in the plan message. Show a sample only to a person who accepts, and call it a sample. Nobody who did not ask sees one.

5. After "go"

Nothing is started before the person's go. From "go" the work goes on through planner-in-session for the plan and managed-campaign-work, which owns starting the campaign, the people and the work. planner-in-session takes the plan from the campaign that exists: the brief and the goals go into its context, and no second campaign is made. Then you start the campaign:

jason campaign update-context cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --set '{"goals":[{"id":"demo","kind":"demo","title":"A demo with the operations lead","reached_when":"a demo is on their calendar","order":1}]}' --reason "the plan agreed with the person"
jason campaign start cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD

In the chat of Jason Desktop you cannot start the campaign: starting it is the person's own act. There, once the plan is agreed and its work is queued, say once that it is ready and that they press Start at the top of the campaign's chat, and never say it has started until jason campaign get answers the status active. Elsewhere you start it on their go, as above.

Until the person chooses otherwise, every message still waits for their yes (approval-boundaries); approvals-and-questions is where they are asked whether sends to people who have not answered, or to people who have, may go on their own, and you never ask it here or set it: step 3 has said the fact, once. The message after "go" that hands over to the planning ends with one line: "There is a guided check of the wiring; say so if you want it."

Rules

  • Never ask for a preference. A preference is set only on the person's own word, never written from what you assume or already know of them; you may say "I take it you are ..., tell me if not". Do not remind them of preferences while sends are manual; the one sentence of step 3 on how messages go is a fact, said once, and is not a reminder. In the chat of Jason Desktop a missing name is said all the same, once: that nobody is named to write as, and that they set it in Settings under "Your name and tone"; a missing tone is said once too, as theirs to add there.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall