multi-agent-workshop
What this skill does
A multi-agent workshop tool for organizing and facilitating collaborative discussions among multiple agents in a structured, phased approach. It is designed for use in planning, requirement gathering,
github/leoyeai - Dependency on External API Key - 2.1k stars
Threat analysis
Skill info
pkg:github/LeoYeAI/openclaw-master-skills@e5199b5?skill=multi-agent-workshopAssessments (2)
Dependency on External API Key
Dependency on External API Key via local-llm-review
scripts/jd_to_role_card.py
The script depends on the SERPER_API_KEY, which is read from the user's ~/.openclaw/.env file. This could be a risk if the .env file is not properly secured or if the API key is exposed.Potential Misuse of Orchestrator Script
Potential Misuse of Orchestrator Script via local-llm-review
scripts/orchestrator.py
The orchestrator script provides functionality to manipulate the state of a workshop session, including setting fields, advancing phases, and importing sessions. If misused, this could lead to unintenBadge
Add the Anomity scan badge for multi-agent-workshop to your README.
How Anomity governs this at runtime
Scan-time vetting tells you what a skill says it will do. Anomity's Endpoint Sensor sees what agents actually do: it discovers skills alongside every other AI artifact on the endpoint, and runtime governance can allow, deny, or log the tool calls a skill triggers. Policy violations route to your SIEM, Slack, email, or Jira, backed by a queryable 90-day audit trail.
Book a 30-minute demo to see your own skill inventory.
Methodology and disputes
Every skill is assessed by the Anomity Skill Intelligence engine against its public source; findings indicate risk patterns, not confirmed exploitation. Maintainer of multi-agent-workshop? Report an issue or request a rescan.
