Menu

Individual skill

portfolio-environment-analysis

0upvotes

Use for engineering portfolio environment tasks that require JSON answers from work items, mix targets, SLA policy, releases, milestones, blockers, dependencies, or the restricted SQL query endpoint. Covers portfolio mix reviews, SLA aging/breach audits, and release-readiness assessments.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/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
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

# Portfolio Environment Analysis

## Start Every Task

1. Read the user's prompt and any supplied answer template/schema. The template is the output contract; match its keys, ordering notes, constants, rounding, and "JSON only" requirements exactly.
2. Read the runtime access file for the environment base URL, token, and allowed endpoints. Use only those access details for network calls.
3. Fetch authoritative data from the environment. Prefer endpoint JSON for clarity; use `POST /api/query` with `{"sql": "..."}` when a scoped SQL query is simpler.
4. Treat `status`, `closed_at`, `duplicate_of`, `work_type`, `labels`, `title`, `team`, `product_area`, `release_id`, and `milestone_id` as authoritative. Ignore stale/export fields such as `mirror_status` and `legacy_category` unless the prompt explicitly asks to report that they were ignored.

Expected endpoint families:

- `/api/work-items`: work items with ids, dates, status, duplicate link, team, product area, release/milestone ids, owner, severity, priority, work type, labels, title, and stale mirror/export fields.
- `/api/mix-targets`: target mix rows with `scope_id`, quarter, product area/team group, and category percentages stored as decimals.
- `/api/sla-policy`: severity-to-days policy. Use it only when an item lacks an authoritative `due_at`.
Back to top