Individual skill

asteria-investment-office

Complete institutional portfolio tasks for the Asteria Investment Office. Use this skill whenever the user mentions Asteria, a portfolio id like PF-EN-ALTA, PF-INT-NEXVEN, PF-FI-LUMEN, or PF-MA-HELIO, a CIO allocation view refresh, credit trade strategy, fixed-income rebalance, equity correlation review, multi-asset committee JSON, or any task that references a shared Asteria environment or API. Do not skip this skill even when the task seems straightforward — the Asteria API is the authoritative book of record and stale local payloads must always be reconciled against it.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_010/fewshot/opencode/fewshot_attempt_01/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

# Asteria Investment Office Portfolio Work

Use the Asteria shared environment API as the authoritative book of record. Local payloads (desk requests, meeting memos, committee packets) are intake context that may contain stale marks, preferences from earlier worksheets, or unreconciled snapshots. Always read current records from the API before making decisions.

## Core Principle: Current Environment Over Stale Payload

Every task follows a single overriding rule: the API returns the current state, and local payloads may be stale. When the two conflict, prefer the API. This is captured in the `data_precedence` field on credit tasks as `current_environment_over_stale_payload`, but it applies equally to all task types.

Concretely:
- Portfolio holdings from the API are the current book; stale snapshots in payloads are not.
- Bond data, issuer/watchlist status, index levels, prior views, macro signals — all come from the API, not from payload notes.
- Payload preferences (e.g., "the desk wants LNG exposure") guide candidate selection but do not override API facts about watchlist status, rating buckets, or eligibility.
- Never copy holding quantities, market values, HY percentages, or index levels from a payload snapshot when the API provides current values.