📝 Add Pixee Analysis Skill

[gilday]

The pixee CLI 0.13.0 release introduced the pixee analysis top-level subcommand with only view; 0.15.0 added list with six filter flags; 0.16.0 rounded out the CRUD shape with pixee analysis delete. The audit-skills workflow caught the gap: no skills/pixee-*/SKILL.md claimed cliHelp: "pixee analysis --help", so an agent asked to enumerate analyses, poll one to completion, follow the analysis HAL link from a finding's representative result, or clean up a bad analysis run was guessing.

This PR adds skills/pixee-analysis/SKILL.md covering all three verbs as they exist on 0.16.0. The PREREQUISITES blockquote names pixee-shared and pixee-auth, plus cross-references to pixee-scan (the analyze verb produces the analysis UUID), pixee-finding (every representative result's _links.analysis.href points back here), and pixee-repo (the --repo resolution protocol used by list).

## pixee analysis list documents the six filter flags — --repo (repeatable), --branch, --state (repeatable; queued/in-progress/skipped/completed/failed), --tool (repeatable), --updated-after, and --updated-before — and the text-mode column set (id, state, branch, sha, updated_at). ## pixee analysis view covers the headline text-mode fields and the full HAL representation under --json, with a nested subsection for --watch documenting the poll-and-narrate loop, terminal states, the exit-code-by-state contract, and the 5-second --interval default. ## pixee analysis delete documents the destructive verb, the server-side cascade to findings and patches, and the absence of any client-side confirmation prompt — matching the voice in pixee-scan, pixee-repo, and pixee-workflow.

Seven runnable examples cover the bread-and-butter calls plus three load-bearing patterns: the start-then-watch chain that captures the analysis id from pixee scan analyze's stdout, the HAL walk that reads representative-results._links.analysis.href from pixee finding view --json and hands it to pixee api, and the cascading delete. Best-practices bullets capture filter-aggressively discipline on list, when to prefer the analysis UUID from the start call over a list lookup, when to reach for --watch, --interval sizing, the "don't hand-roll polling" guidance, the HAL preference, how analysis UUIDs relate to the seven-day scan expiration, and the delete-cascade warning.

The picker description is verb-first and picker-safe at 116 chars: "List, view, and delete Pixee analyses with filters and optional polling until the analysis reaches a terminal state." The README bullet is placed between pixee-scan and pixee-finding to match the lifecycle order (scan → analysis → finding).

/close ISS-7253

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud