Individual skill

engineering-portfolio-env

Solve engineering portfolio task-environment audits that require exact JSON answers from work-item APIs, including portfolio mix, SLA aging and breach-rate analysis, duplicate handling, release readiness, milestones, blockers, dependencies, and ship decisions. Use when prompts mention the task environment base URL placeholder, mix targets, SLA policy, releases, milestones, work items, blockers, or dependencies.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/deepagents/fewshot_attempt_03/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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
engineering Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 6,433 bytes
SKILL.mdcore · 6,433 bytes
SKILL.mdcore · 6,433 bytes
references/calculation-rules.mddoc · 5,068 bytes
scripts/env_fetch.pyruns · 7,041 bytes

Read excerpt


# Engineering Portfolio Environment

Use this skill to solve JSON-only audit tasks over the shared engineering portfolio environment. Always treat the prompt and its `input/payloads/answer_template.json` as the output contract.

## First Pass

1. Read the prompt, the answer template, and the runtime access notes.
2. Resolve the base URL and fetch the necessary API data. If endpoint filters are unreliable, fetch the allowed endpoint and filter locally.
3. Normalize records before calculating: use `status`, `closed_at`, `created_at`, `due_at`, `duplicate_of`, `team`, `product_area`, `work_type`, `labels`, `severity`, `owner`, `release_id`, and `milestone_id` as the primary fields.
4. Ignore stale mirror/export fields such as `mirror_status` for status, completion, and inclusion. Do not let `legacy_category` override current work-type, label, and title evidence.
5. Return exactly one JSON object matching the template. Preserve required keys, requested ordering, numeric precision, and enum spellings. Do not add prose.

For detailed calculation rules, read [references/calculation-rules.md](references/calculation-rules.md).