Menu

Individual skill

engineering-portfolio-env

0upvotes

Solve JSON audit tasks against the shared engineering portfolio task environment. Use for portfolio mix reviews, SLA aging and breach audits, release readiness assessments, milestone completion, blocker and dependency analysis, duplicate/cancelled exclusions, stale mirror/export field handling, and exact answer_template.json output from work-items, mix-targets, SLA policy, releases, milestones, blockers, dependencies, or restricted query endpoints.

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

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 to solve tasks that ask for a JSON answer from the shared engineering portfolio environment. The recurring job is to query the environment, separate authoritative records from stale mirrors/distractors, compute the requested metrics, and emit exactly the schema in `input/payloads/answer_template.json`.

## First Pass

1. Read the user prompt and `input/payloads/answer_template.json`.
2. Read the task's runtime access file if supplied. Use its base URL when the prompt contains `<TASK_ENV_BASE_URL>`.
3. Fetch only the collections needed for the answer. Typical endpoints are:
   - `GET /api/work-items`
   - `GET /api/work-items/{item_id}`
   - `GET /api/mix-targets`
   - `GET /api/sla-policy`
   - `GET /api/releases`
Back to top