evaluator-optimizer
Iterative refinement workflow for polishing code, documentation, or designs through systematic evaluation and improvement cycles. Use when refining drafts into production-grade quality.
What this skill does
# Evaluator-Optimizer Iterative refinement workflow that takes existing code, documentation, or designs and polishes them through rigorous cycles of evaluation and improvement until they meet production-grade quality standards. ## When to Use This Skill - Refining a rough draft of code into production quality - Polishing documentation for clarity, completeness, and accuracy - Iteratively improving a design or architecture proposal - Systematic quality improvement where "good enough" is not sufficient - When you need to converge on high quality through structured iteration ## Quick Reference | Task | Load reference | | --- | --- | | Evaluation criteria and quality rubrics | `skills/evaluator-optimizer/references/evaluation-criteria.md` | ## Workflow: The Loop For any given artifact (code, text, design): 1. **Accept**: Take the current version of the artifact. 2. **Evaluate**: Act as a harsh critic. Rate the artifact on correctness, clarity, efficiency, style, and safety. Assign a score out of 100. 3. **Decide**: - Score >= 90: **Stop** and present the result. - Score < 90: **Refine**. 4. **Refine**: Rewrite the artifact, specifically addressing the critique from step 2. List what changed and why. 5. **Repeat**: Return to step 2 with the new version. ## Behavioral Rules - **Do not settle**: "Good enough" is not good enough. You are here to polish. - **Be explicit**: When evaluating, list specific flaws. "The function `process_data` is O(n^2) but could be O(n)." - **Show your work**: Summarize changes in each iteration. - **Self-correct**: If a refinement breaks something, revert and try a different approach. - **Converge**: Each iteration must improve the score. If two consecutive iterations do not improve the score, stop and present the best version. ## Iteration Output Template ```markdown ## Iteration [N] Evaluation | Criterion | Score (1-10) | Notes | |-----------|-------------|-------| | Correctness | | | | Clarity | | | | Efficiency | | | | Style | | | | Safety | | | | **Total** | **/50** | **[x100/50]** | ### Issues Found 1. [Specific issue with location] 2. [Specific issue with location] ### Refinements Applied - [Change 1 and rationale] - [Change 2 and rationale] ``` ## Example Interaction **Input**: "Refine this Python script." **Iteration 1 Evaluation**: - Functionality: Good - Efficiency: Poor - uses nested loops for matching - Style: Variable names `a` and `b` are unclear - Score: 60/100 **Refinements applied**: - Flattened loops using a set lookup (O(n)) - Renamed `a` to `users`, `b` to `active_ids` - Added type hints **Iteration 2 Evaluation**: - Functionality: Good - Efficiency: Excellent - Style: Good - Score: 95/100 Result: Present the refined script.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.