Menu

Individual skill

reflect-3_attempt_02

0upvotes

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_024/reflect-3/reflect-3_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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
# Portfolio Engineering Skill

Solve portfolio-mix, SLA-aging, and release-readiness assessment tasks against a shared API environment containing work items, targets, policies, releases, milestones, blockers, and dependencies.

## Entry Checklist

Before building an answer, read these three inputs:

1. **Task prompt** (`input/prompt.txt`) — scope, domain, target date or quarter, the specific question to answer.
2. **Answer template** (`input/payloads/answer_template.json`) — the exact JSON schema the answer must match. Every `required` field must be present. Every `enum` or `const` must be respected. Sort orders, rounding rules, and field descriptions in the schema are binding.
3. **Environment access** (`environment_access.md` at the project root) — base URL, available endpoints, any required headers or tokens.

## Environment and Data Sources

All tasks share a REST API at the base URL from the environment access file. Use only the endpoints listed there. The data model includes these entities:
Back to top