Menu

Individual skill

reflect-3_attempt_01

Not available

experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_008/reflect-3/reflect-3_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
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
# Estate and Tax Planning Computation Skill

## Overview

Tasks in this family require computing detailed financial projections for estate planning, tax optimization, and wealth transfer strategies. Each task involves reading a client request memo, performing calculations based on the provided financial data, and producing a structured JSON answer matching a specific template.

## General Approach

1. **Parse the request memo carefully**: Extract all numerical values (ages, balances, rates, premiums, beneficiary counts, dates, tax brackets).
2. **Identify the analysis type**: This determines which set of calculations and enums apply.
3. **Compute all required fields**: Use the formulas and rules documented below.
4. **Resolve source priorities**: Determine the most authoritative source for each data type.
5. **Validate enum values**: Ensure all enum fields use exact allowed values.
6. **Format numbers correctly**: Use JSON numbers (not strings), rounded to cents (2 decimal places). Dates must be ISO `YYYY-MM-DD`.