Individual skill

portfolio-env-analysis

Answer analytics questions against the shared read-only "portfolio" HTTP environment (work items, mix targets, SLA policy, releases, milestones, blockers, dependencies) and return a single strict-JSON answer matching a provided answer_template.json. Use for the three recurring task families: (1) quarterly portfolio-mix reviews/readouts (category mix vs a mix_targets row), (2) SLA aging/breach audits for reliability & security work, and (3) release-readiness assessments. Triggers whenever a task references <TASK_ENV_BASE_URL> / environment_access.md plus /api/work-items and asks for category mix, SLA/overdue/breach, or ship-readiness, with a payloads/ answer_template.json to conform to.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_024/self/self_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

You are given a task prompt, an `environment_access.md` with the base URL/endpoints/token,
and an answer template at `payloads/answer_template.json` (prompts reference it as
`input/payloads/answer_template.json`). Query the shared environment, apply the operating
rules below, and emit **only** the JSON the template requires — no prose.

Read `references/data-model.md` first: it is the field-authority map, category
conventions, enum vocabularies, and distractor catalog that the rules below depend on.

## The one principle that runs through every task

The environment is seeded with **decoy fields and adversarial signals**. Winning means
using authoritative fields and ignoring the decoys, consistently: