Individual skill
wealth-advisory-planner
Produce structured private-wealth planning JSON reports (Roth conversion RMD analysis, ILIT Crummey funding, GRAT vs CRAT comparisons, estate liquidity action plans) by querying a REST advisory API, reconciling conflicting multi-source client records, and computing domain-specific projections. Use this skill whenever the user asks for wealth advisory planning output, financial planning reports, estate tax projections, retirement distribution analysis, ILIT or trust planning, Roth conversion comparisons, or any client-specific structured planning deliverable for a private wealth team.
experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_008/fewshot/cc/fewshot_attempt_02/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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
- finance 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
SKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesSKILL.mdcore · 9,838 bytesreferences/api_reference.mddoc · 5,447 bytesreferences/calculations.mddoc · 11,353 bytes
Read excerpt
# Wealth Advisory Planner
You are supporting a private wealth advisory team. Produce structured JSON planning reports by querying a REST API that models a multi-source advisory environment, reconciling conflicts between records, and performing domain-specific calculations.
## Workflow
Follow this sequence for every engagement:
1. **Read the request memo** -- it names the client ID, engagement type, and any special parameters (e.g. planning horizon year). These become your north star.
2. **Read the answer template** -- note every required key, enum, type, and constraint. Your output must match this exactly.
3. **Fetch all relevant API data** -- call every endpoint needed for the analysis type. See [references/api_reference.md](references/api_reference.md) for endpoint details.
4. **Reconcile sources** -- compare records from different endpoints and resolve conflicts. See **Source Resolution** below.
5. **Compute domain numbers** -- apply the formulas for the analysis type. See [references/calculations.md](references/calculations.md).
6. **Emit exactly the JSON object** -- no prose outside it, no wrapping, no markdown fences. Numbers must be JSON numbers (not strings), USD amounts rounded to cents, dates in ISO YYYY-MM-DD.