Individual skill
self_attempt_02
Not available
experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_008/self/self_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.
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
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
# Roth Conversion RMD Analysis Skill
## Task Overview
Given a client profile with conflicting data sources, produce a JSON analysis recommending whether to execute a staged Roth conversion, defer, or take no conversion action. The analysis must resolve source conflicts, project RMD taxes, and estimate legacy balances.
## Input Structure
Each task contains:
- `prompt.txt` — generic instruction to read `request_memo.md` and produce deliverable
- `payloads/request_memo.md` — client profile, conflicting sources, goals, and specific questions
- `payloads/answer_template.json` — exact schema and enum values for the output
## Source Resolution Rules
The output requires `source_resolution` with two fields:
- `controlling_profile_source`: authoritative source for demographic/legal data (DOB, salary, heir info, tax profile)
- `controlling_account_source`: authoritative source for account balances