evaluating-new-technology
Create a Technology Evaluation Pack (problem framing, options matrix, build vs buy, pilot plan, risk review, decision memo). Use for evaluating new tech, emerging technology, AI tools, vendor selection, and tech stack decisions.
npx skills add majiayu000/claude-skill-registry --skill evaluating-new-technology-liqiongyu-lenny-skills-plus --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Evaluating New Technology ## Scope **Covers** - Evaluating a new tool/platform/vendor (including AI products) for adoption - Emerging tech “should we use this?” decisions - Build vs buy decisions and tech stack changes - Running a proof-of-value pilot and capturing evidence - First-pass risk review (security/privacy/compliance, vendor claims, operational readiness) **When to use** - “Evaluate this new AI tool/vendor for our team.” - “Should we build this in-house or buy a vendor?” - “We’re considering changing our analytics/experimentation stack—make a recommendation.” - “Create a technology evaluation doc with a pilot plan, risks, and decision memo.” **When NOT to use** - You don’t have a real problem/job to solve yet (use `problem-definition` first). - You need a full product strategy/roadmap (use `ai-product-strategy`). - You’re designing how to build an LLM system (use `building-with-llms`). - You need a formal security assessment / penetration testing (engage security; this skill produces a structured first pass). ## Inputs **Minimum required** - Candidate technology (what it is, vendor/build option, links if available) - Problem/workflow to improve + who it’s for - Current
- Scope
- Inputs
- Outputs (deliverables)
- Workflow (8 steps)
- 1) Start with the problem (avoid tool bias)
- 2) Define “good” and hard constraints
- 3) Map options and evaluation criteria (workflows → ROI)
- 4) Fast reality check: integration + data fit
- 5) Build vs buy with “bandwidth” as a first-class cost
- 6) Risk & guardrails review (be skeptical of “100% safe” claims)
- 7) Plan a proof-of-value pilot (or document why you can skip it)
- 8) Decide, communicate, and quality-gate
- Quality gate (required)
- Examples
What does the evaluating-new-technology skill do?
Create a Technology Evaluation Pack (problem framing, options matrix, build vs buy, pilot plan, risk review, decision memo). Use for evaluating new tech, emerging technology, AI tools, vendor selection, and tech stack decisions.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill evaluating-new-technology-liqiongyu-lenny-skills-plus --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.