Individual skill

engineering-portfolio-audits

Derive strict JSON answers from the shared engineering portfolio environment for portfolio-mix reviews, SLA aging audits, and release-readiness assessments. Use when prompts mention work items, mix targets, SLA policy, releases, milestones, blockers, dependencies, duplicate or cancelled records, stale mirror fields, count-based portfolio categories, breach rates, readiness scores, or ship decisions.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_024/self/self_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: Yes
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 · 10,459 bytes

Read excerpt


# Engineering Portfolio Audits

## Start Here

1. Read the user prompt, `environment_access.md`, and the requested answer template before querying data.
2. Use only the base URL, endpoints, and query token listed in `environment_access.md`. Prefer the REST endpoints; use `POST /api/query` with the supplied token only when endpoint joins are insufficient.
3. Load only the datasets needed for the prompt: work items, mix targets, SLA policy, releases, milestones, blockers, and dependencies.
4. Treat the answer template as binding. Preserve exact keys, enum spellings, required ordering, and numeric precision. Do not add prose when the prompt asks for JSON only.

Endpoint list responses are wrapped in top-level keys such as `work_items`, `mix_targets`, `sla_policy`, `releases`, `milestones`, `dependencies`, and `blockers`; unwrap those before filtering.

## Authoritative Fields

Use authoritative work item fields for truth: