Menu

Individual skill

eng-portfolio-review

0upvotes

Query and analyze engineering work-item portfolios from a shared REST API. Use this skill whenever the task involves portfolio mix comparison against targets, SLA aging audits with overdue/breach-rate calculations, or release-readiness assessments with milestone tracking, blocker analysis, and dependency-chain resolution. Also use it when the user mentions work-item classification, SLA compliance, release gating, or any analysis that references the work-item REST API endpoints and asks for structured JSON output from them.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_024/fewshot/cc/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 Review

## Quick start

Before any analysis, read the environment access file (likely named
`environment_access.md` or similar) to obtain the base URL and any
authentication token needed for the `/api/query` endpoint. The solver's
task prompt will point you at a `<TASK_ENV_BASE_URL>` placeholder; replace
it with the actual base URL from the access file.

Identify which analysis type the task requires, then follow the
corresponding workflow below. Read [references/api-reference.md](references/api-reference.md) for
the full endpoint catalog, data model, and field semantics when you need
precise field names or endpoint capabilities.
Back to top