# Finance Skill Tuner

> Diagnose and fix a finance skill that isn't behaving — one that won't trigger, fires when it shouldn't, skips a confirmation, eyeballs the math, or returns the wrong format. Use when someone says "my skill didn't fire," "fix my [X] skill," "it gave the wrong format," "it didn't ask me first," "improve my [X] workflow," or "this skill keeps doing the wrong thing."

- Skill: `aircfo/finance-skill-tuner` (Agent Skill)
- Install (CLI): `npx skillmds@latest add aircfo/finance-skill-tuner`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aircfo/finance-skill-tuner/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: aircfo (https://skillmd.com/u/aircfo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aircfo/finance-skill-tuner

---


# Finance Skill Tuner — diagnose and repair an authored skill

Finance workflows get refined over time. This skill takes a skill the user already authored (usually with `finance-skill-builder`) and fixes why it's misbehaving — in plain language, because the cause is almost always one of a handful of known ones.

## 1 · Find the skill
Look in `.claude/skills/` (this project) and `~/.claude/skills/` (personal). If the name is ambiguous, list the candidates and let the user pick. Read its `SKILL.md` end to end before changing anything.

## 2 · Diagnose against the common failure modes
Match the symptom the user describes to its usual cause:

| Symptom | Usual cause | Fix |
| --- | --- | --- |
| Didn't trigger when expected | `description` is too vague, or missing the phrase the user actually says | Rewrite the description: lead with what it does, add concrete trigger phrases in the user's words |
| Triggers when it shouldn't | `description` overlaps another skill or is too broad | Narrow it; spell out what it's *not* for |
| Re-derived the account setup / used the wrong accounts | Missing (or naive) **Step 0 — load `finance-profile.md`** | Add the Step 0 block with the ContextOS lookup order (pointer → default Desktop folder, new then legacy name → workspace), and name the definitions it depends on |
| Couldn't find the profile and re-ran onboarding | Step 0 only checks the current folder | Add the full lookup order so it finds the saved profile before falling back to `finance-context-builder` |
| Totals look wrong or inconsistent | Aggregates were eyeballed | Add the computation-step rule to **Always** |
| Finalized without checking | Missing a **Gate** | Add a confirmation gate before the output |
| Output is the wrong shape | Output template is vague or absent | Pin a concrete **Output format** |
| Touched a connector / leaked detail | Missing **Never** rules | Add the read-only + no-secrets guardrails |

If the symptom doesn't match the table, read the skill closely and find where its instructions are ambiguous — the spot where a careful reader could reasonably do two different things. That ambiguity is usually the bug.

## 3 · Propose the fix
Show the before/after for only the lines that change, and explain **why** in one sentence each — the user is non-technical, so say what the change does, not just that you made it. Leave everything that already works untouched.

## 4 · Apply and re-test
On confirmation, edit the file in place. Offer to re-run the skill against the connectors for a recent period to confirm the fix holds.

## Never
- Don't rewrite a skill wholesale to "clean it up" — change only what's broken, and preserve the user's logic and voice.
- Read-only against all connectors, including during any test run.
- Never store secrets, tokens, or full account numbers.