tune-recon
From the author
Audit existing fine-tuning or prompt engineering work — find quality gaps and optimization opportunities. Use when asked to "audit our fine-tuning work", "find prompt engineering gaps", or "look for optimization opportunities".
Install
npx skills add tonone-ai/tonone --skill tune-recon -a claude-code
Installs to .claude/skills/tune-recon/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- rank-recontonone-ai/tononeAudit ranking quality — metric trends, failure modes, dataset coverage, reranker performance. Use when asked to "audit our ranking quality", "find search relevance failures", or "review reranker performance".Engineering★ 76
- feat-recontonone-ai/tononeAudit feature engineering code for leakage, quality issues, and pipeline correctness. Use when asked to "audit our feature pipeline", "is there data leakage", or "find feature quality issues".Engineering★ 76
- code-reviewcbrock84/headcountConducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.Engineering★ 2.1K
- plot-recontonone-ai/tononeAudit existing visualizations in a codebase or notebook — find misleading charts and quality issues. Use when asked to "audit our charts", "find misleading visualizations", or "review chart quality".Engineering★ 76
- code-auditarcasilesgroup/ai-engineeringReview code for correctness bugs, concurrency and lifecycle errors, type-safety holes, error handling gaps, API-contract breaks, and maintainability problems, with every finding gated on a concrete failure scenario. Use when asked to review code, check a diff or branch for bugs, look for problems before committing or opening a PR, or assess code quality.Engineering★ 61
- review-codetobihagemann/turboReview code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps and low-value tests by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argument. Use when the user asks to "review my code", "full code review", "review my changes", "check for bugs", "scan for bugs", "review correctness", "security audit", "find vulnerabilities", "review security", "check API usage", "verify against docs", "check for cross-file duplication", "review consistency", "check for code reuse", "review simplicity", "find untested code", "find redundant tests", or "review test coverage".Engineering★ 416
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in