Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jwynia avatar

Technology Impact

  • 286 installs
  • 133 repo stars
  • Updated February 24, 2026
  • jwynia/agent-skills

technology-impact is a version 1.0 Claude agent skill that applies McLuhan's Tetrad of Media Effects to evaluate how proposed technologies affect roadmap risk, team skills, cost, and delivery before developers commit to

About

technology-impact is a jwynia/agent-skills utility at version 1.0 that systematically analyzes societal and organizational consequences of technologies using McLuhan's Tetrad of Media Effects. The framework examines four simultaneous dimensions—what a technology enhances, obsoletes, retrieves, and reverses—to reveal non-obvious adoption risks that roadmap spreadsheets miss. Developers and tech leads invoke technology-impact when evaluating new frameworks, planning platform migrations, or drafting technology policy before architecture review boards sign off. The skill's evaluative mode targets worldbuilding and adoption planning workflows where second-order effects on teams, cost, and delivery timelines matter as much as feature checklists. Reach for technology-impact during vendor bake-offs, build-vs-buy decisions, or platform shifts when stakeholders need structured consequence mapping instead of hype-driven slide decks. Outputs are tetrad worksheets and impact narratives engineers attach to RFCs, ADRs, and adoption proposals so trade-offs stay visible through implementation.

  • Structured impact framing for tech decisions
  • Compare adoption, maintenance, and lock-in risks
  • Connect engineering choices to product and business outcomes
  • Surface hidden migration and talent costs
  • Outputs decision-ready notes for stakeholders

Technology Impact by the numbers

  • 286 all-time installs (skills.sh)
  • +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #920 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jwynia/agent-skills --skill technology-impact

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs286
repo stars133
Last updatedFebruary 24, 2026
Repositoryjwynia/agent-skills

How do you assess technology adoption risks before committing?

Assess how a proposed technology, framework, or platform shift affects roadmap risk, team skills, cost, and delivery before committing to architecture or vendor choices.

Who is it for?

Tech leads and architects evaluating framework or platform shifts who need structured consequence analysis before locking stack or vendor choices.

Skip if: Developers who already finalized architecture and only need implementation tutorials without pre-adoption impact assessment.

When should I use this skill?

A developer asks to evaluate technology adoption, analyze societal or organizational impacts of a platform shift, or apply McLuhan Tetrad before committing to new tooling.

What you get

McLuhan Tetrad worksheet, four-effect impact analysis, adoption risk narrative, and consequence map for architecture or vendor decisions.

  • Tetrad impact worksheet
  • Adoption risk narrative
  • Consequence map for ADRs

By the numbers

  • Version 1.0
  • McLuhan Tetrad covers 4 simultaneous media effects

Files

SKILL.mdMarkdownGitHub ↗

Technology Impact Analysis (McLuhan Tetrad)

Purpose

Systematically analyze the societal impacts of technologies using McLuhan's Tetrad of Media Effects. Examines what technology enhances, obsoletes, retrieves, and reverses to reveal non-obvious consequences.

Core Framework: The Tetrad

Every technology simultaneously has four effects:

EffectQuestionWhat It Reveals
EnhancementWhat does it amplify?Primary capabilities increased
ObsolescenceWhat does it displace?What becomes less relevant
RetrievalWhat does it bring back?Historical patterns revived
ReversalWhat does it become when pushed to extreme?Paradoxical consequences

---

Core Tetrad Questions

Enhancement

  • What capabilities, processes, or tendencies does this technology amplify?
  • How does enhancement manifest across different contexts?
  • What are primary and secondary enhancement effects?

Obsolescence

  • What existing systems, skills, or practices does it displace?
  • Which displaced elements might persist in modified forms?
  • What are the implications of these obsolescences?

Retrieval

  • What historical practices or patterns does it revive in new forms?
  • How do these retrievals manifest differently from originals?
  • What historical understanding informs our analysis?

Reversal

  • What happens when enhancement effects are pushed to extremes?
  • What paradoxical effects emerge from widespread adoption?
  • How might current trends reverse themselves?

---

Analysis Dimensions

1. Domain Analysis

Examine each societal domain:

Economic

  • Production systems
  • Labor markets
  • Financial systems
  • Business models
  • Consumer behavior

Social

  • Interpersonal relationships
  • Community structures
  • Social mobility
  • Cultural expression
  • Identity formation

Political

  • Governance systems
  • Democratic processes
  • Power distribution
  • Policy formation
  • Civic engagement

Educational

  • Learning systems
  • Knowledge transfer
  • Skill development
  • Educational access

Healthcare

  • Care delivery
  • Medical research
  • Health management
  • Healthcare access

Environmental

  • Resource usage
  • Sustainability practices
  • Climate impact
  • Ecosystem management

2. Stakeholder Impact

For each effect, examine impact on:

Demographics

  • Age groups
  • Socioeconomic classes
  • Geographic locations
  • Educational backgrounds

Power Structures

  • Existing authorities
  • Emerging players
  • Resource controllers
  • Knowledge holders

Vulnerable Populations

  • Economic vulnerability
  • Digital divide impacts
  • Accessibility concerns
  • Cultural marginalization

3. Temporal Analysis

Time Horizons

  • Immediate (0-2 years)
  • Short-term (2-5 years)
  • Medium-term (5-10 years)
  • Long-term (10+ years)

Development Patterns

  • Adoption curves
  • Resistance patterns
  • Acceleration points
  • Stabilization periods

Historical Parallels

  • Similar technological transitions
  • Pattern repetitions
  • Lessons from history

4. Systemic Interactions

Cross-Domain Effects

  • How changes in one domain affect others
  • Cascading impacts
  • Feedback loops
  • Emergent properties

Equilibrium Shifts

  • New balances forming
  • Destabilized systems
  • Adaptation patterns

Power Dynamics

  • Authority shifts
  • Control mechanisms
  • Resource allocation

---

Application Process

1. Initial Scoping

  • Define specific technology/application
  • Identify primary domains of impact
  • Establish analysis timeframe
  • Define stakeholder scope

2. Systematic Examination

  • Apply core tetrad questions to each domain
  • Document direct and indirect effects
  • Identify cross-domain interactions
  • Map stakeholder impacts

3. Pattern Analysis

  • Identify recurring themes
  • Note unusual effects
  • Document contradictions
  • Map interaction patterns

4. Impact Assessment

  • Evaluate significance of effects
  • Assess probability of outcomes
  • Identify critical uncertainties
  • Define key indicators

5. Documentation

  • Record findings systematically
  • Map relationships
  • Document assumptions
  • Note areas for further study

---

Analysis Template

Technology: [Name]

Enhancement: What it amplifies: - -

Obsolescence: What it displaces: - -

Retrieval: What it brings back: - -

Reversal: What it becomes at extreme: - -

Domain Impacts

DomainEnhancementObsolescenceRetrievalReversal
Economic
Social
Political
Educational
Healthcare
Environmental

Stakeholder Analysis

GroupPositive EffectsNegative EffectsNet Assessment

Temporal Projections

TimeframeMost Likely Effects
Immediate
Short-term
Medium-term
Long-term

Key Uncertainties

1. 2. 3.

---

Example: Smartphone

Enhancement:

  • Communication immediacy
  • Information access
  • Personal documentation (photos, notes)
  • Navigation capability

Obsolescence:

  • Paper maps
  • Point-and-shoot cameras
  • Landline phones
  • Physical newspapers

Retrieval:

  • Oral culture (voice messages, podcasts)
  • Visual culture (image-based communication)
  • Constant connectivity (pre-modern village awareness)

Reversal:

  • Communication enhancement → isolation through screens
  • Information access → attention fragmentation
  • Connection → addiction and dependency
  • Personal documentation → surveillance infrastructure

---

Anti-Patterns

1. The Techno-Utopian

Pattern: Only analyzing enhancement effects. Focusing on what technology enables while ignoring what it destroys, retrieves, or reverses. Why it fails: Creates incomplete analysis that misses critical consequences. Every enhancement has a shadow—ignoring it leads to surprised stakeholders. Fix: Force yourself through all four quadrants. The reversal quadrant is especially important for identifying unintended consequences.

2. The Surface Analysis

Pattern: Identifying immediate effects without tracing systemic implications. "Social media enhances connection" without examining what connection means at scale. Why it fails: First-order effects are obvious; value comes from second and third-order analysis. Surface analysis tells stakeholders nothing they don't already know. Fix: For each effect, ask "and then what?" at least twice. Map cross-domain cascades. Identify feedback loops.

3. The Historical Blindness

Pattern: Analyzing technology in isolation without examining historical parallels. Missing that we've seen similar patterns before. Why it fails: History reveals patterns that inform projections. The printing press, telegraph, and telephone all have lessons for digital technology. Fix: Explicitly identify 2-3 historical analogs. What was enhanced, obsolesced, retrieved, reversed then? What patterns persist?

4. The Stakeholder Collapse

Pattern: Treating all stakeholders as homogeneous. "Users will experience..." without differentiating who wins and who loses. Why it fails: Technology redistributes power unevenly. Analysis that ignores differential impact misses the most important political dimensions. Fix: Segment stakeholders by power position, access, and capability. Analyze each quadrant for each stakeholder class.

5. The Timeframe Conflation

Pattern: Mixing immediate and long-term effects without distinguishing timelines. "This will obsolete X" without specifying when or under what conditions. Why it fails: Timelines matter for planning. Something that becomes obsolete in 20 years requires different strategy than something obsolete next year. Fix: Separate effects by timeframe: immediate (0-2 years), short-term (2-5), medium-term (5-10), long-term (10+).

Integration Points

Inbound:

  • When evaluating new technology
  • When planning technology adoption
  • When analyzing technology policy

Outbound:

  • To decision-making processes
  • To policy recommendations

Complementary:

  • media-meta-analysis: For analyzing discourse about technology
  • Research frameworks: For gathering evidence

Related skills

How it compares

Pick technology-impact for structured pre-adoption consequence analysis; use implementation-focused framework skills when architecture is already decided.

FAQ

What framework does technology-impact use?

technology-impact applies McLuhan's Tetrad of Media Effects, analyzing what a technology enhances, obsoletes, retrieves, and reverses simultaneously. Version 1.0 from jwynia/agent-skills produces structured consequence maps developers use during adoption planning and architecture

When should developers invoke technology-impact?

Developers should invoke technology-impact when evaluating new frameworks, planning platform migrations, or drafting technology policy before committing to vendors or architecture. The skill targets validate-phase scoping where roadmap risk, team skills, and delivery impact need

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.