1.2.0
ReviewAudited by ClawScan on May 1, 2026.
Overview
This instruction-only support queue skill is purpose-aligned and shows no malicious behavior, but users should confirm ticket-changing actions and note a minor helper-script naming mismatch.
This appears safe to install as an instruction-only support workflow. Before using it, make sure any ticket-classification or handoff command is explicitly approved and scoped to the intended queue, ticket, and owner, and avoid putting sensitive customer details into saved reports unless they belong in your approved support system.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If run on the wrong ticket or team, the agent could misroute or misclassify customer support work.
These documented commands can change ticket classification or ownership. That is aligned with the stated support-queue purpose, but it affects operational business records and should be scoped by the user.
`support classify --ticket <id> --reason <category>` `support handoff --ticket <id> --to <owner>`
Confirm the team, ticket IDs, classification reason, and receiving owner before running any ticket-changing command.
The mismatch could make it harder to verify that all files belong to the intended package.
The healthcheck script prints a name unrelated to the support-queue skill. The script only echoes text, so this is a packaging/provenance consistency note rather than evidence of malicious behavior.
echo "ok: pipiwu-benchmark-beta-skill 1.2.0"
Verify the package identity before installation and consider asking the publisher to correct the healthcheck label.
Support summaries or audit files could retain sensitive ticket details if the user includes them.
The skill encourages creating persistent notes and handoff artifacts. This is appropriate for support operations, but such artifacts may include customer or ticket information.
Keep timeline notes concise and timestamped. Save output artifacts for audit and handoff.
Store outputs only in approved locations, avoid unnecessary customer details, and review handoff artifacts before sharing.