Individual skill
portfolio-work-auditor
Analyze engineering portfolio work-item datasets for portfolio mix, SLA aging, duplicate handling, and release readiness. Use when Codex must produce schema-constrained JSON answers from provided work-item, mix-target, SLA-policy, release, milestone, blocker, or dependency data while avoiding stale mirror/export fields.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_024/reflect-3/reflect-3_attempt_01/SKILL.md
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
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Portfolio Work Auditor
## Core Workflow
1. Read the prompt and the answer template before querying data. Treat the template as the output contract.
2. Load the authoritative task data made available by the user or runtime notes. Use structured parsing for JSON and SQL results.
3. Ignore stale mirror/export fields for business truth unless the prompt explicitly asks to report them. Prefer current work item fields such as `status`, `closed_at`, `duplicate_of`, `work_type`, `labels`, `title`, `release_id`, and `milestone_id`.
4. Build the analysis cohort first, then calculate metrics from that set. Do not calculate from story points unless the prompt explicitly asks for story-point weighting.
5. Sort and round exactly as requested by the template. Return only the requested JSON when the prompt says not to include prose.
## Portfolio Category Classification
Classify each primary work item into exactly one category.
