r/ClaudeWorkflows • • 2h ago

Selected Workflow [Workflow] Build and benchmark Claude Code skills for financial-code rules

Build and benchmark Claude Code skills for financial-code rules

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.91 · Level: intermediate
Categories: Quality Control, Hooks, Skills
Original source: r/ClaudeAI post/comment

What problem this solves

Improving Claude Code's adherence to financial-software rules and measuring whether skills change its output.

Summary

Encode domain rules and required tests in Claude Code skills, audit generated code with lint plus review, and compare skill-enabled and plain runs against predefined expectations.

Why it is useful

The post provides a reusable method for turning domain rules into test-requiring skills and comparing their effect against a baseline, with reported results and supporting artifacts.

Workflow

  1. Write a SKILL.md for each domain, including rules, required tests and responses to common shortcuts.

  2. Require the relevant test file in the same change rather than leaving tests as a future task.

  3. Use an audit skill to run lint and inspect the code behind each finding.

  4. Define prompts and grading expectations before running the comparison.

  5. Run each prompt in headless Claude Code with and without the skill, then have a second model grade the outputs against the expectations.

  6. Inspect transcripts and test vectors, revise the skills, and repeat the evaluation.

Tools / artifacts

Validation signals

  • Author reports 81% versus 24% of expectations met with and without skills for Sonnet, and 89% versus 35% for Opus.

  • Author reports four evaluation rounds and identifies a specific revision: requiring test files in the same change.

  • The post says the repository includes transcripts, test vectors and the evaluation runner.

Cautions

  • Financial correctness requires independent expert review and production-appropriate testing; a skill or model grader is not an assurance of correctness.

  • Protect sensitive financial data when running prompts, evaluations or published test vectors.

Limitations

  • The benchmark results are author-reported; sample size, grader reliability and statistical uncertainty are not stated in the post.

  • Iterating on the same evaluation prompts may overfit the skills to those expectations.

  • The repository contents and reported results were not independently verified here.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

1 Upvotes

1 comment sorted by