kortix-onboarding

Guides new Kortix users through a five-stage first session ending in a finished deliverable.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill kortix-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kortix-onboarding
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/managed/.kortix/opencode/skills/kortix-onboarding
Command: npx skills add https://github.com/kortix-ai/suna --skill kortix-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New users often arrive at Kortix unsure what it can do, send vague first prompts, and leave before experiencing a real result. This Skill turns a first session into a structured onboarding flow that produces one tangible deliverable and builds toward continued usage.

Core Features & Use Cases

  • Five-stage onboarding flow: Set expectations, sharpen a vague ask into a concrete task, deliver one real artifact, surface deeper capabilities contextually, and plant a retention hook such as a scheduled trigger.
  • Contextual capability surfacing: Introduces connectors, memory, subagents, and the marketplace only when the current task calls for them, never as a feature list.
  • Anti-pattern guardrails: Explicit rules against feature-dumping, leading with pricing, or ending a session at a paragraph of text instead of a real artifact.
  • Use Case: A new user messages "what can you do?" — the Skill guides the agent to ask about their work, co-author a concrete first task, deliver a finished report or deck, then offer a recurring scheduled run.

Quick Start

Ask the agent to onboard a new user who just sent a vague first message like "how does this work?" and guide them to one finished deliverable.

Frequently Asked Questions about kortix-onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a new user to an AI agent platform?

Onboard new users by solving one real task first rather than giving a feature tour. Ask what they do, sharpen their vague ask into a concrete deliverable, complete it end to end, then surface deeper capabilities only when the task calls for them.

What should a first session with an AI agent produce?

A first session should produce one tangible artifact such as a file, deployed page, sent message, or populated sheet. A finished deliverable demonstrates value far better than a paragraph of explanatory text.

When should this onboarding flow not be used?

Do not use it when the user arrives with a specific, well-formed task. In that case skip onboarding entirely and execute the task directly, since solving the problem is itself the best onboarding.

How do I introduce connectors and integrations to new users?

Introduce connectors only when the current task clearly needs one, such as when the user mentions email or a CRM. Mint a setup link in the same turn rather than sending users to a settings page or asking for credentials.

How do I turn a first AI session into repeat usage?

Offer a recurring angle once the first task is done, such as a scheduled trigger that reruns the work automatically and notifies the user. Frame it as saving effort, and set it up directly rather than pointing to settings.