Individual skill
wealth-advisory-api-planning
Solve private wealth advisory task-group API planning outputs as schema-conforming JSON. Use when Codex must read a local prompt, request memo, and answer_template.json, fetch advisory records from the provided API, resolve conflicting client/source data, and compute Roth conversion/RMD, ILIT Crummey, GRAT/CRAT, or estate-liquidity action-plan fields.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_008/fewshot/naive/fewshot_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
- data 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
# Wealth Advisory API Planning
## Workflow
1. Read the task prompt, `input/payloads/request_memo.md`, and `input/payloads/answer_template.json`.
2. Extract `client_id`, engagement type, planning horizon if supplied, and the required output fields. Set `task_id` from the current task directory name unless the harness provides it directly.
3. Use `API_BASE` if set; otherwise read the local environment access note for the base URL. Fetch only documented GET endpoints. Never call a judge endpoint.
4. Fetch:
- `/api/clients/{client_id}`
- `/api/source-documents?client_id={client_id}`
- `/api/retirement-accounts?client_id={client_id}`
- `/api/life-insurance?client_id={client_id}`
- `/api/trust-candidates?client_id={client_id}`
- `/api/policies/tax`