Menu

Individual skill

engineering-portfolio-env-solver

0upvotes

Use this skill for strict JSON tasks over a shared engineering portfolio environment. Use it whenever the prompt mentions TASK_ENV_BASE_URL, work items, portfolio mix targets, SLA aging or breach rates, release readiness or ship decisions, blockers, dependencies, duplicate clusters, stale mirror fields, or authoritative environment data.

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

# Engineering Portfolio Environment Solver

Use this skill to answer data-analysis prompts that require a single JSON object built from the shared task environment. The usual domains are portfolio mix, SLA aging, and release readiness.

## First Pass

1. Read the task prompt and `input/payloads/answer_template.json` before querying data.
2. Read `environment_access.md` only for the base URL, endpoint list, credentials, and query-token instructions.
3. Fetch the relevant REST collections. Prefer REST endpoints over SQL unless the access note explicitly supplies a valid `X-Env-Token`.
4. Build a small working table of candidate records with every field used for inclusion, exclusion, classification, sorting, and aggregation.
5. Return only the JSON object requested by the template. Do not include prose.

Optional helper: `scripts/fetch_environment.py` fetches the standard REST collections into JSON files:
Back to top