scopi:team

Coordinate inter-agent teams to generate production-ready design artifacts for Scopi Card News.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/HosungYou/scopi-cardnews --skill scopi-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scopi:team
Source: https://github.com/HosungYou/scopi-cardnews/tree/main/skills/team
Command: npx skills add https://github.com/HosungYou/scopi-cardnews --skill scopi-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent Teams reference — detailed inter-agent communication protocols and task architecture for coordinating design workflows within Scopi Card News production. It is auto-invoked by /scopi:generate when Agent Teams is available and is NOT invoked directly — /scopi:generate auto-detects and routes here.

Core Features & Use Cases

  • Phase-based orchestration: organize work in clear phases (content, design, ethics, render)
  • Direct inter-agent messaging & veto: enable real-time debates with escalation and resolution
  • Output artifacts: final slides.js, design specs, license checks, and final report
  • Config-driven teamwork: agents read their definitions and scopi.config.json to align on goals, roles, and rules

Quick Start

Initiate the Agent Teams workflow to coordinate the design tasks and render the final slides package.

Frequently Asked Questions about scopi:team

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

FAQPage Schema
How do I coordinate inter-agent teams for multi-phase design workflows?

Inter-agent team coordination is managed through phase-based orchestration, organizing work into content, design, ethics, and render phases with defined agent roles and dependency tracking to ensure structured workflow progression.

How does real-time messaging and veto protocol work between agents?

Real-time messaging enables direct inter-agent debates with escalation and resolution mechanisms, while veto protocols allow agents to reject outputs during ethics review or design phases before final render orchestration.

Can I generate production-ready design artifacts using a centralized team API?

Yes, the centralized team API orchestrates final render outputs, generating production-ready design artifacts including final slides.js, design specs, license checks, and a final report for content projects.

Do I need scopi.config.json to align agent roles and rules for content generation?

Yes, config-driven teamwork requires agents to read scopi.config.json and their individual definitions, ensuring all team members align on goals, roles, and rules before executing phase-based tasks.

What's the best way to automate copy, visuals, ethics review, and code rendering for card news?

The optimal approach uses multi-phase orchestration to sequentially process copy, visuals, ethics review, and code rendering, with automatic routing from the parent generate command to the agent teams workflow.

Why does the agent teams workflow get invoked indirectly during content generation?

The workflow is auto-invoked by the parent generate command when agent teams are available, meaning it auto-detects and routes to the inter-agent coordination protocol rather than requiring direct invocation.