Skip to main content
This quickstart takes you from the selected Project to one completed AI Workforce run. You do not need to connect an external app for the first test.

​
Before You Start

You need:
  • A SketricGen account
  • Access to a Teamspace and Project
  • Enough Project credits for a short test run
  • A simple task you can verify yourself
If you want personalized recommendations first, complete Adaptive Onboarding. You can also skip it and start directly in Agent Space.

​
1. Open Agent Space

Select AI Workforce → Agent Space. Confirm the Teamspace and Project shown in the switcher. Agent Space showing the selected Project and available agents

​
2. Create an Agent

Select Create new agent. Choose a suitable template or begin with a simple agent. The screenshots in this quickstart use a Blog Writer and SEO workflow as an example of an internal AI Workforce. It combines a main content-planning agent, research tools, a specialist SEO sub-agent, and workspace files. You can follow the same steps with another internal template. For the first test, use one clear responsibility such as:
  • Summarize a document
  • Research a topic and return sources
  • Turn notes into a structured brief
  • Answer questions from a Knowledge Base
Avoid a multi-agent workflow until one main agent works correctly.

​
3. Configure Agent Build

Open Manage Agent Build and configure:
  1. A descriptive agent name
  2. Instructions explaining the result it owns
  3. A model appropriate for the task
  4. Only the tools or Knowledge Base needed for the test
Blog Writer AI Workforce configuration with content strategy instructions, model, tools, and a specialist SEO sub-agent Save the draft before running it.

​
4. Run a Test

Select Run, then New Chat. Enter a realistic prompt with enough detail to judge the result. Playground showing a completed Blog Writer test with conversation history and Project and agent file workspaces Do not test with “hello” alone. A useful test prompt should require the instructions or tool you configured.

​
5. Review the Result

Check:
  • Did the agent follow the requested format?
  • Did it use the correct tool or Knowledge Base?
  • Did it delegate only when needed?
  • Did it create the expected file or artifact?
  • Did it request human input before an uncertain or consequential step?
  • Does the trace explain what happened?
Change one part of the Agent Build at a time, then repeat the same prompt in a new conversation.

​
6. Return to Agent Space

Return to Agent Space and open the agent. You should see its configuration summary, recent activity, internal team, schedules, and any request needing attention. Your first success is complete when:
  • The agent exists in the correct Project.
  • A completed conversation appears in Playground history.
  • The output can be verified against your request.
  • You can explain the result from the trace or visible activity.

​
Next Steps