# Tool Evaluator

> Evalúa herramientas y tecnologías objetivamente. Usa este skill para comparar opciones técnicas, evaluar vendors, hacer build vs buy decisions, y elegir el stack correcto para cada problema.

- Skill: `leandroomargarcia/tool-evaluator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add leandroomargarcia/tool-evaluator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leandroomargarcia/tool-evaluator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: leandroomargarcia (https://skillmd.com/u/leandroomargarcia)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/leandroomargarcia/tool-evaluator

---


# Tool Evaluator

Especialista en evaluar herramientas, frameworks, y servicios de forma objetiva. Ayuda a tomar decisiones técnicas informadas basadas en necesidades reales.

## Cuándo Usar Este Skill

- Comparar frameworks o librerías
- Evaluar SaaS vs build in-house
- Seleccionar vendors
- Decidir migraciones técnicas
- Evaluar nueva tecnología
- Build vs buy decisions

## Evaluation Framework

```
PARA CADA HERRAMIENTA, EVALUAR:

1. FIT (1-5)
   - ¿Resuelve nuestro problema?
   - ¿Escala con nuestras necesidades?
   - ¿Se integra con nuestro stack?

2. MATURITY (1-5)
   - ¿Qué tan establecida está?
   - ¿Comunidad activa?
   - ¿Documentación completa?

3. COST (1-5)
   - ¿Precio inicial?
   - ¿Escala de costos?
   - ¿Hidden costs?

4. RISK (1-5)
   - ¿Vendor lock-in?
   - ¿Longevity del proyecto?
   - ¿Security track record?

5. TEAM (1-5)
   - ¿Learning curve?
   - ¿Team expertise?
   - ¿Hiring pool?

TOTAL SCORE = weighted average
```

## Evaluation Template

```markdown
## Tool Evaluation: [Category]

**Evaluator:** @person
**Date:** [date]
**Decision needed by:** [date]

### Problem Statement
[What problem are we solving?]

### Requirements
Must Have:
- [ ] Requirement 1
- [ ] Requirement 2

Nice to Have:
- [ ] Requirement 3
- [ ] Requirement 4

### Options Evaluated

#### Option A: [Name]
**Fit:** 4/5
**Maturity:** 5/5
**Cost:** 3/5
**Risk:** 4/5
**Team:** 4/5
**Total:** 4.0/5

Pros:
- [Pro 1]
- [Pro 2]

Cons:
- [Con 1]
- [Con 2]

#### Option B: [Name]
[Same structure]

### Comparison Matrix
| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| Fit | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Cost | $$$ | $ | $$ |
| Learning | Medium | Easy | Hard |

### Recommendation
**Chosen:** Option [X]

**Rationale:**
[Why this option best fits our needs]

### Implementation Plan
1. [Step 1]
2. [Step 2]
3. [Step 3]

### Risks & Mitigations
- [Risk]: [Mitigation]
```

## Build vs Buy Framework

```
CONSIDERAR BUILD CUANDO:
- Core differentiator
- Unique requirements
- Long-term cost savings
- Full control needed
- Simple enough to maintain

CONSIDERAR BUY CUANDO:
- Commodity feature
- Time to market critical
- Specialized expertise needed
- Maintenance burden too high
- Better TCO over time

QUESTIONS TO ASK:
1. ¿Es core para nuestro negocio?
2. ¿Tenemos expertise para buildear?
3. ¿Cuál es el TCO a 3 años?
4. ¿Qué pasa si el vendor desaparece?
5. ¿Podemos migrar si es necesario?
```

## TCO Calculation

```
TOTAL COST OF OWNERSHIP:

INITIAL COSTS:
+ License/subscription
+ Implementation
+ Training
+ Migration
+ Integration

ONGOING COSTS:
+ Monthly/annual fees
+ Maintenance
+ Support
+ Updates
+ Infrastructure

HIDDEN COSTS:
+ Learning curve
+ Productivity loss during transition
+ Technical debt
+ Vendor negotiations
+ Exit/migration costs

CALCULATE FOR 3 YEARS:
TCO = Initial + (Ongoing × 36) + Hidden
```

## Technology Radar

```
ASSESS NEW TECH:

ADOPT:
- Production-ready
- Proven value
- Team trained
- Start using now

TRIAL:
- Promising
- Worth trying
- Low-risk projects
- Evaluate further

ASSESS:
- Interesting
- Worth watching
- Research more
- Not ready yet

HOLD:
- Too risky
- Better alternatives
- Wait and see
- Don't invest yet
```

## Vendor Evaluation

```
DUE DILIGENCE CHECKLIST:

COMPANY:
☐ Financial stability
☐ Growth trajectory
☐ Customer base size
☐ Leadership team
☐ Funding/exit risk

PRODUCT:
☐ Feature completeness
☐ Roadmap alignment
☐ API/integration quality
☐ Performance benchmarks
☐ Security certifications

SUPPORT:
☐ SLA guarantees
☐ Support channels
☐ Response times
☐ Documentation quality
☐ Community/forums

CONTRACT:
☐ Pricing model clear
☐ Exit terms
☐ Data ownership
☐ Compliance (GDPR, etc.)
☐ Liability limits
```

## Migration Risk Assessment

```
BEFORE MIGRATING:

LOW RISK:
- Well-defined scope
- Good documentation
- Parallel running possible
- Rollback plan clear
- Team experienced

HIGH RISK:
- Unclear scope
- Poor documentation
- Big bang required
- No rollback
- New to team

MITIGATION STRATEGIES:
1. Incremental migration
2. Feature flags
3. Shadow testing
4. Extended parallel run
5. Rollback procedures
```

## Decision Record Template

```markdown
## ADR: [Decision Title]

**Status:** Proposed | Accepted | Deprecated
**Date:** [date]
**Deciders:** @person1, @person2

### Context
[Why is this decision needed?]

### Decision
[What we decided]

### Consequences

Positive:
- [Benefit 1]
- [Benefit 2]

Negative:
- [Tradeoff 1]
- [Tradeoff 2]

### Alternatives Considered
1. [Alternative 1]: [Why not chosen]
2. [Alternative 2]: [Why not chosen]

### Review Date
[When to revisit this decision]
```

## Red Flags

```
⚠️ VENDOR WARNING SIGNS:
- No pricing transparency
- Aggressive sales tactics
- Poor documentation
- No trial available
- Recent leadership exodus
- Declining community activity
- Acquisition rumors
- Lock-in by design

⚠️ TECHNOLOGY WARNING SIGNS:
- Single maintainer
- No updates in 6+ months
- Breaking changes frequently
- Poor backwards compatibility
- Minimal adoption
- No enterprise users
- Security incidents
```

## Mejores Prácticas

1. **Define requirements first** - Don't evaluate in vacuum
2. **Try before you buy** - POC/trial essential
3. **Consider TCO** - Cheap now ≠ cheap forever
4. **Plan for exit** - What if vendor fails?
5. **Get team input** - They'll use it daily
6. **Document decision** - Future you will thank you

## Filosofía

> "The best tool is the one that solves your problem with the least total cost and risk, not the one with the most features."

El objetivo es tomar decisiones técnicas informadas que balanceen necesidades presentes con flexibilidad futura.