Tirosman Demo Skill

Drive the TirOSMAN autonomous multi-agent demo (5 projects × 150 tasks, Jira-like lifecycle, QA approval) from any MCP-aware client.

The skill appears to implement a TirOSMAN demo controller, but the manifest omitted environment variables the runtime expects. Before installing: 1) Confirm the MCP endpoint (mcp.url) and whether a TIROSMAN_MCP_API_KEY is required — ask the publisher to add it to the metadata or refuse until corrected. 2) Never point TIROSMAN_DEMO_WEBHOOK_URL at an untrusted external endpoint — webhook events contain task transitions and could leak data. 3) Run the demo only against a non-production company_id and an isolated/local MCP/Postgres instance so demo_start/demo_reset won't touch real data. 4) If you need higher assurance, request the publisher to publish a homepage/source and to declare required env vars and a security/privacy note. The current mismatch between docs and manifest is a red flag — treat it as suspicious until clarified.

Type: OpenClaw Skill Name: tirosman-demo Version: 0.2.0 The skill bundle provides a legitimate interface for managing a multi-agent demo system (TirOSMAN) via the Model Context Protocol (MCP). It defines tools for task lifecycle management, such as 'demo_start', 'demo_run', and 'demo_status', and uses standard environment variables for authentication (TIROSMAN_MCP_API_KEY). No indicators of malicious intent, data exfiltration, or suspicious execution logic were found in the SKILL.md or metadata.