1.2.0

Structured triage and handoff for customer support ticket queues.

Security Scan

The skill claims to implement structured support-queue triage, but its metadata and runtime instructions are inconsistent (missing declared CLI dependencies and contains mismatched files), so proceed cautiously.

Purpose & Capability

The SKILL.md describes a 'support-queue-operations' skill that expects to run CLI commands like `support` and `workflow`, but the registry metadata's top-level Name is '1.2.0' (looks like a version placed in the name field) and the skill has no declared required binaries or install steps. That mismatch means the package does not declare the runtime capabilities it actually needs.

Instruction Scope

Runtime instructions explicitly call external commands (`support queue`, `support classify`, `support handoff`, `workflow checklist`, `workflow report`) and reference local templates. The skill does not document or declare the required CLIs or how those commands should be provided, which is a scope/operational gap. The templates and small scripts themselves are benign-looking, but one script's healthcheck echoes an unrelated identifier ('pipiwu-benchmark-beta-skill'), indicating possible copy‑paste or packaging errors.

Install Mechanism

There is no install spec (instruction-only plus a few tiny scripts/templates). This lowers installation risk because nothing is downloaded or extracted at install time, but it also means the skill relies on external CLIs being present without declaring them.

Credentials

The skill requests no environment variables, credentials, or config paths, which is proportionate for a guidance-style skill. However, because the instructions call external CLI tools, those tools (if installed) could themselves require credentials—this skill does not document that relationship.

Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous invocation allowed. It does not request elevated or persistent system privileges and does not modify other skills or system config.

What to consider before installing

This skill is plausible for support triage, but there are definite inconsistencies you should resolve before trusting it. Actions to consider: (1) Confirm the skill's publisher/source (metadata shows no homepage and an unknown owner ID). (2) Verify which command-line tools the skill expects (the SKILL.md references `support` and `workflow`) and only install/run this skill in an environment where those tools are intentionally provided. (3) Inspect or run the included scripts/templates in a sandbox—note the healthcheck script prints an unrelated identifier ('pipiwu-benchmark-beta-skill'), which suggests a packaging mistake. (4) Ask the publisher to correct the metadata (name/version mismatch) and to declare required binaries or an install procedure. (5) Do not provide secrets or system-level access on the basis of this skill until these inconsistencies are clarified.

Support Queue Operations

Use when backlog rises and you need repeatable queue cleanup and prioritization.

Inputs to Gather

• Primary target (service, team, or dataset)
• Current impact and urgency
• Assigned owner and deadline

Core Commands

• support queue --team <team> --priority high
• support classify --ticket <id> --reason <category>
• support handoff --ticket <id> --to <owner>
• workflow checklist --from templates/checklist.md
• workflow report --from templates/report.md

Operating Notes

• Prefer explicit owner assignment before action.
• Keep timeline notes concise and timestamped.
• Save output artifacts for audit and handoff.
• This version adds a structured report template for post-task summaries.

Version marker: support-queue-operations 1.2.0