Individual skill

asteria-portfolio

Institutional portfolio workflows for the Asteria Investment Office shared environment. Use when preparing JSON answer files for Asteria credit trade strategies, international equity correlation reviews, CIO allocation view refreshes, fixed-income risk rebalances, or multi-asset committee decisions. Covers API-driven data fetching from the task environment, Pearson correlation computations, signal-to-view mapping, constraint checks, and strict JSON output contracts. Do not use for generic portfolio work or non-Asteria domains.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_010/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
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 Portfolio

## Core rules

Apply these on every Asteria task, regardless of task type.

### Environment-first precedence

Always fetch current records from the task-environment API before making decisions. Local payloads (desk requests, meeting memos, committee packets) are intake context and may contain stale marks, preferences, or pre-reconciled snapshots. When a local value conflicts with the current environment, default to the environment value and set `data_precedence` to `current_environment_over_stale_payload` where the output contract requires it.

### JSON output contract

Every task provides an `input/payloads/answer_template.json` that declares the required output shape: top-level keys, field types, enum allowed values, numeric precisions, list lengths, and sort orders. Read the template first and conform to it exactly. Do not add extra fields, skip required fields, or change precision.
Back to top