Individual skill

engineering-portfolio-audit

Analyze shared engineering portfolio task environments and produce schema-exact JSON answers for work item portfolio mix, SLA aging, release readiness, blockers, dependencies, duplicate clusters, stale mirror fields, and prompts that provide a TASK_ENV_BASE_URL plus answer_template.json.

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

Use this skill to answer task-environment prompts that ask for portfolio mix, SLA aging, or release readiness from work item data. Treat the prompt and `input/payloads/answer_template.json` as the output contract.

## Core Workflow

1. Read the user prompt, answer template, and runtime access file. Extract the base URL, allowed endpoints, scope filters, dates, precision, ordering, and required JSON keys.
2. Fetch the environment data. Prefer `scripts/fetch_env_snapshot.py` for documented GET endpoints:

   ```bash
   python3 skill/scripts/fetch_env_snapshot.py --base-url "$TASK_ENV_BASE_URL" --out /tmp/task-env-snapshot.json
   ```

   If a restricted SQL query token is supplied, pass it only to documented query calls that need it. The observed GET endpoints are sufficient for portfolio mix, SLA aging, and release readiness tasks.
Back to top