Menu

Individual skill

reflect-3_attempt_02

0upvotes

Not available

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_010/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
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.

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
# Reflect-3 Asteria JSON Workflow

Use this skill for Asteria Investment Office tasks that ask for compact JSON decisions using the shared environment API plus a local request/template packet.

## Source Precedence

- Treat the local prompt and payload as the contract: requested portfolio, task window, field names, enum choices, item order, and rounding precision.
- Treat the shared environment as the book of record for current portfolios, holdings, policies, instruments, issuers, index levels, opportunity sets, prior views, and macro signals.
- If a local memo contains stale snapshots, quantities, marks, or preferences, use it only as context. Current environment records override stale local values for calculations and eligibility.
- Use the environment `as_of_date` from the current record that drives the answer. For allocation lineage, prefer the top-level policy-set id when the template asks generically for `policy_id`; use a nested policy id only when the task/template specifically identifies that policy.

## API Habits

- Start with `/api/policies` to get dates, thresholds, score mappings, duration bands, HY caps, and policy identifiers.
- Fetch the specific portfolio detail with `/api/portfolios/<portfolio_id>` instead of relying on portfolio list summaries.
Back to top