score-style
Score migrated code against style guidelines and best practices. Evaluates code quality independent of functional correctness.
What this skill does
Evaluate migrated code against style guidelines and best practices.
This skill scores code quality aspects that are independent of functional correctness — focusing on readability, maintainability, and adherence to conventions.
## Default Scoring Criteria
Unless a custom rubric is provided, score on these attributes (1-5 scale):
### Naming Conventions (1-5)
- 1: Inconsistent or meaningless names
- 3: Mostly follows conventions, some issues
- 5: Clear, consistent, idiomatic names
### Code Organization (1-5)
- 1: Monolithic, hard to navigate
- 3: Some structure, could be cleaner
- 5: Well-organized, logical structure
### Error Handling (1-5)
- 1: Missing or swallowed exceptions
- 3: Basic error handling present
- 5: Comprehensive, appropriate error handling
### Documentation (1-5)
- 1: No documentation
- 3: Some documentation, inconsistent
- 5: Thorough, helpful documentation
### Idiomaticity (1-5)
- 1: Non-idiomatic, smells like translated code
- 3: Mostly idiomatic, some foreign patterns
- 5: Fully idiomatic, natural code
## Output Format
Save scores as a JSON file:
```json
{
"target_file_a.java": {
"naming_conventions": 4,
"code_organization": 3,
"error_handling": 5,
"documentation": 4,
"idiomaticity": 4,
"justification": "Good naming and error handling. Some methods could be extracted for better organization."
}
}
```
## Custom Rubric
If a custom rubric is provided, use its attributes and scoring criteria instead of the defaults. The rubric should define:
- Attribute names
- Score meanings for each level (1-5)
- Examples of good/bad code for each attribute
## Evaluation Guidelines
### What to Look For
**Positive indicators:**
- Consistent naming (camelCase for Java, snake_case for Python)
- Appropriate class/method sizes
- Single responsibility principle followed
- Meaningful comments (not obvious ones)
- Standard library usage over custom implementations
- Defensive programming practices
**Negative indicators:**
- Literal translations (COBOL-style Java)
- God classes or methods
- Magic numbers
- Excessive comments or no comments
- Reinvented wheels
- Swallowed exceptions
- Hardcoded values
### Language-Specific Considerations
**Java:**
- Streams vs. for loops (both acceptable, but be consistent)
- Optional vs. null checks
- Record types for data classes
- Builder pattern for complex objects
**Python:**
- Type hints
- List comprehensions
- Context managers
- Pythonic idioms
## Incremental Scoring
If a score file already exists, update it with new scores rather than replacing it entirely.
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.