Agent skill

evaluating-new-technology

Help users evaluate emerging technologies. Use when someone is assessing new tools, making build vs buy decisions, evaluating AI vendors, or deciding on technical architecture.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill evaluating-new-technology-refoundai-lenny-skills-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/evaluating-new-technology-refoundai-lenny-skills-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Evaluating New Technology Help the user evaluate emerging technologies using frameworks from 22 product leaders who have made critical technology decisions at companies from Google to Shopify. ## How to Help When the user asks for help evaluating technology: 1. **Start with the problem** - Clarify what problem they're solving before discussing tools 2. **Assess maturity** - Determine if the technology is stable enough for their use case 3. **Consider build and buy** - Help them find the right mix rather than forcing a binary choice 4. **Plan for change** - Design for modularity since the landscape will shift ## Core Principles ### Tools solve problems, not the reverse Austin Hay: "I have this adage I always say, which is tools are just meant to solve problems. And the problem set for marketing technologists and business technologists is you focus on the tools." Always define the problem and the people involved before selecting a system or tool. ### Build AND buy, not build vs buy Austin Hay: "Build and buy as opposed to build versus buy. Build and buy means that both of you can win." Buy tools to handle 90% of standard functionality and build the 'cool' 10% that is unique to your

What's inside
Steps it walks through
  1. How to Help
  2. Core Principles
  3. Tools solve problems, not the reverse
  4. Build AND buy, not build vs buy
  5. Evaluate mental bandwidth, not just dollars
  6. Update your priors constantly
  7. Bet on abstraction layers
  8. AI guardrails don't work
  9. Use the tools yourself
  10. Context drives AI value
  11. Questions to Help Users
  12. Common Mistakes to Flag
  13. Deep Dive
  14. Related Skills
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the evaluating-new-technology skill do?

Help users evaluate emerging technologies. Use when someone is assessing new tools, making build vs buy decisions, evaluating AI vendors, or deciding on technical architecture.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill evaluating-new-technology-refoundai-lenny-skills-2 --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.

Keep going