comparative-matrix
Generate structured comparisons and decision matrices across analyzed frameworks. Use when (1) comparing multiple frameworks or approaches side-by-side, (2) making architectural decisions between alternatives, (3) creating best-of-breed selection documentation, (4) synthesizing findings from multiple analysis skills into actionable decisions, or (5) producing recommendation reports for technical stakeholders.
What this skill does
# Comparative Matrix
Synthesizes analysis outputs into structured decision frameworks.
## Process
1. **Collect** analysis outputs from multiple frameworks
2. **Normalize** findings to comparable dimensions
3. **Generate** comparison matrix
4. **Apply** decision heuristics
5. **Document** recommendations with rationale
## Comparison Dimensions
### Core Dimensions (Always Include)
| Dimension | What to Compare | Decision Criteria |
|-----------|-----------------|-------------------|
| **Typing** | Strict (Pydantic) vs Loose (dicts) | Team preference, runtime safety needs |
| **Async** | Native async vs sync-with-wrappers | Scalability requirements |
| **State** | Immutable vs mutable | Concurrency safety, debugging |
| **Config** | Code-first vs config-first | Flexibility vs discoverability |
| **Extensibility** | Composition vs inheritance | Maintainability, learning curve |
### Domain-Specific Dimensions
| Dimension | When to Include |
|-----------|-----------------|
| **Reasoning Pattern** | Comparing agent frameworks |
| **Memory Strategy** | Long-running agents |
| **Multi-Agent** | Orchestration systems |
| **Observability** | Production deployments |
| **Tool Interface** | Custom tool development |
## Matrix Template
```markdown
## Best-of-Breed Matrix: [Analysis Title]
| Dimension | Framework A | Framework B | Framework C | **Recommendation** |
|:----------|:------------|:------------|:------------|:-------------------|
| **Typing** | Pydantic V1, deep nesting | TypedDict, flat | Loose dicts | *Pydantic V2, flat structures* |
| **Async** | Sync core, async wrapper | Native async | Mixed | *Native async required* |
| **State** | Mutable, in-place | Immutable copy | Hybrid | *Immutable preferred* |
| **Config** | YAML + Python | Pure Python | JSON | *Python for type safety* |
| **Extensibility** | Deep inheritance (6 layers) | Composition | Protocols | *Composition + Protocols* |
### Dimension Details
#### Typing
- **Framework A**: Uses Pydantic V1 with deeply nested models (Message → Content → Block → ...)
- Pro: Full validation at boundaries
- Con: Difficult to extend, version migration pain
- **Framework B**: TypedDict with flat structure
- Pro: Simple, fast, IDE support
- Con: No runtime validation
- **Recommendation**: Adopt Pydantic V2 with intentionally flat structures. Use TypedDict for internal types.
[Continue for each dimension...]
```
## Decision Heuristics
Apply these heuristics when recommendations aren't obvious:
### Scalability-First
```
IF high_concurrency_expected:
PREFER native_async
PREFER immutable_state
PREFER stateless_tools
```
### DX-First (Developer Experience)
```
IF team_is_small OR rapid_iteration:
PREFER simple_inheritance_over_protocols
PREFER code_first_config
PREFER explicit_over_magic
```
### Production-First
```
IF mission_critical:
PREFER strict_typing
PREFER comprehensive_observability
PREFER explicit_error_boundaries
```
## Output Artifacts
1. **Summary Matrix** - Single-page comparison table
2. **Detailed Analysis** - Per-dimension breakdown with evidence
3. **Recommendation Document** - Actionable decisions with rationale
4. **Trade-off Log** - Documented compromises and their justification
## Example Output Structure
```
comparative-analysis/
├── matrix.md # Summary comparison table
├── dimensions/
│ ├── typing.md # Detailed typing analysis
│ ├── async.md # Concurrency model analysis
│ └── ...
├── recommendations.md # Final decisions
└── tradeoffs.md # Documented compromises
```
## Integration
- **Inputs from**: All Phase 1 & 2 analysis skills
- **Outputs to**: `antipattern-catalog`, `architecture-synthesis`
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.