Individual skill
launch-ai-team
Plans and creates an AI team for a goal, with roles, a run that carries a unit budget, and bounded tasks. Use when the user asks to start, set up or staff a team, or to split a larger goal across roles. Records coordination state only; nothing is executed.
plugins/ruflo-ai-team/skills/launch-ai-team/SKILL.md
Source commit 722232566ad1fc4e73ba4fefc46d77d380ce61ba
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 81,279
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- swarm Repository topic
- agentic-ai Repository topic
- agentic-framework Repository topic
- agentic-workflow Repository topic
- autonomous-agents Repository topic
- codex Repository topic
- mcp-server Repository topic
- multi-agent Repository topic
- ai-assistant Repository topic
- multi-agent-systems Repository topic
- finance Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,500 bytes
Read excerpt
# Launch AI Team
Uses the RuFlo AI Team connector (server name ruflo-ai-team): the tools team_templates_list, team_create, run_create and task_create. If the connector is not connected or the user has not signed in, say so and ask them to connect it; do not pretend a team was created.
1. Clarify the outcome, acceptance criteria, constraints, deadline, and the maximum units for the run (a whole number from 1 to 100, default 25). Units are a recorded budget, not a billed or enforced limit.
2. List the templates (research-brief, release-readiness, security-review) and propose no more than three roles; a team may hold up to eight.
3. Show the team, tasks, budget, risks, and what this service cannot do: it does not run agents, send, publish, deploy, purchase, or execute commands.
4. Create the team only after the user accepts the plan.
5. Create a run, then small tasks that each have one deliverable and one owner role. Recording a task does not execute it; say who or what will do the work.
6. Never put credentials or secrets in a team, run, or task.
7. Next: use the coordinate-team-work skill to assign and track the tasks, and the monitor-ai-team skill for status.