Individual skill
reflect-3
Solve private-wealth-advisory structured planning tasks (Roth/RMD, ILIT/Crummey, GRAT/CRAT, estate-liquidity) against a remote advisory API with conflicting source documents. Produce exact JSON conforming to each task's answer template.
experiments/claude_code_glm_5_2_max/reports/skills/task_group_008/reflect-3/reflect-3_attempt_02/SKILL.md
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.
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- engineering Derived category
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
# Private Wealth Advisory Structured-Output Skill
Produce a single JSON object conforming to the task's `answer_template.json`. No prose outside the JSON. All USD amounts rounded to cents (2 decimals, JSON numbers not strings). All dates ISO `YYYY-MM-DD`.
## 1. Remote API workflow
Read the API base URL from the staged `environment_access.md` (the harness `API_BASE`). Call endpoints in this order, GET unless noted:
1. `GET /api/health` — confirm the environment is up.
2. `GET /api/clients/<client_id>` — base client record (age, filing_status, planning_year, estate_value, liquid_assets).
3. `GET /api/source-documents?client_id=<id>` — the conflicting source docs (CRM_NOTE, ATTORNEY_MEMO, SIGNED_PROFILE, sometimes STALE_MARKETING_INTAKE). Each has `effective_date` and a `facts` map.
4. `GET /api/retirement-accounts?client_id=<id>` — custodian retirement accounts (traditional/roth balances, expected_return, rmd_start_age, recommended_conversion_years).
5. `GET /api/life-insurance?client_id=<id>` — ILIT policy facts (death_benefit, annual_premium, planned_contribution_date, is_existing_policy_transfer).
6. `GET /api/trust-candidates?client_id=<id>` — GRAT/CRAT candidate (asset_value, expected_growth_rate, grat_term_years, grat_annuity_rate, crat_term_years, crat_payout_rate).