Individual skill

wealth-advisory-json

Produce JSON-only private wealth advisory planning outputs from the task-group advisory API, including Roth conversion and RMD summaries, ILIT Crummey funding checks, GRAT versus CRAT comparisons, and estate liquidity action plans. Use when a prompt asks for a client-specific structured planning object, exact schema compliance, source resolution across conflicting records, or any similar advisory memo that must be returned as JSON rather than prose.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_008/fewshot/opencode/fewshot_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.

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.

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 JSON Planner

Use this skill for client-specific advisory outputs that must exactly follow a JSON schema.

## Workflow
1. Read the prompt, request memo, and answer template first.
2. Identify the template family and the required top-level keys.
3. Query `API_BASE` for the controlling records and supporting policy data.
4. Resolve conflicts by source authority, not by recency. See [references/workflow.md](references/workflow.md).
5. Build the final object with the exact keys, enums, number types, and date formats from the template.
6. Return JSON only.

## Output rules
- Use JSON numbers for USD amounts and round to cents.