Menu

Individual skill

self_attempt_03

0upvotes

Not available

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_010/self/self_attempt_03/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
No
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
# Asteria Portfolio Risk Skill

Use this skill for Asteria Investment Office tasks that ask for JSON decisions on credit trades, fixed-income rotations, international equity correlations, active allocation views, or multi-asset committee files. The common pattern is: read the local task input for scope and schema, use the shared Asteria API as the current book of record, compute with unrounded source values, then emit only the requested JSON shape.

## Source Discipline

1. Read the task prompt and `input/payloads/*` files first. Treat local memos, stale snapshots, and preference packets as context, not authoritative holdings or marks.
2. Use the environment access file for the API base URL. Quote URLs that contain query strings, for example `curl -s '.../api/instruments/bonds?candidate=true'`.
3. Prefer current API records over local payload records whenever they conflict. If the schema has a `data_precedence` field, use the enum that states the current environment overrode stale local payload data.
4. Never use output files, answer files, judge feedback, or generated answers from other runs. The answer must be derived from the task inputs plus the public API only.
5. Emit exactly the JSON object requested by `answer_template.json`. Do not add narrative text around it.

Useful endpoints:

- `/api/catalog`