The Treaty of Detroit for AI

Tim Green

The nightmares have evolved. Once, workers feared the factory floor going silent as machines hummed to life. Today, the anxiety haunts conference rooms and home offices, where knowledge workers refresh job boards compulsively and wonder if their expertise will survive the next quarterly earnings call. The statistics paint a stark picture: around 37 per cent of employees now worry about automation threatening their jobs, a marked increase from just a decade ago.

This isn’t unfounded paranoia. Anthropic CEO Dario Amodei recently predicted that AI could eliminate half of all entry-level white-collar jobs within five years. Meanwhile, 14 per cent of all workers have already been displaced by AI, though public perception inflates this dramatically. Those not yet affected believe 29 per cent have lost their jobs to automation, whilst those who have experienced displacement estimate the rate at 47 per cent. The gap between perception and reality reveals something crucial: the fear itself has become as economically significant as the displacement.

But history offers an unexpected comfort. We’ve navigated technological upheaval before, and certain policy interventions have demonstrably worked. The question isn’t whether automation will reshape knowledge work (it will), but which protections can transform this transition from a zero-sum catastrophe into a managed evolution that preserves human dignity whilst unlocking genuine productivity gains.

The Ghost of Industrial Automation Past

To understand what might work for today’s knowledge workers, we need to examine what actually worked for yesterday’s factory workers. The 1950s through 1970s witnessed extraordinary automation across manufacturing. The term “automation” itself was coined in the 1940s at the Ford Motor Company, initially applied to automatic handling of parts in metalworking processes.

When Unions Made Automation Work

What made this transition manageable wasn’t market magic or technological gradualism. It was policy, particularly the muscular collective bargaining agreements that characterised the post-war period. By the 1950s, more than a third of the American workforce belonged to a union. This union membership helped build the American middle class.

The so-called “Treaty of Detroit” between General Motors and the United Auto Workers in 1950 established a framework that would characterise US labour relations through the 1980s. In exchange for improved wages and benefits (including cost-of-living adjustments, pensions beginning at 125 dollars per month, and health care provisions), the company retained all managerial prerogatives. The compromise was explicit: workers would accept automation’s march in exchange for sharing its productivity gains.

But the Treaty represented more than a simple exchange. It embodied a fundamentally different understanding of technological progress—one where automation’s bounty wasn’t hoarded by shareholders but distributed across the economic system. When General Motors installed transfer machines that could automatically move engine blocks through 500 machining operations, UAW members didn’t riot. They negotiated. The company’s profit margins soared, but so did workers’ purchasing power. A factory worker in 1955 could afford a house, a car, healthcare, and college for their children. That wasn’t market equilibrium—it was conscious policy design.

The Golden Age of Shared Prosperity

The numbers tell an extraordinary story. Critically, collective bargaining performed impressively after World War II, more than tripling weekly earnings in manufacturing between 1945 and 1970. It gained for union workers an unprecedented measure of security against old age, illness and unemployment. Real wages for production workers rose 75 per cent between 1947 and 1973, even as automation eliminated millions of manual tasks. The productivity gains from automation flowed downward, not just upward.

The system worked because multiple protections operated simultaneously. The Wagner Act of 1935 bolstered unions and minimum wage laws, which mediated automation’s displacing effects by securing wage floors and benefits. By the mid-1950s, the UAW fought for a guaranteed annual wage, a demand met in 1956 through Supplemental Unemployment Benefits funded by automotive companies.

These mechanisms mattered because automation didn’t arrive gradually. Between 1950 and 1960, the automobile industry’s output per worker-hour increased by 60 per cent. Entire categories of work vanished—pattern makers, foundry workers, assembly line positions that had employed thousands. Yet unemployment in Detroit remained manageable because displaced workers received benefits, retraining and alternative placement. The social compact held.

The Unravelling

Yet this system contained the seeds of its own decline. The National Labor Relations Act enshrined the right to unionise, but the system meant that unions had to organise each new factory individually rather than by industry. In many European countries, collective bargaining agreements extended automatically to other firms in the same industry, but in the United States, they usually reached no further than a plant’s gates.

This structural weakness became catastrophic when globalisation arrived. Companies could simply build new factories in right-to-work states or overseas, beyond the reach of existing agreements. The institutional infrastructure that had made automation manageable began fragmenting. Between 1975 and 1985, union membership fell by 5 million. By the end of the 1980s, less than 17 per cent of American workers were organised, half the proportion of the early 1950s. The climax came when President Ronald Reagan broke the illegal Professional Air Traffic Controllers Organisation strike in 1981, dealing a major blow to unions.

What followed was predictable. As union density collapsed, productivity and wages decoupled. Between 1973 and 2014, productivity increased by 72.2 per cent whilst median compensation rose only 8.7 per cent. The automation that had once enriched workers now enriched only shareholders. The social compact shattered.

The lesson from this history isn’t that industrial automation succeeded. Rather, it’s that automation’s harms were mitigated when workers possessed genuine structural power, and those harms accelerated when that power eroded. Union decline occurred in every sector within the private sector, not just manufacturing. When the institutional mechanisms that had distributed automation’s gains disappeared, so did automation’s promise.

The Knowledge Worker Predicament

Today’s knowledge workers face automation without the institutional infrastructure that cushioned industrial workers. A Forbes Advisor Survey undertaken in 2023 found that 77 per cent of respondents were “concerned” that AI will cause job loss within the next 12 months, with 44 per cent “very concerned”. A Reuters/Ipsos poll in 2025 found 71 per cent of US adults fear that AI could permanently displace workers. The World Economic Forum’s 2025 Future of Jobs Report indicates that 41 per cent of employers worldwide intend to reduce their workforce in the next five years due to AI automation.

The Anxiety Is Visceral and Immediate

The fear permeates every corner of knowledge work. Copywriters watch ChatGPT produce adequate marketing copy in seconds. Paralegals see document review systems that once required teams now handled by algorithms. Junior financial analysts discover that AI can generate investment reports indistinguishable from human work. Customer service representatives receive termination notices as conversational AI systems assume their roles. The anxiety isn’t abstract—it’s visceral and immediate.

Goldman Sachs predicted in 2023 that 300 million jobs across the United States and Europe could be lost or degraded as a result of AI adoption. McKinsey projects that 30 per cent of work hours could be automated by 2030, with 70 per cent of job skills changing during that same period.

Importantly, AI agents automate tasks, not jobs. Knowledge-work positions are combinations of tasks (some focused on creativity, context and relationships, whilst others are repetitive). Agents can automate repetitive tasks but struggle with tasks requiring judgement, deep domain knowledge or human empathy. If businesses capture all productivity gains from AI without sharing, workers may only produce more for the same pay, perpetuating inequality.

The Pipeline Is Constricting

Research from SignalFire shows Big Tech companies reduced new graduate hiring by 25 per cent in 2024 compared to 2023. The pipeline that once fed young talent into knowledge work careers has begun constricting. Entry-level positions that provided training and advancement now disappear entirely, replaced by AI systems supervised by a skeleton crew of senior employees. The ladder’s bottom rungs are being sawn off.

Within specific industries, anxiety correlates with exposure: 81.6 per cent of digital marketers hold concerns about content writers losing their jobs due to AI’s influence. The International Monetary Fund found that 79 per cent of employed women in the US work in jobs at high risk of automation, compared to 58 per cent of men. The automation wave doesn’t strike evenly—it targets the most vulnerable first.

The Institutional Vacuum

Yet knowledge workers lack the collective bargaining infrastructure that once protected industrial workers. Private sector union density in the United States hovers around 6 per cent. The structural power that enabled the Treaty of Detroit has largely evaporated. When a software engineer receives a redundancy notice, there’s no union representative negotiating severance packages or alternative placement. There’s no supplemental unemployment benefit fund. There’s an outdated résumé and a LinkedIn profile that suddenly needs updating.

The contrast with industrial automation couldn’t be starker. When automation arrived at GM’s factories, workers had mechanisms to negotiate their futures. When automation arrives at today’s corporations, workers have non-disclosure agreements and non-compete clauses. The institutional vacuum is nearly total.

This absence creates a particular cruelty. Knowledge workers invested heavily in their human capital—university degrees, professional certifications, years of skill development. They followed the social script: educate yourself, develop expertise, secure middle-class stability. Now that expertise faces obsolescence at a pace that makes retraining feel futile. A paralegal who spent three years mastering document review discovers their skillset has a half-life measured in months, not decades.

Three Policy Pillars That Actually Work

Despite this bleak landscape, certain policy interventions have demonstrated genuine effectiveness in managing technological transitions.

Re-skilling Guarantees

The least effective approach to worker displacement is the one that dominates American policy discourse: underfunded, voluntary training programmes. The Trade Adjustment Assistance programme, designed to help US workers displaced by trade liberalisation, offers a cautionary tale.

Why American Retraining Fails

Research from Mathematica Policy Research found that the TAA is not effective in terms of increasing employability. TAA participation significantly increased receipt of reemployment services and education, but impacts on productive activity were small. Labour market outcomes for participants were significantly worse during the first two years than for their matched comparison group. In the final year, TAA participants earned about 3,300 dollars less than their comparisons.

The failures run deeper than poor outcomes. The programme operated on a fundamentally flawed assumption: that workers displaced by economic forces could retrain themselves whilst managing mortgage payments, childcare costs and medical bills. The cognitive load of financial precarity makes focused learning nearly impossible. When you’re worried about keeping the lights on, mastering Python becomes exponentially harder.

Coverage proved equally problematic. Researchers found that the TAA covered only 6 per cent of the government assistance provided to workers laid off due to increased Chinese import competition from 1990 to 2007. Of the 88,001 workers eligible in 2019, only 32 per cent received its benefits and services. The programme helped a sliver of those who needed it, leaving the vast majority to navigate displacement alone.

Singapore’s Blueprint for Success

Effective reskilling requires a fundamentally different architecture. The most successful models share several characteristics: universal coverage, immediate intervention, substantial funding, employer co-investment and ongoing income support.

Singapore’s SkillsFuture programme demonstrates what comprehensive reskilling can achieve. In 2024, 260,000 Singaporeans used their SkillsFuture Credit, a 35 per cent increase from 192,000 in 2023. Singaporeans aged 40 and above receive a SkillsFuture Credit top-up of 4,000 Singapore dollars that will not expire. This is in addition to the Mid-Career Enhanced Subsidy, which offers subsidies of up to 90 per cent of course fees.

The genius of SkillsFuture lies in its elimination of friction. Workers don’t navigate byzantine application processes or prove eligibility through exhaustive documentation. The credit exists in their accounts, immediately available. Training providers compete for learners, creating a market dynamic that ensures quality and relevance. The government absorbs the financial risk, freeing workers to focus on learning rather than budgeting.

The programme measures outcomes rigorously. The Training Quality and Outcomes Measurement survey is administered at course completion and six months later. The results speak for themselves. The number of Singaporeans taking up courses designed with employment objectives increased by approximately 20 per cent, from 95,000 in 2023 to 112,000 in 2024. SkillsFuture Singapore-supported learners taking IT-related courses surged from 34,000 in 2023 to 96,000 in 2024. About 1.05 million Singaporeans, or 37 per cent of all Singaporeans, have used their SkillsFuture Credit since 2016.

These aren’t workers languishing in training programmes that lead nowhere. They’re making strategic career pivots backed by state support, transitioning from declining industries into emerging ones with their economic security intact.

Denmark’s Safety Net for Learning

Denmark’s flexicurity model offers another instructive example. The Danish system combines high job mobility with a comprehensive income safety net and active labour market policy. Unemployment benefit is accessible for two years, with compensation rates reaching up to 90 per cent of previous earnings for lower-paid workers.

The Danish approach recognises a truth that American policy ignores: people can’t retrain effectively whilst terrified of homelessness. The generous unemployment benefits create psychological space for genuine skill development. A worker displaced from a manufacturing role can take eighteen months to retrain as a software developer without choosing between education and feeding their family.

Denmark achieves this in combination with low inequality, low unemployment and high-income security. However, flexicurity alone is insufficient. The policy also needs comprehensive active labour market programmes with compulsory participation for unemployment compensation recipients. Denmark spends more on active labour market programmes than any other OECD country.

Success stems from tailor-made initiatives to individual displaced workers and stronger coordination between local level actors. The Danish government runs education and retraining programmes and provides counselling services, in collaboration with unions and employers. Unemployed workers get career counselling and paid courses, promoting job mobility over fixed-position security.

This coordination matters enormously. A displaced worker doesn’t face competing bureaucracies with conflicting requirements. There’s a single pathway from displacement to reemployment, with multiple institutions working in concert rather than at cross-purposes. The system treats worker transition as a collective responsibility, not an individual failing.

France’s Cautionary Tale

France’s Compte Personnel de Formation provides another model, though with mixed results. Implemented in 2015, the CPF is the only example internationally of an individual learning account in which training rights accumulate over time. However, in 2023, 1,335,900 training courses were taken under the CPF, down 28 per cent from 2022. The decline was most marked among users with less than a baccalauréat qualification.

The French experience reveals a critical design flaw. Individual learning accounts without adequate support services often benefit those who need them least. Highly educated workers already possess the cultural capital to navigate training systems, identify quality programmes and negotiate with employers. Less educated workers face information asymmetries and status barriers that individual accounts can’t overcome alone.

The divergence in outcomes reveals a critical insight: reskilling guarantees only work when they’re adequately funded, easily accessible, immediately available and integrated with income support. Programmes that require workers to navigate bureaucratic mazes whilst their savings evaporate tend to serve those who need them least.

Collective Bargaining Clauses

The second pillar draws directly from industrial automation’s most successful intervention: collective bargaining that gives workers genuine voice in how automation is deployed.

Hollywood’s Blueprint

The most prominent recent example comes from Hollywood. In autumn 2023, the Writers Guild of America ratified a new agreement with the Alliance of Motion Picture and Television Producers after five months of stopped work. The contract may be the first major union-management agreement regulating artificial intelligence across an industry.

The WGA agreement establishes several crucial principles. Neither traditional AI nor generative AI is a writer, so no AI-produced material can be considered literary material. If a company provides generative AI content to a writer as the basis for a script, the AI content is not considered “assigned materials” or “source material” and would not disqualify the writer from eligibility for separated rights. This means the writer will be credited as the first writer, affecting writing credit, residuals and compensation.

These provisions might seem technical, but they address something fundamental: who owns the value created through human-AI collaboration? In the absence of such agreements, studios could have generated AI scripts and paid writers minimally to polish them, transforming high-skill creative work into low-paid editing. The WGA prevented this future by establishing that human creativity remains primary.

Worker Agency in AI Deployment

Critically, the agreement gives writers genuine agency. A producing company cannot require writers to use AI software. A writer can choose to use generative AI, provided the company consents and the writer follows company policies. The company must disclose if any materials given to the writer were AI-generated.

This disclosure requirement matters enormously. Without it, writers might unknowingly build upon AI-generated foundations, only to discover later that their work’s legal status is compromised. Transparency creates the foundation for genuine choice.

The WGA reserved the right to assert that exploitation of writers’ material to train AI is prohibited. In addition, companies agreed to meet with the Guild to discuss their use of AI. These ongoing conversation mechanisms prevent AI deployment from becoming a unilateral management decision imposed on workers after the fact.

As NewsGuild president Jon Schleuss noted, “The Writers Guild contract helps level up an area that previously no one really has dealt with in a union contract. It’s a really good first step in what’s probably going to be a decade-long battle to protect creative individuals from having their talent being misused or replaced by generative AI.”

European Innovations in Worker Protection

Denmark provides another model through the Hilfr2 agreement concluded in 2024 between cleaning platform Hilfr and trade union 3F. The agreement explicitly addresses concerns arising from AI use, including transparency, accountability and workers’ rights. Platform workers—often excluded from traditional labour protections—gained concrete safeguards through collective action.

The Teamsters agreement with UPS in 2023 curtails surveillance in trucks and prevents potential replacement of workers with automated technology. The contract doesn’t prohibit automation, but establishes that management cannot deploy it unilaterally. Before implementing driver-assistance systems or route optimisation algorithms, UPS must negotiate impacts with the union. Workers get advance notice, training and reassignment rights.

These agreements share a common structure: they don’t prohibit automation, but establish clear guardrails around its deployment and ensure workers share in productivity gains. They transform automation from something done to workers into something negotiated with them.

Regulatory Frameworks Create Leverage

In Europe, broader regulatory frameworks support collective bargaining on AI. The EU’s AI Act entered into force in August 2024, classifying AI in “employment, work management and access to self-employment” as a high-risk AI system. This classification triggers stringent requirements around risk management, data governance, transparency and human oversight.

The regulatory designation creates legal leverage for unions. When AI in employment contexts is classified as high-risk, unions can demand documentation about how systems operate, what data they consume and what impacts they produce. The information asymmetry that typically favours management narrows substantially.

In March 2024, UNI Europa and Friedrich-Ebert-Stiftung created a database of collective agreement clauses regarding AI and algorithmic management negotiation. The database catalogues approaches from across Europe, allowing unions to learn from each other’s innovations. A clause that worked in German manufacturing might adapt to French telecommunications or Spanish logistics.

At the end of 2023, the American Federation of Labor and Congress of Industrial Organizations and Microsoft announced a partnership to discuss how AI should address workers’ needs and include their voices in its development. This represents the first agreement focused on AI between a labour organisation and a technology company.

The Microsoft-AFL-CIO partnership remains more aspirational than binding, but it signals recognition from a major technology firm that AI deployment requires social license. Microsoft gains legitimacy; unions gain influence over AI development trajectories. Whether this partnership produces concrete worker protections remains uncertain, but it acknowledges that AI isn’t purely a technical question—it’s a labour question.

Germany’s Institutional Worker Voice

Germany’s Works Constitution Act demonstrates how institutional mechanisms can give workers voice in automation decisions. Worker councils have participation rights in decisions about working conditions or dismissals. Proposals to alter production techniques by introducing automation must pass through worker representatives who evaluate impacts on workers.

If a company intends to implement AI-based software, it must consult with the works council and find agreement prior to going live, under Section 87 of the German Works Constitution Act. According to Section 102, the works council must be consulted before any dismissal. A notice of termination given without the works council being heard is invalid.

These aren’t advisory consultations that management can ignore. They’re legally binding processes that give workers substantive veto power over automation decisions. A German manufacturer cannot simply announce that AI will replace customer service roles. The works council must approve, and if approval isn’t forthcoming, the company must modify its plans.

Sweden’s Transition Success Story

Sweden’s Job Security Councils offer perhaps the most comprehensive model of social partner collaboration on displacement. The councils are bi-partite social partner bodies in charge of transition agreements, career guidance and training services under strict criteria set in collective agreements, without government involvement. About 90 per cent of workers who receive help from the councils find new jobs within six months to two years.

Trygghetsfonden covers blue-collar workers, whilst TRR Trygghetsrådet covers 850,000 white-collar employees. According to TRR, in 2016, 88 per cent of redundant employees using TRR services found new jobs. As of 2019, 9 out of 10 active job-seeking clients found new jobs, studies or became self-employed within seven months. Among the clients, 68 per cent have equal or higher salaries than the jobs they were forced to leave.

These outcomes dwarf anything achieved by market-based approaches. Swedish workers displaced by automation don’t compete individually for scarce positions. They receive coordinated support from institutions designed explicitly to facilitate transitions. The councils work because they intervene immediately after layoffs and have financial resources that public re-employment offices cannot provide. Joint ownership by unions and employers lends the councils high legitimacy. They cooperate with other institutions and can offer education, training, career counselling and financial aid, always tailored to individual needs.

The Swedish model reveals something crucial: when labour and capital jointly manage displacement, outcomes improve dramatically for both. Companies gain workforce flexibility without social backlash. Workers gain security without employment rigidity. It’s precisely the bargain that made the Treaty of Detroit function.

AI Usage Covenants

The third pillar involves establishing clear contractual and regulatory frameworks governing how AI is deployed in employment contexts.

US Federal Contractor Guidance

On 29 April 2024, the Department of Labour’s Office of Federal Contract Compliance Programmes released guidance to federal contractors regarding AI use in employment practices. The guidance reminds contractors of existing legal obligations and potentially harmful effects of AI on employment decisions if used improperly.

The guidance informs federal contractors that using automated systems, including AI, does not prevent them from violating federal equal employment opportunity and non-discrimination obligations. Recognising that “AI has the potential to embed bias and discrimination into employment decision-making processes,” the guidance advises contractors to ensure AI systems are designed and implemented properly to prevent and mitigate inequalities.

This represents a significant shift in regulatory posture. For decades, employment discrimination law focused on intentional bias or demonstrable disparate impact. AI systems introduce a new challenge: discrimination that emerges from training data or algorithmic design choices, often invisible to the employers deploying the systems. The Department of Labour’s guidance establishes that ignorance provides no defence—contractors remain liable for discriminatory outcomes even when AI produces them.

Europe’s Comprehensive AI Act

The EU’s AI Act, which entered into force on 1 August 2024, takes a more comprehensive approach. Developers of AI technologies are subject to stringent risk management, data governance, transparency and human oversight obligations. The Act classifies AI in employment as a high-risk AI system, triggering extensive compliance requirements.

These requirements aren’t trivial. Developers must conduct conformity assessments, maintain technical documentation, implement quality management systems and register their systems in an EU database. Deployers must conduct fundamental rights impact assessments, ensure human oversight and maintain logs of system operations. The regulatory burden creates incentives to design AI systems with worker protections embedded from inception.

State-Level Innovation in America

Colorado’s Anti-Discrimination in AI Law imposes different obligations on developers and deployers of AI systems. Developers and deployers using AI in high-risk use cases are subject to higher standards, with high-risk areas including consequential decisions in education, employment, financial services, healthcare, housing and insurance.

Colorado’s law introduces another innovation: an obligation to conduct impact assessments before deploying AI in high-risk contexts. These assessments must evaluate potential discrimination, establish mitigation strategies and document decision-making processes. The law creates an audit trail that regulators can examine when discrimination claims emerge.

California’s Consumer Privacy Protection Agency issued draft regulations governing automated decision-making technology under the California Consumer Privacy Act. The draft regulations propose granting consumers (including employees) the right to receive pre-use notice regarding automated decision-making technology and to opt out of certain activities.

The opt-out provision potentially transforms AI deployment in employment. If workers can refuse algorithmic management, employers must maintain parallel human-centred processes. This requirement prevents total algorithmic domination whilst creating pressure to design AI systems that workers actually trust.

Building Corporate Governance Structures

Organisations should implement governance structures assigning responsibility for AI oversight and compliance, develop AI policies with clear guidelines, train staff on AI capabilities and limitations, establish audit procedures to test AI systems for bias, and plan for human oversight of significant AI-generated decisions.

These governance structures work best when they include worker representation. An AI ethics committee populated entirely by executives and technologists will miss impacts that workers experience daily. Including union representatives or worker council members in AI governance creates feedback loops that surface problems before they metastasise.

More than 200 AI-related laws have been introduced in state legislatures across the United States. The proliferation creates a patchwork that can be difficult to navigate, but it also represents genuine experimentation with different approaches to AI governance. California’s focus on transparency, Colorado’s emphasis on impact assessments, and Illinois’s regulations around AI in hiring each test different mechanisms for protecting workers. Eventually, successful approaches will influence federal legislation.

What Actually Mitigates the Fear

Having examined the evidence, we can now answer the question posed at the outset: which policies best mitigate existential fears among knowledge workers whilst enabling responsible automation?

Piecemeal Interventions Don’t Work

The data points to an uncomfortable truth: piecemeal interventions don’t work. Voluntary training programmes with poor funding fail. Individual employment contracts without collective bargaining power fail. Regulatory frameworks without enforcement mechanisms fail. What works is a comprehensive system operating on multiple levels simultaneously.

The most effective systems share several characteristics. First, they provide genuine income security during transitions. Danish flexicurity and Swedish Job Security Councils demonstrate that workers can accept automation when they won’t face destitution whilst retraining. The psychological difference between retraining with a safety net and retraining whilst terrified of poverty cannot be overstated. Fear shrinks cognitive capacity, making learning exponentially harder.

Procedural Justice Matters

Second, they ensure workers have voice in automation decisions through collective bargaining or worker councils. The WGA contract and German works councils show that procedural justice matters as much as outcomes. Workers can accept significant workplace changes when they’ve participated in shaping those changes. Unilateral management decisions breed resentment and resistance even when objectively reasonable.

Third, they make reskilling accessible, immediate and employer-sponsored. Singapore’s SkillsFuture demonstrates that when training is free, immediate and tied to labour market needs, workers actually use it. Programmes that require workers to research training providers, evaluate programme quality, arrange financing and coordinate schedules fail because they demand resources that displaced workers lack.

Legal Frameworks Prevent the Worst Abuses

Fourth, they establish clear legal frameworks around AI deployment in employment contexts. The EU AI Act and various US state laws create baseline standards that prevent the worst abuses. Without such frameworks, AI deployment becomes a race to the bottom, with companies competing on how aggressively they can eliminate labour costs.

Fifth, and perhaps most importantly, they ensure workers share in productivity gains. If businesses capture all productivity gains from AI without sharing, workers will only produce more for the same pay. The Treaty of Detroit’s core bargain (accept automation in exchange for sharing gains) remains as relevant today as it was in 1950.

Workers Need Stake in Automation’s Upside

This final point deserves emphasis. When automation increases productivity by 40 per cent but wages remain flat, workers experience automation as pure extraction. They produce more value whilst receiving identical compensation—a transfer of wealth from labour to capital. No amount of retraining programmes or worker councils will make this palatable. Workers need actual stake in automation’s upside.

The good news is that 74 per cent of workers say they’re willing to learn new skills or retrain for future jobs. Nine in 10 companies planning to use AI in 2024 stated they were likely to hire more workers as a result, with 96 per cent favouring candidates demonstrating hands-on experience with AI. The demand for AI-literate workers exists; what’s missing is the infrastructure to create them.

The Implementation Gap

Yet a 2024 Boston Consulting Group study demonstrates the difficulties: whilst 89 per cent of respondents said their workforce needs improved AI skills, only 6 per cent said they had begun upskilling in “a meaningful way.” The gap between intention and implementation remains vast.

Why the disconnect? Because corporate reskilling requires investment, coordination and patience—all scarce resources in shareholder-driven firms obsessed with quarterly earnings. Training workers for AI-augmented roles might generate returns in three years, but executives face performance reviews in three months. The structural incentives misalign catastrophically.

Corporate Programmes Aren’t Enough

Corporate reskilling programmes provide some hope. PwC has implemented a 3 billion dollar programme for upskilling and reskilling. Amazon launched an optional upskilling programme investing over 1.2 billion dollars. AT&T’s partnership with universities has retrained hundreds of thousands of employees. Siemens’ digital factory training programmes combine conventional manufacturing knowledge with AI and robotics expertise.

These initiatives matter, but they’re insufficient. They reach workers at large, prosperous firms with margins sufficient to fund extensive training. Workers at small and medium enterprises, in declining industries or in precarious employment receive nothing. The pattern replicates the racial and geographic exclusions that limited the Treaty of Detroit’s benefits to a privileged subset.

However, relying solely on voluntary corporate programmes recreates the inequality that characterised industrial automation’s decline. Workers at large, profitable technology companies receive substantial reskilling support. Workers at smaller firms, in declining industries or in precarious employment receive nothing. The pattern replicates the racial and geographic exclusions that limited the Treaty of Detroit’s benefits to a privileged subset.

The Two-Tier System

We’re creating a two-tier system: knowledge workers at elite firms who surf the automation wave successfully, and everyone else who drowns. This isn’t just unjust—it’s economically destructive. An economy where automation benefits only a narrow elite will face consumption crises as the mass market hollows out.

Building the Infrastructure of Managed Transition

Today’s knowledge workers face challenges that industrial workers never encountered. The pace of technological change is faster. The geographic dispersion of work is greater. The decline of institutional labour power is more advanced. Yet the fundamental policy challenge remains the same: how do we share the gains from technological progress whilst protecting human dignity during transitions?

Multi-Scale Infrastructure

The answer requires building institutional infrastructure that currently doesn’t exist. This infrastructure must operate at multiple scales simultaneously—individual, organisational, sectoral and national.

At the individual level, workers need portable benefits that travel with them regardless of employer. Health insurance, retirement savings and training credits should follow workers through career transitions rather than evaporating at each displacement. Singapore’s SkillsFuture Credit provides one model; several US states have experimented with portable benefit platforms that function regardless of employment status.

At the organisational level, companies need frameworks for responsible AI deployment. These frameworks should include impact assessments before implementing AI in employment contexts, genuine worker participation in automation decisions, and profit-sharing mechanisms that distribute productivity gains. The WGA contract demonstrates what such frameworks might contain; Germany’s Works Constitution Act shows how to institutionalise them.

Sectoral and National Solutions

At the sectoral level, industries need collective bargaining structures that span employers. The Treaty of Detroit protected auto workers at General Motors, but it didn’t extend to auto parts suppliers or dealerships. Today’s knowledge work increasingly occurs across firm boundaries—freelancers, contractors, gig workers, temporary employees. Protecting these workers requires sectoral bargaining that covers everyone in an industry regardless of employment classification.

At the national level, countries need comprehensive active labour market policies that treat displacement as a collective responsibility. Denmark and Sweden demonstrate what’s possible when societies commit resources to managing transitions. These systems aren’t cheap—Denmark spends more on active labour market programmes than any OECD nation—but they’re investments that generate returns through social stability and economic dynamism.

Concrete Policy Proposals

Policymakers could consider extending unemployment insurance for all AI-displaced workers to allow sufficient time for workers to acquire new certifications. The current 26-week maximum in most US states barely covers job searching, let alone substantial retraining. Extending benefits to 18 or 24 months for workers pursuing recognised training programmes would create space for genuine skill development.

Wage insurance, especially for workers aged 50 and older, could support workers where reskilling isn’t viable. A 58-year-old mid-level manager displaced by AI might reasonably conclude that retraining as a data scientist isn’t practical. Wage insurance that covers a portion of earnings differences when taking a lower-paid position acknowledges this reality whilst keeping workers attached to the labour force.

An “AI Adjustment Assistance” programme would establish eligibility for workers affected by AI. This would mirror the Trade Adjustment Assistance programme for trade displacement but with the design failures corrected: universal coverage for all AI-displaced workers, immediate benefits without complex eligibility determinations, generous income support during retraining, and employer co-investment requirements.

Apprenticeships and Legal Protections

AI response legislation could encourage registered apprenticeships that align with good jobs. Registered apprenticeships appear to be the strategy most poised to train workers for new AI jobs. South Carolina’s simplified 1,000 dollar per apprentice per year tax incentive has helped boost apprenticeships with potential for national scale. Expanding this model nationally whilst ensuring apprenticeships lead to family-sustaining wages would create pathways from displacement to reemployment.

The No Robot Bosses Act, proposed in the United States, would prohibit employers from relying exclusively on automated decision-making systems in employment decisions such as hiring or firing. The bill would require testing and oversight of decision-making systems to ensure they do not have discriminatory impact on workers. This legislation addresses a crucial gap: current anti-discrimination law struggles with algorithmic bias because traditional doctrines assume human decision-makers.

Enforcement Must Have Teeth

Critically, these policies must include enforcement mechanisms with real teeth. Regulations without enforcement become suggestions. The EU AI Act creates substantial penalties for non-compliance—up to 7 per cent of global revenue for the most serious violations. These penalties matter because they change corporate calculus. A fine large enough to affect quarterly earnings forces executives to take compliance seriously.

The World Economic Forum estimates that by 2025, 50 per cent of all employees will need reskilling due to adopting new technology. The Society for Human Resource Management’s 2025 research estimates that 19.2 million US jobs face high or very high risk of automation displacement. The scale of the challenge demands policy responses commensurate with its magnitude.

The Growing Anxiety-Policy Gap

Yet current policy remains woefully inadequate. A 2024 Gallup poll found that nearly 25 per cent of workers worry that their jobs can become obsolete because of AI, up from 15 per cent in 2021. In the same study, over 70 per cent of chief human resources officers predicted AI would replace jobs within the next three years. The gap between worker anxiety and policy response yawns wider daily.

A New Social Compact

What’s needed is nothing short of a new social compact for the age of AI. This compact must recognise that automation isn’t inevitable in its current form; it’s a choice shaped by policy, power and institutional design. The Treaty of Detroit wasn’t a natural market outcome; it was the product of sustained organising, political struggle and institutional innovation. Today’s knowledge workers need similar infrastructure.

This infrastructure must include universal reskilling guarantees that don’t require workers to bankrupt themselves whilst retraining. It must include collective bargaining rights that give workers genuine voice in how AI is deployed. It must include AI usage covenants that establish clear legal frameworks around employment decisions. And it must include mechanisms to ensure workers share in the productivity gains that automation generates.

Political Will Over Economic Analysis

The pathway forward requires political courage. Extending unemployment benefits costs money. Supporting comprehensive reskilling costs money. Enforcing AI regulations costs money. These investments compete with other priorities in constrained budgets. Yet the alternative—allowing automation to proceed without institutional guardrails—costs far more through social instability, wasted human potential and economic inequality that undermines market functionality.

The existential fear that haunts today’s knowledge workers isn’t irrational. It’s a rational response to a system that currently distributes automation’s costs to workers whilst concentrating its benefits with capital. The question isn’t whether we can design better policies; we demonstrably can, as the evidence from Singapore, Denmark, Sweden and even Hollywood shows. The question is whether we possess the political will to implement them before the fear itself becomes as economically destructive as the displacement it anticipates.

The Unavoidable First Step

History suggests the answer depends less on economic analysis than on political struggle. The Treaty of Detroit emerged not from enlightened management but from workers who shut down production until their demands were met. The WGA contract came after five months of picket lines, not conference room consensus. The Danish flexicurity model reflects decades of social democratic institution-building, not technocratic optimisation.

Knowledge workers today face a choice: organise collectively to demand managed transition, or negotiate individually from positions of weakness. The policies that work share a common prerequisite: workers powerful enough to demand them. Building that power remains the unavoidable first step toward taming automation’s storm. Everything else is commentary.

References & Sources

  1. AIPRM. (2024). “50+ AI Replacing Jobs Statistics 2024.” https://www.aiprm.com/ai-replacing-jobs-statistics/

  2. Center for Labor and a Just Economy at Harvard Law School. (2024). “Worker Power and the Voice in the AI Response Report.” https://clje.law.harvard.edu/app/uploads/2024/01/Worker-Power-and-the-Voice-in-the-AI-Response-Report.pdf

  3. Computer.org. (2024). “Reskilling for the Future: Strategies for an Automated World.” https://www.computer.org/publications/tech-news/trends/reskilling-strategies

  4. CORE-ECON. “Application: Employment security and labour market flexibility in Denmark.” https://books.core-econ.org/the-economy/macroeconomics/02-unemployment-wages-inequality-10-application-labour-market-denmark.html

  5. Emerging Tech Brew. (2023). “The WGA contract could be a blueprint for workers fighting for AI rules.” https://www.emergingtechbrew.com/stories/2023/10/06/wga-contract-ai-unions

  6. Encyclopedia.com. “General Motors-United Auto Workers Landmark Contracts.” https://www.encyclopedia.com/history/encyclopedias-almanacs-transcripts-and-maps/general-motors-united-auto-workers-landmark-contracts

  7. Equal Times. (2024). “Trade union strategies on artificial intelligence and collective bargaining on algorithms.” https://www.equaltimes.org/trade-union-strategies-on?lang=en

  8. Eurofound. (2024). “Collective bargaining on artificial intelligence at work.” https://www.eurofound.europa.eu/en/publications/all/collective-bargaining-on-artificial-intelligence-at-work

  9. European Parliament. (2024). “Addressing AI risks in the workplace.” https://www.europarl.europa.eu/RegData/etudes/BRIE/2024/762323/EPRS_BRI(2024)762323_EN.pdf

  10. Final Round AI. (2025). “AI Job Displacement 2025: Which Jobs Are At Risk?” https://www.finalroundai.com/blog/ai-replacing-jobs-2025

  11. Growthspace. (2024). “Upskilling and Reskilling in 2024.” https://www.growthspace.com/post/future-of-work-upskilling-and-reskilling

  12. National University. (2024). “59 AI Job Statistics: Future of U.S. Jobs.” https://www.nu.edu/blog/ai-job-statistics/

  13. OECD. (2015). “Back to Work Sweden: Improving the Re-employment Prospects of Displaced Workers.” https://www.oecd.org/content/dam/oecd/en/publications/reports/2015/12/back-to-work-sweden_g1g5efbd/9789264246812-en.pdf

  14. OECD. (2024). “Individualising training access schemes: France – the Compte Personnel de Formation.” https://www.oecd.org/en/publications/individualising-training-access-schemes-france-the-compte-personnel-de-formation-personal-training-account-cpf_301041f1-en.html

  15. SEO.ai. (2025). “AI Replacing Jobs Statistics: The Impact on Employment in 2025.” https://seo.ai/blog/ai-replacing-jobs-statistics

  16. SkillsFuture Singapore. (2024). “SkillsFuture Year-In-Review 2024.” https://www.ssg.gov.sg/newsroom/skillsfuture-year-in-review-2024/

  17. TeamStage. (2024). “Jobs Lost to Automation Statistics in 2024.” https://teamstage.io/jobs-lost-to-automation-statistics/

  18. TUAC. (2024). “The Swedish Job Security Councils – A case study on social partners’ led transitions.” https://tuac.org/news/the-swedish-job-security-councils-a-case-study-on-social-partners-led-transitions/

  19. U.S. Department of Labor. “Chapter 3: Labor in the Industrial Era.” https://www.dol.gov/general/aboutdol/history/chapter3

  20. U.S. Government Accountability Office. (2001). “Trade Adjustment Assistance: Trends, Outcomes, and Management Issues.” https://www.gao.gov/products/gao-01-59

  21. U.S. Government Accountability Office. (2012). “Trade Adjustment Assistance: Changes to the Workers Program.” https://www.gao.gov/products/gao-12-953

  22. Urban Institute. (2024). “How Government Can Embrace AI and Workers.” https://www.urban.org/urban-wire/how-government-can-embrace-ai-and-workers

  23. Writers Guild of America. (2023). “Artificial Intelligence.” https://www.wga.org/contracts/know-your-rights/artificial-intelligence

  24. Writers Guild of America. (2023). “Summary of the 2023 WGA MBA.” https://www.wgacontract2023.org/the-campaign/summary-of-the-2023-wga-mba

  25. Center for American Progress. (2024). “Unions Give Workers a Voice Over How AI Affects Their Jobs.” https://www.americanprogress.org/article/unions-give-workers-a-voice-over-how-ai-affects-their-jobs/

Tim Green

Tim Green
UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795
Email: [email protected]

2025 yılında 634 deniz arama kurtarma operasyonu gerçekleştirildi

Ulaşım ve Altyapı Bakanı Abdulkadir Uraloğlu, 2025 yılı boyunca Ana Arama Kurtarma Koordinasyon Merkezi tarafından 634 deniz arama kurtarma operasyonu gerçekleştirilerek 7 bin 861 kişinin kurtarıldığını açıkladı. Bakan ayrıca, uydu destekli sistem sayesinde müdahalelerin hızlı bir şekilde gerçekleştirildiğini vurguladı.

AAKKM koordinasyonunda 2025'te 634 deniz arama kurtarma operasyonu gerçekleştirildi

Ulaştırma ve Altyapı Bakanı Abdulkadir Uraloğlu, 2025 yılı boyunca Ana Arama Kurtarma Koordinasyon Merkezi’nin koordinasyonunda 634 deniz arama kurtarma operasyonu gerçekleştirildiğini, 7 bin 861 kişinin sağ bulunduğunu ve 101 kişinin yaralı olarak kurtarıldığını açıkladı. Türkiye, modern uydu destekli sistemler ile arama kurtarma faaliyetlerini hızlandırıyor.

Bingöl'de dijital bağımlılığa 'çelik çomak' molası

Bingöl’ün Genç ilçesinde bir araya gelen gençler, dijital bağımlılığa dikkat çekmek amacıyla geleneksel ‘çelik çomak’ oyununu Murat Nehri kıyısında oynadılar. Büyüklerinin mirasını yaşatmayı amaçlayan gençler, bu etkinlikle hem spor yapıp hem de kültürel bağlarını güçlendirmeyi hedefliyorlar.

English is now a programming language and I have mixed feelings

A few years ago if you said “just describe what you want and the computer will do it” — that was science fiction. Now it’s Tuesday.

I spent last week building 40 browser-based developer tools. Half of them I described in plain English to Claude Code and it just… built them. Components, types, tests, the lot.

The weird part isn’t that it works. It’s how it feels.

There’s this guilt developers know — the “am I even really coding?” feeling. Stack Overflow used to trigger it. AI just cranks it to 11.

But here’s what I actually noticed: the thinking didn’t go away. It moved. Less time on “how do I type this correctly”. More time on “is this the right thing to build at all”.

The English-as-code thing is real. But it’s less like replacing programming and more like the abstractions keep going up. Assembly → C → Python → now this. Each step felt like cheating to someone.

Where do you draw the line between “using tools” and “not really coding”? Or is that even the right question?

OpenClaw Skills: Teaching Your AI Agent New Abilities

Your AI agent is only as capable as the tools it knows about. Out of the box, OpenClaw gives you a solid foundation — file operations, web search, browser control, messaging. But the real power comes from Skills: modular packages that teach your agent entirely new abilities.

Want your agent to post to X (Twitter)? Generate images via DALL-E? Transcribe audio? Manage GitHub issues? There’s a skill for that. And if there isn’t, you can build one in an afternoon.

This guide covers how Skills work, how to install them, how to configure them, and how to create your own.

What Is a Skill?

A Skill is a directory containing a single SKILL.md file. That file has two parts:

  • YAML frontmatter — metadata: name, description, gating rules (what binaries or API keys are required)
  • Instructions — the actual text injected into the agent’s system prompt, describing how to use the tool

When OpenClaw loads, it scans for eligible skills, filters them based on your environment and config, and injects the relevant instructions into the agent’s context. From that point on, your agent knows how to use that tool — no code changes, no restarts (for new sessions).

Skills follow the AgentSkills spec, which means they’re portable across compatible agent runtimes. A skill built for OpenClaw can also work with other Pi-compatible agents.

Where Skills Live

OpenClaw looks for skills in three places, in order of precedence:

  1. Workspace skills — <workspace>/skills/ (your agent’s workspace folder)
  2. Managed/local skills — ~/.openclaw/skills/
  3. Bundled skills — shipped with OpenClaw itself

If the same skill name appears in multiple locations, the higher-precedence copy wins. This means you can override a bundled skill by placing a modified version in your workspace — without touching the install.

In multi-agent setups, workspace skills are agent-specific (each agent has its own workspace), while ~/.openclaw/skills/ is shared across all agents on that machine.

Finding and Installing Skills from ClawHub

ClawHub is the public registry for OpenClaw skills. Browse it to discover what the community has built.

Installing a skill is one command:

# Install a skill into your workspace
clawhub install <skill-slug>

# Update all installed skills
clawhub update --all

# Sync (scan local skills + publish updates)
clawhub sync --all

By default, clawhub install drops the skill into ./skills/ under your current working directory (falling back to your configured workspace). OpenClaw picks it up as a workspace skill on the next new session.

Treat third-party skills as untrusted code. Read the SKILL.md before enabling — it gets injected into your agent’s system prompt, and malicious instructions could influence behavior. Prefer sandboxed runs for skills that touch sensitive data.

Skill Gating: What Gets Loaded and When

Not every skill is eligible on every machine. OpenClaw uses gating rules in the skill’s frontmatter to decide what loads:

---
name: openai-image-gen
description: "Batch-generate images via OpenAI Images API."
metadata: {"openclaw": {"requires": {"bins": ["node"], "env": ["OPENAI_API_KEY"]}}}
---

Gating options in metadata.openclaw.requires:

  • bins — all listed binaries must exist on PATH
  • anyBins — at least one must exist on PATH
  • env — env variable must be set (or provided via config)
  • config — a key in openclaw.json must be truthy (e.g. browser.enabled)

Other useful flags:

  • always: true — skip all other gates and always include this skill
  • os — limit to specific platforms (darwin, linux, win32)
  • primaryEnv — the main API key this skill needs (used for config UI)

If a skill’s requirements aren’t met, it silently drops out of the eligible set. Your agent won’t see broken skill instructions — it just won’t have that skill available.

Configuring Skills

Some skills need API keys or custom config. Set these in ~/.openclaw/openclaw.json under skills.entries:

{
  "skills": {
    "entries": {
      "openai-image-gen": {
        "enabled": true,
        "apiKey": { "source": "env", "provider": "default", "id": "OPENAI_API_KEY" }
      },
      "my-custom-skill": {
        "enabled": true,
        "env": {
          "MY_TOOL_API_KEY": "sk-..."
        },
        "config": {
          "endpoint": "https://api.myservice.com",
          "model": "fast"
        }
      }
    }
  }
}

Key rules:

  • enabled: false disables a skill even if it’s bundled and eligible
  • env values are injected only if the variable isn’t already in the environment
  • apiKey is a shorthand for the skill’s primary API key — supports plaintext or a SecretRef object
  • Skill names with hyphens must be quoted in JSON5

If you only want specific bundled skills to load, use skills.allowBundled as an allowlist. Workspace and managed skills are unaffected.

Per-Agent vs Shared Skills

When running multiple agents on one machine, skills placement determines scope:

  • Per-agent skills → <workspace>/skills/ — only that agent sees them
  • Shared skills → ~/.openclaw/skills/ — all agents on the machine see them
  • Extra shared folders → configure via skills.load.extraDirs in openclaw.json

This matters when you have a general-purpose agent and a specialized one. Your X-posting skill might live in the marketing agent’s workspace only — your DevOps agent doesn’t need to know about it.

How to Write Your Own Skill

Creating a skill is simpler than it sounds. You need one file:

skills/
  my-weather-skill/
    SKILL.md

A minimal SKILL.md:

---
name: my-weather-skill
description: Get current weather via wttr.in API. Use when the user asks about weather or temperature.
---

## my-weather-skill

To get weather for a location, run:

  curl -s "https://wttr.in/LOCATION?format=3"

Replace LOCATION with a city name or coordinates. Returns a one-line weather summary. Use the exec tool to run this command.

Drop this in <workspace>/skills/my-weather-skill/SKILL.md and start a new session. Your agent will now know how to fetch weather on request.

Advanced: Gating and Environment Injection

If your skill needs an API key or a specific binary, add gating metadata:

---
name: my-api-skill
description: Interact with MyService API for data lookups.
metadata: {"openclaw": {"requires": {"env": ["MY_API_KEY"]}, "primaryEnv": "MY_API_KEY"}}
---

## my-api-skill

You have access to the MyService API via the MY_API_KEY environment variable.

To query data:
  curl -H "Authorization: Bearer $MY_API_KEY" https://api.myservice.com/data

OpenClaw will only load this skill if MY_API_KEY is set — either in the environment or via skills.entries.my-api-skill.apiKey in your config.

Referencing the Skill Directory

Use {baseDir} in your skill instructions to reference the skill folder path. This is useful when your skill includes scripts or assets alongside SKILL.md:

Run the helper script at {baseDir}/run.sh to process files.

Skills vs Plugins: What’s the Difference?

Skills are pure instructions — text injected into the system prompt. They teach the agent how to use existing tools (CLI commands, APIs via curl, shell scripts). No code executes at load time. Zero runtime overhead.

Plugins are code modules that run alongside the Gateway. They can register new tools as first-class agent functions, add CLI commands, start background services, and hook into the Gateway’s RPC layer. Plugins can also ship skills — a plugin might register a new tool and include a skill that teaches the agent how to invoke it.

Rule of thumb: start with a skill. If the skill needs to do something a shell command can’t handle (complex auth flows, streaming APIs, event-driven behavior), graduate to a plugin.

Token Impact and Performance

Skills inject text into your system prompt. The overhead is deterministic:

  • Base overhead (when ≥1 skill is loaded): ~195 characters
  • Per skill: ~97 characters + the length of name + description + location

OpenClaw snapshots eligible skills when a session starts and reuses that list for subsequent turns. Changes to skills (adding, modifying, removing) take effect on the next new session. The skills watcher can hot-reload the snapshot mid-session when SKILL.md files change — configure this under skills.load.watch.

Keep skill descriptions concise. The description field is what triggers skill selection (the agent reads it to decide whether a skill applies). Clear, specific descriptions reduce noise in the system prompt and improve accuracy.

Real-World Examples: Skills in Action

X (Twitter) Posting Agent

The xurl skill teaches the agent how to use the xurl CLI for authenticated X API calls. Install it, configure your API keys, and your agent can draft and post tweets, reply to mentions, and search threads — all from a Slack DM.

GitHub Issue Automation

The gh-issues skill pairs with the gh CLI to let your agent fetch open issues, spawn sub-agents to fix bugs, and open PRs — automatically, on a schedule.

Content Pipeline

Skills can chain: a web_search skill feeds research into an openai-image-gen skill to generate cover art, then a custom Slack-posting skill delivers the finished post. Each skill handles one step; the agent orchestrates the flow.

Getting Started

If you’re new to OpenClaw, start with the complete OpenClaw overview. Once your agent is running:

  1. Browse ClawHub for skills relevant to your workflow
  2. Install one with clawhub install <slug>
  3. Add any required API keys to your config
  4. Start a new session — the agent now has the ability
  5. For custom tools, create a SKILL.md in <workspace>/skills/<name>/

The right skill stack turns your agent from a smart chatbot into a fully operational team member — one that knows how to use your tools, respects your environment, and picks up new abilities as your needs evolve.

Originally published at openclawplaybook.ai. Get The OpenClaw Playbook — $9.99

Building a development organization driven by generative artificial intelligence JAWS 2026 K1

1️⃣ Jeff Barr has driven the AWS news blog for 20 years. His long-term developer advocacy has built a feedback loop between product teams and builders. He continuously maintains the blog to gather developer feedback.
2️⃣ Narrative documents define AWS’s web services vision. He writes documents to ensure product-market fit before software development. Narrative documents are completed before development begins.
3️⃣ Barr has written 3,200 articles documenting service launches. Technical communication drives cloud infrastructure adoption and maintains enterprise transparency. He documents service releases through technical articles.
4️⃣ Barr has visited 14 countries to gather developer insights. Direct customer engagement identifies operational challenges and optimizes the product roadmap. He personally participates in developer events to refine the product roadmap.
5️⃣ Generative AI is changing the software development lifecycle. Internal projects utilize Gen AI to improve developer productivity and maintain safety standards. Generative AI is integrated into internal processes.
6️⃣ Launched Amazon S3 and AWS on March 14, 2006. Tracked milestones to help stakeholders measure the long-term growth of the cloud platform. Recorded key time points to evaluate platform development.
7️⃣ User groups facilitated knowledge exchange among builders. Connected stakeholders to ensure product goals were aligned. Supported the developer community to build scalable systems.
8️⃣ AI-generated images enhanced technical presentations. Included prompts to ensure transparency and reproducibility. Revealed AI involvement and provided input parameters.
9️⃣ Project Mantle identified the value of generative AI. Understood developer workflows to assist in tooling optimization analysis of internal projects to refine AI implementation.
1️⃣0️⃣ Generative AI and development tools evolved daily. Stayed abreast of current developments to maintain a competitive edge in software development. Monitored model releases to integrate emerging technologies.
1️⃣1️⃣ Technological shifts brought operational challenges. Identified skills gaps and conducted targeted training. Assess technical proficiency to address industry transformation.
1️⃣2️⃣ Rapidly changing industry trends. Identify the pace to help organizations adjust product cycles. Use the bullet train analogy to measure AI adoption readiness.
1️⃣3️⃣ Continuous learning mitigates the impact of model updates. Assess individual status to ensure the team keeps up with innovation. Conduct developer surveys to determine tool readiness.
1️⃣4️⃣ Amazon Bedrock provides infrastructure for running models. The platform simplifies AI application building. Use models and inference services through Bedrock.
1️⃣5️⃣ Customization features and safety guardrails protect data. Perform policy checks to ensure enterprise compliance. Apply security protocols to protect customer information.
1️⃣6️⃣ Agentic AI capabilities drive complex application development. Rapid iteration accelerates feature expansion. Utilize Bedrock tools to build autonomous systems.
1️⃣7️⃣ Model catalogs expanded to 277 models in December. Offer diverse options to drive platform adoption. Maintain infrastructure to support model growth.
1️⃣8️⃣ Inference jobs generate varying latency. Optimize GPU resources to improve cost efficiency. Manage computing resources to handle diverse workloads.
1️⃣9️⃣ Job isolation prevents interference between clients. Ensure independent execution to maintain system reliability. Isolate tenant workloads to protect AWS regions’ performance.
2️⃣0️⃣ Tiered service levels offer diverse pricing. Align speed and cost to optimize resource allocation. Choose service tiers based on latency requirements.
2️⃣1️⃣ Model lifecycles require automated resource reclamation. Decommission old models to reduce operational overhead. Monitor model activity to optimize region resources.
2️⃣2️⃣ Model lifecycle management reclaims computing resources from obsolete models. Automated resource allocation prevents waste. Decommission models not used by clients.
2️⃣3️⃣ Project Mantle refactors Bedrock infrastructure. Foundational architecture supports long-term scalability. A senior engineering team modernizes core systems.
2️⃣4️⃣ Traditional development cycles cannot meet market speeds. Align development velocity with market demands to enhance competitiveness. Evaluate development methodologies when behind schedule.
2️⃣5️⃣ Generative AI provides alternatives to manpower expansion. Maintain small teams to reduce communication overhead. Experiment with AI tools to generate productivity.
2️⃣6️⃣ Q Developer and Qiro tools accelerate code generation. Shorter development times demonstrate ROI. Utilize AI to assist in writing unit tests and technical documentation.
2️⃣7️⃣ Gen AI enabled Bedrock to launch within 76 days. Shorten time-to-market for rapid deployment. Utilize AI workflows to meet delivery schedules.
2️⃣8️⃣ Project Mantle supports the publication of 18 models on re:Invent. Infrastructure supports platform expansion. Expand backend systems to accommodate new products.
2️⃣9️⃣ AI integration boosted developer productivity by 20 times. Weekly commits increased from 2 to 40. AI tools were implemented to optimize individual output.
3️⃣0️⃣ Project organization is centralized in monorepo. Centralized code and documentation simplify knowledge management. A single repository structure is used to provide feedback to the model context.
3️⃣1️⃣ Local testing environments are built, removing external dependencies. Developers run full-stack tests on laptops. Local tests are set up to ensure software quality.
3️⃣2️⃣ Automated code generation generates thousands of tests. Code quality is verified through extensive testing. Unit tests are generated with the source code to maintain engineering standards.
3️⃣3️⃣ Future-proofing code requires an AI-friendly development cycle. Code that is easy for the model to understand facilitates iteration. The model is instructed to generate readable syntax.
3️⃣4️⃣ The development cycle achieves hourly code changes. Workflow decomposition accelerates problem-solving. Prompts are given to the model for specific changes.
3️⃣5️⃣ End-to-end tests follow AI code changes. Human review ensures the code safely enters production. Use automated testing to verify logic.
3️⃣6️⃣ Accumulate code for next-day production pushes. Shorten release intervals to deliver business value. Optimize CI/CD pipelines to handle high-frequency commits.
3️⃣7️⃣ Prompt engineering delivers value through specific tasks. Strongly typed languages ​​provide better model information. Use precise instructions to reduce development errors.
3️⃣8️⃣ Strongly typed languages ​​like Rust and Go improve model inference. Structured information ensures outcome quality. Choose languages ​​with clear syntax for AI-assisted development.
3️⃣9️⃣ Gen AI amplifies developer skills. Transform builders into high-performing engineers. Focus on skill acquisition by extending AI capabilities.
4️⃣0️⃣ Workflow separation includes search and fix elements. Isolate exploration and execution to improve prompt accuracy. Use independent instructions to locate logic problems.
4️⃣1️⃣ High-quality prompts build developer confidence. Increase the regularity of development cycles to expand productivity. 4️⃣2️⃣ AI tools produce code of equivalent
quality to human effort. Maintain industry-standard error rates to ensure system reliability. Leverage AI to expand code volume without compromising software quality.
4️⃣3️⃣ Larger code output increases the overall number of errors. A 20x increase in code volume can create downstream operational risks. Monitor critical errors generated in the production environment due to high speed.
4️⃣4️⃣ Traditional testing must be increased to match code volume. Strengthen unit tests and end-to-end tests to reduce risk. Require tools to actively build complete test suites.
4️⃣5️⃣ Test-to-production ratios must expand with AI output. Improve error detection capabilities to prevent faults from reaching customers. Implement smart testing to ensure safe high-speed development.
4️⃣6️⃣ Formal methods use mathematical techniques to prove program correctness. Minimize logical errors to ensure functional correctness. Invest in automated reasoning to find errors missed by traditional testing.
4️⃣7️⃣ Context management impacts model performance. Reduce excessive tools or information to avoid tracking difficulties. Frequently opening new sessions clears context and improves accuracy.
4️⃣8️⃣ Session summarization stores and restores model context. Preserving summary data ensures continuity without sacrificing performance. Use tools to load information only when needed.
4️⃣9️⃣ Loading information on demand prevents preloading overhead. Exercise judgment to ensure the model only receives the data it needs at the moment. Load specific documentation only when requested by the model.
5️⃣0️⃣ Pattern mimicking allows models to replicate modern code. Following updated module patterns ensures repository consistency. Hint at models to use existing patterns in other source code locations.
5️⃣1️⃣ Developer judgment is increasingly important in AI workflows. Long-term built skills ensure high-quality decision-making. Develop personal expertise to effectively guide and validate AI tool outputs.
5️⃣2️⃣ The software building environment is changing for both experienced and junior developers. Understanding career advancement paths helps organizations recruit effective builders. Focus on problem-solving and experience, not just language syntax.
5️⃣3️⃣ Senior developers provide experience and intuition beyond technical skills. Make informed and competent judgments in complex situations to ensure project success. Focus on judgment skills to drive product development.
5️⃣4️⃣ New developers need to be trained with complex systems. Develop judgment through experience to prepare for senior positions. Lead teams through informed decision-making processes.
5️⃣5️⃣ Prompt writing as a new language for expressing ideas. Learn syntax and structure to better communicate with models. Consider instruction writing a core competency in modern software development.
5️⃣6️⃣ Shift-left strategies: Automate QA and build processes. Improve efficiency early to maintain product quality. Ensure every commit passes all configuration tests.
5️⃣7️⃣ Downstream systems face pressure to accelerate output. A 20-fold increase in productivity will put pressure on code repositories and review workflows. Optimize internal processes to handle high-speed AI-assisted output.
5️⃣8️⃣ Code reviews must be scaled to match the merge rate. Avoid developers reviewing excessive code, causing operational bottlenecks. Invest resources to synchronize review speed with generation speed.
5️⃣9️⃣ CI/CD processes need to be triggered frequently to maintain value. Run automated builds to prevent system lag. Ensure the delivery pipeline is as fast as AI-assisted developers.
6️⃣0️⃣ Amdahl’s Law: Identify and optimize system bottlenecks in the architecture. The benefits of improving a single part are limited by the unimproved parts. Balance development speed with downstream processing capacity.
6️⃣1️⃣ Parallel agents generate code independently of developer ideas. They can work without coordination to accelerate the build phase. Foster autonomous agents to handle different layers of the system.
6️⃣2️⃣ Review workload increases fivefold when agents work in parallel. Increase personnel to handle code reviews to prevent delivery bottlenecks. Scalable review capabilities to match AI output.
6️⃣3️⃣ CI/CD systems must process merges and tests at 20x speed. Synchronize downstream processes and deployment speeds to ensure productivity gains. Optimize deployment pipelines to receive high-speed code.
6️⃣4️⃣ Non-developmental software lifecycles require speed optimization. Identify market opportunities involving improved review and CI/CD efficiency. Focus on process improvements to support rapid development.
6️⃣5️⃣ The BMW Group established a serverless CI/CD architecture. Handling 130,000 deployments daily to support 3,000 builders. Implementing a serverless pipeline to scale builds across AWS regions.
6️⃣6️⃣ Multi-region builds allow simultaneous deployments across different operating systems. Covering 1,300 microservices demonstrates enterprise scalability. Maintaining global team pipeline speed using a serverless architecture.
6️⃣7️⃣ Serverless CI/CD operates at the same speed as developers. Documenting architectural details provides best practices for stakeholders. Referencing technical blogs to learn implementation strategies.
6️⃣8️⃣ Decision-making processes must match code generation speed. Accelerating software development requires stakeholders to make decisions 20 times faster. Synchronizing leadership review with technical speed prevents operational bottlenecks.
6️⃣9️⃣ In-person collaboration improves communication within the AI ​​team. Allowing for instant consultation from the same physical location. Co-working optimizes knowledge transfer and problem-solving.
7️⃣0️⃣ Hacker houses represent a lifestyle optimized for maximum productivity. Co-working maximizes development focus. Assess team proximity to determine the best environment for high-productivity projects.
7️⃣1️⃣ Traditional agile models with daily stand-up meetings are becoming less efficient. Weekly meetings are too infrequent for high-speed AI workflows. Redesign development processes to support continuous coordination and rapid iteration.
7️⃣2️⃣ Two-pizza teams must evolve into smaller units. Maintaining one-pizza-size teams reduces communication overhead. Reducing team size increases individual control and functional ownership.
7️⃣3️⃣ As teams shrink, a broader skill set is needed. Each developer manages a wider scope of work and responsibilities. Encourage cross-disciplinary training to ensure builders can handle end-to-end development.
7️⃣4️⃣ Reference manuals and memorization define legacy programming models. Mastering syntax and operators ensures suitability. Beyond static facts, embrace experimental learning in AI environments.
7️⃣5️⃣ Model capabilities are discovered through hands-on exploration. There is no checklist of generative AI strengths and weaknesses. Directly test models to understand their specific utility for business cases.
7️⃣6️⃣ Hands-on exploration reveals model strengths and weaknesses. Directly try out models to find strengths for business cases. Hands-on experience provides a new understanding of limitations.
7️⃣7️⃣ The application philosophy shifts from long-term maintenance to short cycles. Rapidly build software to reduce the need for costly investments. Frequently rebuild applications to align with current customer issues.
7️⃣8️⃣ Disposable code simplifies the software development lifecycle. Long-term code maintenance is no longer enterprise best practice. Treat issue specifications and prompts as durable assets in development.
7️⃣9️⃣ Durable code remains important for microservices. Separate ephemeral application code from long-term infrastructure optimization. Focus engineering efforts on building reusable internal services.
8️⃣0️⃣ Data value increases as application lifespan shortens. Collecting and analyzing information provides an organization with a competitive advantage. Build general-purpose applications that reference and utilize high-value datasets.
8️⃣1️⃣ Generalist skills replace specialized roles in small teams. Adapt to new environments to ensure builders remain resource-sufficient. Develop broad skills to manage end-to-end project challenges.
8️⃣2️⃣ Next-generation skills focus on customer understanding and business cases. Identify user challenge details to drive product-market fit. Focus on stakeholder needs to build effective AI solutions.
8️⃣3️⃣ Communication skills require expressive writing developed for instructions. Use more vocabulary in prompts to produce better results. Practice reading and writing to become an effective communicator for AI tools.
8️⃣4️⃣ Prompt-based development requires high-density word input. Provide more context for models to produce accurate outputs. Write complete instructions to improve software development efficiency.
8️⃣5️⃣ Cooperative skills: Strengthen team connections through physical co-working. Working in the same location improves coordination and speed. Prioritize teamwork to maintain alignment with product goals.
8️⃣6️⃣ Concentration: Technical skills in high-speed environments. Maintain focus to ensure stability amidst tool changes. Allocate time for mental clarification to cope with technology transfer.
8️⃣7️⃣ 15 minutes of continuous learning daily to mitigate the risk of becoming obsolete. Acquire new facts or tool knowledge daily to ensure readiness. Schedule daily training to keep up with industry innovation.
8️⃣8️⃣ Automated code generation: Reduce the need for manual code review. Builders report that AI output meets expectations. Evaluate and validate workflows to identify key areas for human review.
8️⃣9️⃣ Multilingual model support: Remove the English language barrier in software development. Open development to more backgrounds to expand the global talent pool. Use local languages ​​to expand technical engagement and innovation.
9️⃣0️⃣ Prompt engineering uses Markdown and structured rules as its syntax. It shifts from formatted code to natural language guidance to maintain logical standards. Applying markup formats provides a clear sequence for AI tools.
9️⃣1️⃣ Defining problem statements replaces syntax as the primary bottleneck. Developers who communicate effectively gain a competitive advantage. Focus on verbal and written communication to drive technical outcomes.
9️⃣2️⃣ Learning and adaptation are core principles of engineering. Shifting from syntax to expressive instructions ensures long-term career growth. Embrace new methodologies to maintain productivity in changing environments.

https://www.youtube.com/watch?v=r9-ke0c7GsU
[JAWS DAYS 2026] K1 Keynote / Building a Development Organization Led by Generative AI

I Built a Production-Ready Biometric Auth Microservice. Here Are 5 Problems Nobody Warns You About.

Everyone talks about biometric authentication as the future of security. Fingerprint scanning, face recognition, liveness detection… it all sounds elegant in a conference talk or a product demo. Then you actually start building one, and reality shows up uninvited.

I built a biometric authentication microservice from scratch. Not a wrapper around someone else’s API. A standalone, production-ready, multi-tenant service with its own recognition pipeline, anti-spoofing layers, and encryption stack. The goal: offer it as a SaaS product that other applications can plug into.

This post is not a tutorial. I’m not going to walk you through code or tell you which libraries to use. Instead, I want to share 5 real problems I ran into during this process. These are things you won’t find in documentation, Stack Overflow answers, or “Getting Started with Biometrics” blog posts. You only learn them by building.

1. Liveness Detection is Harder Than Face Recognition

Here’s what most people assume: the hard part of biometric auth is recognizing a face. It’s not. Face recognition models are mature, well-documented, and surprisingly accurate even on modest hardware.

The actual hard part? Figuring out whether the face in front of the camera belongs to a living person.

Think about the attack surface for a moment. Someone holds up a photo of the target user. Someone plays a video on their phone screen. Someone prints a high-resolution image and curves it slightly to mimic facial contours. Someone uses a replay attack, feeding a previously captured video stream directly into the system.

Your face recognition model will happily match all of these. It doesn’t care if the face is alive or printed on a piece of paper. That’s not its job.

I treated anti-spoofing as a completely separate engineering layer. Face recognition and liveness detection run as independent steps in my pipeline. Each produces its own confidence score, and both must exceed their respective thresholds for the request to succeed. If either fails, the entire operation is rejected.

This separation was a deliberate architectural decision, not something I bolted on after the first demo. If you’re building any kind of biometric system and you’re treating liveness detection as a “nice to have” or an afterthought, stop and reconsider. It’s a harder problem than recognition itself, and it deserves first-class engineering attention from day one.

2. Why a Layered Architecture is Non-Negotiable

Biometric authentication is not a single feature. It’s a stack of concerns: face detection, recognition, liveness verification, encryption, tenant isolation, compliance logging, and more. Each of these has its own failure modes, its own security implications, and its own performance characteristics.

Early on, I made the decision to design the system as distinct, decoupled layers. Each layer has one job and a clear contract with the next. This is not microservices-for-the-sake-of-microservices. It is security-driven separation of concerns.

The layers, in broad strokes:

  • Input validation and preprocessing. Reject garbage before it reaches anything expensive.
  • Biometric processing. Recognition and liveness as separate sub-layers with independent scoring.
  • Encryption and secure storage. Handles the cryptographic lifecycle of biometric data.
  • Tenant isolation and access control. Ensures one customer’s data never touches another’s.
  • Audit and compliance logging. Records every operation for regulatory requirements.

Why does this matter? Because in a security product, a vulnerability in one layer should not cascade into others. If there’s a bug in how I handle image preprocessing, it should never give an attacker access to encrypted biometric templates. If a tenant isolation check fails, it should never bypass the encryption layer.

There’s a practical benefit too: compliance auditors can review each layer independently. Performance bottlenecks become visible per layer. And when you need to swap out a biometric model for a better one, you don’t have to rewrite your encryption logic.

If your auth system is a monolith where recognition, encryption, and tenant management are tangled together, you are one bug away from a full breach.

3. Encryption is a Lifecycle, Not a Feature

Let me start with the number one rule in cryptography: never roll your own encryption.

This isn’t a suggestion. It’s not a guideline you can bend when you’re feeling clever. Use proven, battle-tested, peer-reviewed cryptographic primitives. If someone tells you they wrote their own encryption algorithm, run.

This rule extends beyond algorithms. Key management, initialization vectors, padding schemes, modes of operation… for all of these, use what the cryptographic community has already built and vetted. The history of security is littered with smart engineers who thought they could do better.

Now, with that foundation in place, here’s the real challenge: biometric data is not a password. If a password leaks, you reset it. If biometric data leaks, the consequences are permanent. You cannot reset someone’s face.

So “encrypt everything” is not a strategy. It’s a starting point. The real questions are: encrypt what, where, when, and how?

I never store raw biometric data. What gets stored is a mathematically transformed, encrypted representation. The transformation is irreversible by design. Even if someone dumps the entire database, they cannot reconstruct the original biometric data from what they find. The goal is not just to encrypt data, but to make leaked data useless.

During comparison operations, decryption happens in a controlled manner: decrypt in memory, perform the match, wipe immediately. Each tenant operates within its own isolated encryption scope. Key management lives entirely separate from application logic.

The lesson: design your encryption strategy around the data lifecycle. Enrollment, storage, comparison, deletion. Each stage carries different risks and requires different protections. “One key encrypts everything” sounds simple because it is. And simple, in this context, means vulnerable.

4. Running ML Models When You Can’t Afford a GPU

Face recognition and anti-spoofing models ideally want GPU acceleration. Inference is faster, throughput is higher, everything feels smoother.

My reality: a VPS under $50/month. Single CPU. Minimal RAM. No GPU.

The easy answer is “you need a GPU.” The more interesting question is: how far can you go without one?

Further than you might think, as it turns out. But it requires deliberate engineering at every level.

Model optimization was the first lever. I evaluated smaller model variants and made conscious precision trade-offs. Not every use case needs the absolute highest accuracy. Choosing a model that’s 98.5% accurate but runs 3x faster on CPU versus one that’s 99.2% accurate but requires a GPU is a valid engineering decision. Context matters.

Memory management was the second. I keep models loaded in memory rather than reloading per request. I avoid redundant copies. Every megabyte counts when you have limited RAM, and a careless memory allocation can turn a working service into an OOM crash.

Request handling was the third. Biometric operations are computationally heavy, so I serialize concurrent requests rather than letting them compete for CPU. A queue with predictable latency is better than parallel execution that degrades unpredictably under load.

The last piece: graceful degradation. Under heavy load, the system reduces throughput rather than crashing. A slower response is always better than no response.

Tight constraints force better engineering decisions. When you have unlimited GPU budget, you can afford to be lazy about optimization. When every CPU cycle and every byte of RAM matters, you think harder about what’s actually necessary. A production-ready biometric auth service can absolutely run on a minimal VPS. You just can’t waste anything.

5. Privacy Regulations Shape Your Architecture

Biometric data is classified as “sensitive personal data” in most jurisdictions. GDPR in Europe, KVKK in Turkey, CCPA in California, and many more. Each comes with its own specific requirements, and none of them are optional.

The temptation is to say “we’ll handle compliance later.” This does not work. Privacy requirements are not features you add on top. They are architectural decisions that affect how you design the system from the ground up.

A few examples:

Data minimization. You should store only the absolute minimum data needed for the operation. If you don’t need to keep a raw image after enrollment, delete it. If you can perform verification with a compact representation instead of a full biometric template, use the compact one.

Consent management. Explicit user consent must be enforced at the API level, not just in the UI. The backend should refuse to process biometric data without a valid consent record.

Right to deletion. When a tenant leaves or a user requests data removal, all biometric data must be irreversibly deleted. Not soft-deleted. Not archived. Destroyed. This means your storage architecture must support true hard deletes.

Audit trail. Every biometric operation must be logged: who processed what data, when, and for what purpose. These logs must be tenant-isolated and tamper-resistant.

I designed all of this into the system from the beginning. Not because I enjoy compliance paperwork, but because retrofitting privacy into an existing architecture is a painful, expensive rewrite. If you’re building anything that handles biometric data, make privacy-by-design your starting principle. Your future self will thank you.

Closing Thoughts

Building a biometric authentication microservice taught me that this space has very little tolerance for shortcuts. “We’ll handle it later” is the most expensive sentence in security engineering.

The five challenges I described are not edge cases. They are core engineering problems that anyone building biometric systems will face:

  1. Liveness detection deserves first-class engineering attention.
  2. Layered architecture is survival, not a luxury.
  3. Encryption is a lifecycle that starts with one rule: never roll your own.
  4. Hardware constraints force better decisions, not worse products.
  5. Privacy compliance is an architectural choice, not a checkbox.

If you’re working on something similar, or considering building biometric capabilities into your product, I’d be happy to discuss approaches. Drop a comment or reach out directly.

And if there’s interest, I may write a follow-up diving deeper into one of these areas.

Filtering a DB using SQL Queries

While practicing SQL, I worked on a movie rental database and tried solving different types of queries using conditions, sorting,limits and pattern matching.

1.Movies with rental rate > $3

SELECT * FROM film WHERE rental_rate > 3;

2.Rental rate > $3 AND replacement cost < $20

SELECT * 
FROM film
WHERE rental_rate > 3 AND replacement_cost < 20;

3.Movies rated ‘PG’ OR rental rate = $0.99

SELECT * FROM film WHERE rating = 'PG' OR rental_rate = 0.99;

4.Top 10 movies by highest rental rate

SELECT * FROM film ORDER BY rental_rate DESC LIMIT 10;

5.Skip first 5, fetch next 3 (ascending rental rate)

SELECT * FROM film ORDER BY rental_rate ASC LIMIT 3 OFFSET 5;

6.First 5 movies sorted by title

SELECT * FROM film ORDER BY title ASC LIMIT 5;

7.Skip first 10, fetch next 3 (highest replacement cost)

SELECT * FROM film ORDER BY replacement_cost DESC LIMIT 3 OFFSET 10;

8.Top 5 movies with highest replacement cost (skip most expensive)

SELECT * FROM film ORDER BY replacement_cost DESC LIMIT 5 OFFSET 1;

9.Rental duration between 3 and 7 days

SELECT * FROM film WHERE rental_duration BETWEEN 3 AND 7;

10.Rentals between two dates

SELECT * FROM rental WHERE rental_date BETWEEN '2005-05-01' AND '2005-06-01';

11.Title starts with ‘A’ and ends with ‘e’

SELECT * FROM film WHERE title LIKE 'A%e';

12.Title starts with ‘A’ or ‘B’ and ends with ‘s’

SELECT * FROM film WHERE (title LIKE 'A%s' OR title LIKE 'B%s');

13.Title contains “Man”, “Men”, or “Woman”

SELECT * FROM film WHERE title LIKE '%Man%' OR title LIKE '%Men%' OR title LIKE '%Woman%';

14.Title starts with ‘The’

SELECT * FROM film WHERE title LIKE 'The%';

15.Title contains “Love” or “Hate”

SELECT * FROM film WHERE title LIKE '%Love%' OR title LIKE '%Hate%';

16.Titles ending with ‘er’, ‘or’, or ‘ar’ (top 5)

SELECT * FROM film WHERE title LIKE '%er' OR title LIKE '%or' OR title LIKE '%ar' LIMIT 5;

17.Movies released in 2006, rental rate 2.99 or 3.99, title starts with ‘S’

SELECT title, rental_rate, release_year FROM film WHERE release_year = 2006 AND rental_rate IN (2.99, 3.99) AND title LIKE 'S%' LIMIT 5;

18.Movies with rental rate 4.99 and replacement cost > 20

SELECT * FROM film WHERE rental_rate = 4.99 AND replacement_cost > 20;

19.Movies with rental rate 0.99 OR rating ‘PG-13’

SELECT * FROM film WHERE rental_rate = 0.99 OR rating = 'PG-13';

20.Movies with rating in (‘G’, ‘PG’, ‘PG-13’)

SELECT * FROM film WHERE rating IN ('G', 'PG', 'PG-13');

21.Movies with rental rate between $2 and $4

SELECT * FROM film WHERE rental_rate BETWEEN 2 AND 4;

22.Movies where special_features is NULL

SELECT * FROM film WHERE special_features IS NULL;

23.Customers without email

SELECT * FROM customer WHERE email IS NULL;

24.Movies with rental duration > 7 days

SELECT * FROM film WHERE rental_duration > 7;

25.Movies with rental rate 2.99 or 4.99, rating ‘R’, title contains “Love”

SELECT * FROM film WHERE rental_rate IN (2.99, 4.99) AND rating ='R' AND title LIKE '%Love%' LIMIT 10;

26.Titles containing % symbol

SELECT * FROM film WHERE title LIKE '%%%' ESCAPE '';

27.Titles containing underscore _

SELECT * FROM film WHERE title LIKE '%_%' ESCAPE '';

28.Titles containing digits

SELECT * FROM film WHERE title REGEXP '[0-9]';

29.Titles containing backslash ()

SELECT * FROM film WHERE title LIKE '%\\%';

30.10 customers after skipping 20 (sorted by last name)

SELECT * FROM customer ORDER BY last_name ASC LIMIT 10 OFFSET 20;

What I Learned

  • How to filter data using WHERE, AND, OR
  • Sorting with ORDER BY
  • Pagination(Page navigation) using LIMIT and OFFSET
  • Pattern matching with LIKE and REGEXP
  • Handling missing data using NULL