Menu

Individual skill

portfolio-work-review

Compute portfolio-mix, SLA-aging, and release-readiness reviews from a shared work-item environment. Use when a task asks for a closed-work portfolio mix vs target, an SLA breach/aging audit, or a release ship-readiness assessment, and points at a shared environment with work items, mix targets, SLA policy, releases, milestones, dependencies, and blockers.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_024/reflect-3/reflect-3_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Portfolio Work Review

This skill produces a single JSON answer for three kinds of engineering-portfolio
review tasks against a shared work-item environment:

1. **Portfolio mix** — closed work in a scope, classified into portfolio
   categories, compared to a target mix, with a rebalance recommendation.
2. **SLA aging / breach audit** — reliability & security work tracked against
   SLA due dates, with overdue items, aging, duplicate clusters, and breach rate.
3. **Release readiness** — a release's milestone completion, gating work,
   blockers, dependency chains, and a ship decision.

The environment, the available endpoints, and any access token are supplied
separately at solve time (e.g. an `environment_access.md` file). Read that file