Menu

Individual skill

engineering-portfolio-json-solver

0upvotes

Solve JSON-only engineering portfolio environment tasks that require querying shared work-item, portfolio mix target, SLA, release, milestone, blocker, dependency, or restricted SQL endpoints; use for tasks asking Codex to compute portfolio mix, SLA aging/breach metrics, duplicate clusters, release readiness, ship decisions, gating work, blockers, dependency chains, or schema-constrained answers from a TASK_ENV_BASE_URL and environment_access.md.

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

# Engineering Portfolio JSON Solver

Use this workflow for shared engineering portfolio tasks that require a JSON answer built from runtime environment data.

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` before querying data.
2. Extract the exact scope: dates, quarter, release, teams, product areas, categories, recent-closed window, target `scope_id`, and required output ordering.
3. Read `environment_access.md` only for runtime access details: base URL substitution, endpoint list, query token, and authentication/query syntax. Do not copy access secrets into the final answer.
4. Query authoritative environment endpoints first. Use restricted SQL only to inspect or cross-check staged environment data, not to bypass prompt logic.
5. Build the answer from current authoritative records. Treat mirror, export, cached, legacy, or denormalized fields as stale when they conflict with source-specific records.
6. Validate the final object against the template shape, required keys, enum values, ordering rules, and rounding precision. Return only JSON, with no prose.

## Data Handling Rules
Back to top