Menu

Individual skill

portfolio-environment-analysis

0upvotes

Solve engineering portfolio analysis tasks against the shared task environment, including portfolio mix reviews, SLA aging audits, and release-readiness assessments. Use when prompts mention work items, mix targets, SLA policy, releases, milestones, blockers, dependencies, duplicate/cancelled records, stale mirror fields, or JSON answers shaped by an answer_template.json payload.

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

# Portfolio Environment Analysis

Use this skill to produce JSON answers from the read-only portfolio task environment.

## Workflow

1. Read the user prompt and any `input/payloads/answer_template.json` before querying data.
2. Read the runtime access file for the base URL, token, and allowed endpoints. Do not call judge endpoints.
3. Prefer the authoritative fields in the environment records:
   - Work item truth: `status`, `closed_at`, `created_at`, `due_at`, `duplicate_of`, `work_type`, `labels`, `title`, `team`, `product_area`, `owner`, `severity`, `priority`, `release_id`, `milestone_id`.
   - Ignore stale mirror/export fields such as `mirror_status` and `legacy_category` when deciding status or portfolio category.
4. Use [scripts/portfolio_tool.py](scripts/portfolio_tool.py) to fetch the allowed API data and compute a reusable summary, then adapt that summary to the exact answer template.
5. For detailed rules and edge cases, read [references/rules.md](references/rules.md).
Back to top