Menu

Individual skill

reflect-3_attempt_01

0upvotes

Not available

experiments/claude_code_glm_5_2_max/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
# Personal Financial Advisory — Structured Planning Output Skill

Methodology for producing the structured JSON planning output the advisory harness
expects across five analysis types: `roth_conversion_rmd`, `ilit_crummey_implementation`,
`trust_comparison`, and `estate_liquidity_action_plan`. The advisory API exposes client
records plus CONFLICTING source documents (CRM note, attorney memo, custodian export,
signed profile, stale marketing intake). Resolving which source controls each fact is
half the task; applying the right formula with cent-level rounding is the other half.

## 1. Remote API Workflow (endpoint order)

Base URL is supplied by the harness as the advisory API base. Always GET in this order:

1. `GET /api/health` — confirm `{ok:true}` before anything else.
2. `GET /api/clients/<client_id>` — base record (age, filing_status, planning_year,