Individual skill

portfolio-review

Solve engineering portfolio review tasks (mix analysis, SLA aging, release readiness) against a shared REST API with work items, milestones, blockers, dependencies, mix targets, and SLA policy data. Use when the task requires classifying work items into portfolio categories, computing mix gaps, auditing SLA compliance, or assessing release readiness.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_024/fewshot/naive/fewshot_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
No
Observed behavior
Network or broad shell
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 Review Skill

## Overview

This skill solves engineering portfolio review tasks that query a shared REST API
and produce structured JSON answers. Three task families are covered: portfolio
mix analysis, SLA aging audits, and release readiness assessments.

The API is accessed at a base URL supplied in the task prompt (typically as
`<TASK_ENV_BASE_URL>` or similar token). Endpoint and credential details are
provided in an `environment_access.md` file staged alongside the task. The API
returns JSON; all data extraction uses `curl` piped to `jq`.

## Environment Setup