Skillv3.3.1

ClawScan security

FIS Architecture · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 7, 2026, 9:24 AM

Verdict: benign
Confidence: medium
Model: gpt-5-mini
Summary: The skill's code and instructions are consistent with its stated purpose (multi-agent task orchestration using JSON tickets, Discord threads, and the OpenClaw sessions API), but it reads/writes local OpenClaw workspace/ticket directories and can spawn background sub-agents, so review generated commands and workspace paths before use.
Guidance: This skill appears to do what it says (create/manage JSON tickets, generate Discord thread templates, and coordinate sub-agents). Before installing or running it: 1) Review the repository locally to confirm you trust the hardcoded Discord role and forum IDs and the printed A2A/sessions commands. 2) Note it will create/read ticket files under your OpenClaw home (default ~/.openclaw/fis-hub) and scan workspace output/deliverables directories — consider setting FIS_HUB_PATH or OPENCLAW_HOME to an isolated location if you don't want it enumerating your existing workspaces. 3) When executing generated sessions_send or sessions_spawn commands, inspect them first — spawning background sub-agents can increase the blast radius of any subsequent actions. 4) Ensure the Discord bot permissions it requests are intentionally granted to the correct bot accounts. If you need higher assurance, open the truncated generate_report/archive code paths (not fully shown) to confirm they don't read file contents or transmit more than file metadata and small summaries.

Review Dimensions

Purpose & Capability: okThe name/description (FIS multi-agent orchestration) matches the actual behavior: creating JSON tickets, generating thread templates, invoking sessions_send/sessions_spawn semantics, and coordinating Workers. Hardcoded Discord role IDs and forum channel mappings are consistent with a Discord-based coordination workflow.
Instruction Scope: noteSKILL.md and the scripts instruct the agent to create/modify tickets under a shared hub, create Forum threads via the platform 'discord' tool, and call sessions_send/sessions_spawn. The code also attempts to detect the current session via OPENCLAW_SESSION_KEY or by calling the 'openclaw' CLI, and the lifecycle code scans workspace output/deliverables directories for files. These actions are expected for a coordination tool but do access local filesystem metadata and invoke platform CLI/tools — review outputs before broadcasting.
Install Mechanism: okNo install spec; the skill is instruction-plus-scripts only. It requires Python 3.8+ (standard library only) and uses existing runtime tools (openclaw CLI, platform-provided 'discord' and session APIs). Nothing is downloaded from external URLs or written by an installer.
Credentials: noteThe skill does not declare required env vars, but the code will read optional variables if present (OPENCLAW_SESSION_KEY, OPENCLAW_HOME, FIS_HUB_PATH). It also writes and reads files under the derived OpenClaw home and workspaces (e.g., ~/.openclaw/fis-hub/tickets and workspace-* directories). These accesses are proportionate to ticket/deliverable tracking, but you should be aware it will enumerate files in workspace output/deliverables and include path/metadata in tickets.
Persistence & Privilege: okalways is false. The skill uses platform session APIs (sessions_send, sessions_spawn) to notify and spawn sub-agents; this is expected for a coordination skill. It does create and manage its own ticket files under the OpenClaw workspace, but it does not change other skills' configs or request elevated system privileges.