Menu

Individual skill

self_attempt_03

0upvotes

Not available

experiments/claude_code_kimi2_6_enabled/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
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
# Skill: Structured Financial JSON Generation from Portfolio Data

## When to Use

Use this skill when given a prompt and one or more JSON payload files that describe a portfolio management, risk analysis, or performance attribution task, and you must produce a structured JSON answer conforming to a strict schema template.

## Overview

These tasks require reading financial data from a request JSON, performing precise quantitative calculations, and emitting a response JSON that exactly matches a provided schema template. The schema defines required top-level keys, field types, enum values, ordering rules, and numeric precision. Errors in calculation, field ordering, or enum values will cause rejection.

## Step-by-Step Procedure

### 1. Read All Input Files

Read the `prompt.txt`, the request JSON (e.g., `desk_request.json`, `review_request.json`, `allocation_request.json`, `risk_meeting_memo.json`, `committee_request.json`), and the `answer_template.json`. Do not skip any file — the prompt may contain critical context (e.g., benchmark definitions, lookback periods, calculation conventions) not repeated in the JSON.
Back to top