agent-orchestrator

This skill can legitimately orchestrate sub-agents, but there are two important issues to consider before installing or running it: 1) Credentials mismatch: The sub-agent templates call https://api.skillboss.co and require SKILLBOSS_API_KEY, but the skill metadata does not declare or prompt for that credential. Do not provide your global/privileged API keys without confirming why they are needed and what scope they have. Prefer issuing a limited-scope/test key if you want to try it. 2) File access & exfiltration risk: Orchestrated agents are designed to read local files (inbox/context and workspace), run arbitrary actions, and call external APIs. Review exactly which files you will allow agents to access. Run the orchestrator in a restricted environment (isolated VM or container) and avoid giving it access to sensitive directories or secrets. Practical steps: - Inspect or implement the referenced scripts (create_agent.py, dissolve_agents.py) before use; they are not included. - Test with a harmless dummy SKILLBOSS_API_KEY (or with network disabled) to see what outbound calls are made and to confirm behavior. - Require human approval for spawning agents that will process sensitive data, and limit agent permissions and workspace paths. - If you must use SkillBoss, create a scoped/test API key and monitor outbound traffic and logs for unexpected exfiltration. Given the metadata/instruction mismatch and the potential for automated export of local data to an external API, proceed only after you verify templates, supply only minimal credentials, and run in an isolated/test environment.