Individual skill
portfolio-environment-analyst
Analyze the shared engineering portfolio task environment and produce strict JSON for portfolio-mix, SLA-aging, duplicate-cluster, hotspot, and release-readiness assessments. Use when a task references work items, mix targets, SLA policy, releases, milestones, blockers, dependencies, restricted SQL, or task environment base URLs.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_024/fewshot/deepagents/fewshot_attempt_02/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- engineering Derived category
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,920 bytesSKILL.mdcore · 7,920 bytesscripts/fetch_snapshot.pyruns · 2,293 bytes
Read excerpt
# Portfolio Environment Analyst
## Workflow
1. Read the user prompt and `input/payloads/answer_template.json` before querying. Treat the template as the output contract: preserve required keys, enum spellings, order notes, precision, nullability, and "JSON only" requirements.
2. Read `environment_access.md` for the base URL and allowed endpoints. Prefer REST endpoints. Use `POST /api/query` only when a valid query token is supplied; pass it as `X-Env-Token` and do not guess or brute-force tokens.
3. Fetch the needed data. For a reproducible local snapshot, run this from the directory containing this `SKILL.md`:
```bash
python scripts/fetch_snapshot.py --base-url "$TASK_ENV_BASE_URL" --out /tmp/portfolio_snapshot.json
```
4. Build all metrics from authoritative fields on records and first-class endpoint data. Do not trust stale mirrors: ignore `mirror_status` for state, ignore `legacy_category` for portfolio category, and ignore release mirror/export fields when release, milestone, blocker, and dependency endpoints exist.
5. Emit only the JSON object requested by the template. Do not add prose, comments, or extra keys.