Menu

Individual skill

engineering-portfolio-env

0upvotes

Solve JSON-only engineering portfolio environment tasks that use a shared task API for work items, mix targets, SLA policy, releases, milestones, blockers, and dependencies. Use for portfolio mix reviews, SLA aging audits, release readiness decisions, duplicate/distractor exclusion, canonical category/status resolution, strict answer_template.json outputs, and any prompt mentioning <TASK_ENV_BASE_URL> with these engineering portfolio endpoints.

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

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 for tasks that ask you to inspect the shared engineering portfolio environment and return a single JSON answer.

## First Steps

1. Read the user prompt completely, then read every file in `input/payloads/`, especially `answer_template.json`.
2. Read the runtime access file for the base URL, allowed endpoints, and any query token. Prefer the documented GET endpoints; use `POST /api/query` only when the runtime access notes provide a valid token and it is genuinely useful.
3. Read [references/domain-rules.md](references/domain-rules.md) before calculating. It contains the reusable status, category, portfolio-mix, SLA, and release-readiness rules.
4. Optionally snapshot the environment with:

```bash
python3 skill/scripts/fetch_env_snapshot.py --base-url "$TASK_ENV_BASE_URL" --out /tmp/portfolio_env_snapshot.json
```
Back to top