Menu

Individual skill

engineering-portfolio-env

0upvotes

Solve engineering portfolio environment tasks that ask Codex to inspect work items, mix targets, SLA policy, releases, milestones, blockers, or dependencies through the provided task environment and return exact JSON for portfolio mix, SLA aging, or release readiness analyses.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/deepagents/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 when the prompt points at the shared engineering portfolio environment and asks for JSON based on work items, mix targets, SLA policy, releases, milestones, blockers, or dependencies.

## Workflow

1. Read the task prompt and the supplied answer template/schema first. The template controls field names, constants, ordering, and precision.
2. Read the runtime access file for `base_url`, allowed endpoints, and any query token. Prefer the GET endpoints; use `POST /api/query` only when a token is actually supplied.
3. Load authoritative records from the environment:
   - `GET /api/work-items` -> `work_items`
   - `GET /api/work-items/{item_id}` -> `work_item`
   - `GET /api/mix-targets` -> `mix_targets`
   - `GET /api/sla-policy` -> `sla_policy`
   - `GET /api/releases` and `GET /api/releases/{release_id}` -> release metadata, and sometimes related milestones/blockers
Back to top