Individual skill

engineering-portfolio-review

Solve engineering portfolio environment review tasks that ask for JSON answers from shared work-item APIs, including portfolio mix, SLA aging, release readiness, blockers, dependencies, duplicate handling, and stale mirror field avoidance. Use this skill whenever a task mentions work items, mix targets, SLA policy, release readiness, blockers, dependencies, or a shared task environment with an answer_template.json.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/cc/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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

# Engineering Portfolio Review

Use this skill to produce schema-exact JSON answers for engineering portfolio tasks backed by the shared REST environment.

## Workflow

1. Read the user prompt, `input/payloads/answer_template.json`, and the runtime access file supplied with the task.
2. Fetch authoritative environment data from the allowed endpoints. Prefer the helper script in `scripts/env_review.py` for repeatable calculations.
3. Build the answer to match the template exactly: keep only required fields, preserve enum strings, obey requested ordering, and return JSON only.
4. Treat `status`, `work_type`, `labels`, `title`, `closed_at`, `due_at`, `duplicate_of`, `release_id`, and `milestone_id` as authoritative. Use `mirror_status` and `legacy_category` only as stale/conflict evidence, not as truth.

## Helper Script

Run the helper from the task workspace, passing the task environment access file or base URL:
Back to top