Menu

Individual skill

engineering-portfolio-environment

Solve engineering portfolio environment tasks that require producing strict JSON from read-only work item data, mix targets, SLA policy, releases, milestones, blockers, dependencies, or the restricted SQL endpoint. Use for portfolio-mix reviews, SLA aging audits, release-readiness assessments, duplicate/cancelled exclusion reports, and similar tasks that reference TASK_ENV_BASE_URL, environment_access.md, or input/payloads/answer_template.json.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/naive/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
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

## Core Workflow

1. Read the user prompt, `environment_access.md`, and the answer template before querying data.
2. Use the base URL and token exactly as supplied by `environment_access.md`; never call `/api/judge`.
3. Fetch authoritative records through the business endpoints or `POST /api/query`.
4. Build the answer from source-of-truth fields, then validate it against the template shape.
5. Return only the requested JSON when the prompt says not to include prose.

Useful endpoint set:

- `GET /api/work-items`
- `GET /api/work-items/{item_id}`