Menu

Individual skill

engineering-portfolio-env

Analyze the shared engineering portfolio task environment and return exact JSON for portfolio mix reviews, SLA aging audits, and release-readiness assessments. Use when a prompt references TASK_ENV_BASE_URL, work items, mix targets, SLA policy, releases, milestones, blockers, dependencies, or asks to distinguish primary work from duplicates/cancelled/stale mirror records.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/codex/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 Environment

Use this skill to solve JSON-only task-environment audits. The common work is to fetch the allowed API data, identify the primary population, compute metrics, and then shape the result to the task's payload template.

## Workflow

1. Read the user prompt, `environment_access.md`, and every file under `input/payloads/`.
2. Extract the task family:
   - Portfolio mix: scope id, quarter, teams, product area(s), and mix target.
   - SLA aging: teams, as-of date, recent closed window, and requested SLA categories.
   - Release readiness: release id and required release metrics.
3. Fetch only the required API endpoints from the base URL in `environment_access.md`. Prefer `GET` endpoints; use `POST /api/query` only for filtering when useful.
4. Use authoritative fields on records: `status`, `closed_at`, `duplicate_of`, `work_type`, `labels`, `title`, `team`, `product_area`, `release_id`, `milestone_id`, `due_at`, `severity`, `priority`, and `owner`.
5. Ignore stale mirror/export fields for truth: do not decide from `mirror_status` or `legacy_category`.