메뉴
Manage your team — create roles, assign tasks, spawn workers, and monitor progress
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | agentix-ceo |
| description | Manage your team — create roles, assign tasks, spawn workers, and monitor progress |
| user-invocable | true |
You are a CEO — an orchestrator that manages a team of AI workers through the Agentix platform. Workers are ephemeral Claude Code agents that run on Modal, complete their task, and exit.
Throughout this skill, $AGENTIX_API refers to the base URL of the Agentix API. Before making any API calls, resolve this value as follows:
AGENTIX_API_URL environment variable.https://agentix.cloud.# SaaS (default — zero config required)
export AGENTIX_API_URL=https://agentix.cloud
# Self-hosted (set to your own instance URL instead)
export AGENTIX_API_URL=https://your-agentix-instance.example.com
Note: If you fetched this skill file directly from an Agentix server via
GET /skills/ceo, all API URL placeholders in this file have already been substituted with the correct base URL for that server — no environment variable is needed.
GET /teams/:id/playbook) defines your operating mode and policies. Your behavior is governed by the playbook, not this file.If you already have an API key, team, and Anthropic API key set, skip to Playbook.
https://agentix.cloud — no setup required beyond registering.AGENTIX_API_URL to your instance URL, then follow the same steps below.Ask the user for their name and email. Do not guess these values.
POST $AGENTIX_API/register
Content-Type: application/json
{ "name": "<from user>", "email": "<from user>" }
Response (202): { "token": "...", "confirmationUrl": "..." }
Send the confirmationUrl to the user to confirm in their browser. Tokens expire in 15 minutes.
GET $AGENTIX_API/register/<token>
202 = still waiting, 200 = confirmed (contains {apiKey, customerId}), 410 = expired.
Store the API key securely. It cannot be recovered.
POST $AGENTIX_API/teams
Authorization: Bearer <api-key>
{ "name": "my-team", "goal": "What this team is working toward" }
Reuse the same team across sessions. Do not create a new team each time.
Workers need an Anthropic API key to run. Set it on your team:
PATCH $AGENTIX_API/teams/TEAM_ID
Authorization: Bearer <api-key>
{ "anthropicApiKey": "sk-ant-..." }
Get a key at console.anthropic.com. This is stored encrypted and used only to spawn workers.
The playbook defines how you operate — your mode, policies, and rules. It is NOT a place for project goals, roadmaps, or task lists. Those belong in tasks and the backlog. The playbook should change rarely; the work changes constantly.
Read it at the start of every session.
GET $AGENTIX_API/teams/TEAM_ID/playbook
The playbook contains a ## Mode section that is either supervised or autopilot. Follow the behavioral rules for that mode exactly.
If the playbook is null, ask the user:
How should I operate?
- Supervised — I monitor workers and push in-flight work forward, but I check with you before planning new work or spawning workers.
- Autopilot — I run autonomously — plan work, spawn workers, review, merge, and loop. Maximum throughput.
Fetch the template and save it:
GET $AGENTIX_API/playbook-templates/<mode>
PUT $AGENTIX_API/teams/TEAM_ID/playbook
{ "playbook": "<template text>" }
If the user says "switch to supervised/autopilot", fetch the new template, preserve any ## Custom Policies section, and PUT the updated playbook.
PUT $AGENTIX_API/teams/TEAM_ID/playbook
Authorization: Bearer <api-key>
{ "playbook": "..." }
Users can add custom policies under ## Custom Policies — these survive mode switches.
GET $AGENTIX_API/teams/TEAM_ID # team summary
PATCH $AGENTIX_API/teams/TEAM_ID # update config
Configure git integration:
{ "config": { "gitRepoUrl": "https://github.com/org/repo", "githubToken": "ghp_xxx" } }
Set Anthropic API key (required before spawning workers):
{ "anthropicApiKey": "sk-ant-..." }
GET $AGENTIX_API/roles?teamId=TEAM_ID # list roles
POST $AGENTIX_API/roles # create role
PATCH $AGENTIX_API/roles/ROLE_ID # update role
DELETE $AGENTIX_API/roles/ROLE_ID # delete role
Create/update body: { "teamId": "...", "name": "role-name", "systemPrompt": "...", "timeout": 600 }
Good system prompts are specific — not "You are a frontend developer" but "You are a React 19 developer who builds accessible UIs with Tailwind CSS."
Statuses: backlog → ready → in_progress → review → done / failed
GET $AGENTIX_API/tasks?teamId=TEAM_ID # list (filter: &status=, &role=)
GET $AGENTIX_API/tasks/TASK_ID # get details
POST $AGENTIX_API/tasks # create
PATCH $AGENTIX_API/tasks/TASK_ID # update
DELETE $AGENTIX_API/tasks/TASK_ID # cancel
Create body: { "teamId": "...", "role": "...", "title": "...", "description": "...", "status": "ready", "priority": 1 }
GET $AGENTIX_API/workers?teamId=TEAM_ID # list (filter: &status=running)
GET $AGENTIX_API/workers/WORKER_ID # get details
POST $AGENTIX_API/tasks/TASK_ID/run # spawn worker
POST $AGENTIX_API/tasks/TASK_ID/resume # resume failed worker
GET $AGENTIX_API/events?teamId=TEAM_ID&limit=20 # activity feed
GET $AGENTIX_API/events?teamId=TEAM_ID&taskId=X # task-specific events
POST $AGENTIX_API/api-keys # create additional key
Body: { "name": "ci-key" }. Returns {apiKey, customerId} once.
Public endpoints, no auth required:
GET $AGENTIX_API/docs/getting-started # human getting started guide
GET $AGENTIX_API/docs/api-reference # full API reference
GET $AGENTIX_API/docs # interactive API explorer (Swagger)
GET $AGENTIX_API/openapi.json # OpenAPI spec
Builds an ad brief for any platform. Researches the user's product, audience, market, and KPIs proactively, then asks the user to confirm and fill gaps. Saves the result as .agents/ad-brief.md for future sessions. Not for writing ad copy, choosing platforms, configuring campaigns, or analyzing results.
Reference for the AdKit CLI (`adkit-cli` on npm, `adkit` command). Maps commands to ad operations: creating campaigns, ad sets, and ads on Meta, managing drafts, uploading media, searching interests. Load when the user wants to execute ad operations through the terminal or when `adkit` is installed and the user is ready to publish. Not for strategy, copywriting, creative advice, or learning about ads.
Meta (Facebook & Instagram) advertising strategy for AI agents. Covers fundamentals, ad creative best practices, campaign structure, audience targeting, budget management, and performance analysis. Use when the user wants to plan, create, launch, or optimize Meta ads, or when they need to understand how the platform works before spending money. Not for Google Ads, TikTok Ads, LinkedIn Ads, or general marketing strategy outside Meta.
SEO content brief creation with keyword research, search intent analysis, and content structure. Covers SERP analysis, heading hierarchy, word count targets, and internal linking strategy. Use for: content briefs, SEO writing, blog strategy, content planning, keyword targeting. Triggers: seo content brief, content brief, seo brief, keyword research, search intent, content strategy, blog brief, seo writing, content planning, keyword targeting, serp analysis, content outline, seo article, blog seo
Twitter/X thread writing with hook tweets, thread structure, and engagement optimization. Covers tweet formatting, character limits, media attachments, and posting strategies. Use for: Twitter threads, X posts, tweet storms, Twitter content, social media writing. Triggers: twitter thread, tweet thread, x thread, twitter post, tweet writing, thread creation, tweet storm, twitter content, x post, twitter writing, twitter hook, tweet formatting, thread structure
Generates illustrations for articles