Post-Labor Economics

v1.0.0

Model post-labor economies with automation shocks, distribution redesign, and policy portfolios across income, ownership, time, and services.

0· 273·0 current·0 all-time
byIván@ivangdavila

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for ivangdavila/post-labor-economics.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Post-Labor Economics" (ivangdavila/post-labor-economics) from ClawHub.
Skill page: https://clawhub.ai/ivangdavila/post-labor-economics
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install ivangdavila/post-labor-economics

ClawHub CLI

Package manager switcher

npx clawhub@latest install post-labor-economics
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (post-labor economic modeling, policy portfolios, scenarios) align with the provided files and declared behavior. There are no unexpected env vars, binaries, or external services required.
Instruction Scope
Runtime instructions are limited to structuring analysis, asking the user for context, and optionally persisting memory in ~/post-labor-economics/. The skill explicitly asks for user confirmation before writing files and states it makes no undeclared network calls or reads outside its declared path.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is downloaded or written by an installer. This is low-risk and proportionate for a documentation/assistant skill.
Credentials
Requires no environment variables, credentials, or config paths beyond the declared local memory directory. The skill's requested persistence (local memory) is proportional to its stated purpose.
Persistence & Privilege
always:false and no special privileges requested. The skill may persist local preference/memory under the user path only after explicit confirmation, which matches its functionality. Note: agent autonomous invocation is allowed by platform default but is not a specific concern here given the skill's limited scope.
Assessment
This skill appears coherent and instruction-only. Before installing: (1) Confirm you are comfortable with files being created under ~/post-labor-economics/ and only grant permission when prompted; (2) Do not paste sensitive personal credentials or private data into prompts or saved memory; (3) If the skill recommends installing related skills (e.g., 'economics', 'strategy'), review those skills' requirements separately — they may request additional access or tooling; (4) If you need strict non-persistence, decline the setup persistence option so the skill runs session-only. Overall, the skill does what it says and requests no disproportionate system access.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📉 Clawdis
OSLinux · macOS · Windows
latestvk971pc1mr36xh4gdbw1fvevdp98285tg
273downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0
Linux, macOS, Windows

Setup

If ~/post-labor-economics/ does not exist or is empty, read setup.md, explain that you can save local preferences for continuity, and ask for explicit confirmation before writing memory files.

When to Use

User wants to analyze a world where paid employment is no longer the main channel for income, status, or social coordination. Use for automation transition strategy, post-work policy design, distribution modeling, and labor market scenario planning.

Architecture

Memory lives in ~/post-labor-economics/. See memory-template.md for setup.

~/post-labor-economics/
|- memory.md            # Core context and integration preferences
|- portfolios.md        # Policy portfolio drafts and decision logs
|- indicators.md        # Chosen metrics, targets, and thresholds
`- scenarios.md         # Transition scenarios and stress tests

Data Storage

Local working memory and transition artifacts are stored in ~/post-labor-economics/ only.

Quick Reference

TopicFile
Setup processsetup.md
Memory templatememory-template.md
Core frameworksframeworks.md
Policy portfolio designpolicy-portfolio.md
Indicators and dashboardsindicators.md
Scenario stress testsscenarios.md
Evidence mapresearch-notes.md

Core Rules

1. Define the Transition Mechanism Before Debating Policy

Start by naming what changed in production:

  • task automation,
  • capital concentration,
  • platform coordination,
  • energy and ecological limits,
  • demographic pressure.

No mechanism means no credible post-labor recommendation.

2. Separate Production Logic from Distribution Logic

Model these as two distinct layers:

  • how goods and services are produced,
  • how purchasing power, rights, and access are distributed.

Do not assume that efficient production automatically produces fair distribution.

3. Design Bundles, Not Single-Idea Policies

Always propose a portfolio with at least three categories:

  • baseline security (income or services),
  • coordination of socially necessary work,
  • ownership and bargaining architecture.

Single-policy answers are fragile and usually fail under political stress.

4. Make Power and Ownership Explicit

For each design, state:

  • who owns productive assets,
  • who controls allocation decisions,
  • who captures automation gains,
  • who absorbs transition risk.

If power is hidden, the model is incomplete.

5. Quantify the Path, Not Just the End-State

Require phased planning:

  • near term (0-3 years),
  • transition (3-10 years),
  • structural horizon (10+ years).

For each phase, define financing, institutions, and measurable checkpoints.

6. Evaluate Multiple Human Profiles

Every recommendation must score effects on:

  • displaced workers,
  • care workers,
  • young entrants,
  • older workers,
  • disabled people,
  • small producers and local communities.

A policy that works only for one profile is not a post-labor solution.

7. Maintain an Evidence Ledger

Tag every claim as one of:

  • empirical finding,
  • modeling assumption,
  • normative preference,
  • political constraint.

Never present assumptions or values as settled facts.

Common Traps

  • Treating post-labor economics as "no one works" -> ignores care, coordination, and public goods labor.
  • Debating UBI as the whole system -> misses services, institutions, and ownership design.
  • Assuming automation gains distribute automatically -> reproduces inequality under new technology.
  • Mixing descriptive and moral claims -> analysis becomes rhetorical instead of decision-grade.
  • Skipping implementation sequencing -> creates elegant theory with no transition path.
  • Ignoring political feasibility entirely -> proposal cannot survive first contact with institutions.

Security & Privacy

Data that leaves your machine:

  • None from this skill itself.

Data that stays local:

  • Policy drafts, indicators, and scenarios in ~/post-labor-economics/.

This skill does NOT:

  • Make undeclared network calls.
  • Collect or infer sensitive personal data beyond what user provides for analysis.
  • Write outside its declared local path.

Scope

This skill ONLY:

  • Structures post-labor economic analysis.
  • Builds policy portfolios and transition scenarios.
  • Separates empirical evidence from assumptions and values.

This skill NEVER:

  • Claims deterministic macro forecasts.
  • Replaces legal or fiscal sign-off by institutions.
  • Treats one country template as universally transferable.

Related Skills

Install with clawhub install <slug> if user confirms:

  • economics - Economic reasoning and policy tradeoff analysis.
  • strategy - Structured decision design under constraints.
  • work - Practical work design and role-level execution planning.
  • productivity - Throughput and workflow optimization at task level.
  • collaborate - Multi-stakeholder communication and coordination patterns.

Feedback

  • If useful: clawhub star post-labor-economics
  • Stay updated: clawhub sync

Comments

Loading comments...