Contributor Economy Designer

An agent skill for Claude and other AI agents that helps community builders design contribution systems that make invisible labor visible, reward people fairly, and align community work to business outcomes.

Core belief: The hardest problems in community building are not technical. They are human. Most contribution systems fail not because of bad tooling but because they were designed without understanding what people actually need to feel seen, valued, and motivated to keep showing up.

Install

Claude Code

npx skills add cassandraoid/contributor-economy-designer -a claude-code

Codex CLI

npx skills add cassandraoid/contributor-economy-designer -a codex

Cursor

npx skills add cassandraoid/contributor-economy-designer -a cursor

GitHub Copilot

npx skills add cassandraoid/contributor-economy-designer -a copilot

All agents (auto-detect)

npx skills add cassandraoid/contributor-economy-designer

Prerequisites: Node.js required. Install via brew install node (Mac) or nodejs.org.

What this skill does

When installed, this skill gives Claude deep expertise in designing, auditing, and improving contribution economies for developer communities, open source projects, and DevRel programs.

It treats three things — that most frameworks handle separately — as inseparable:

Making invisible labor visible and valued
Designing contribution systems organizations can actually implement
Aligning community work to outcomes the business cares about

The five questions it helps answer:

What are we actually recognizing — and what are we missing?
Does recognition feel proportional to the people receiving it?
How is contribution load distributed — and who is carrying too much?
Can contributors see their own impact?
Are community incentives aligned with business outcomes?

Usage examples

"I run a DevRel program and leadership keeps questioning the ROI. How do I design the program so I can actually show business impact?"

"We have a contributor program but it's always the same 10 people getting recognized. What's wrong with the system?"

"I think some of my most valuable community members are doing work nobody is tracking. How do I make that visible?"

"Our top contributor just left and I didn't see it coming. What signals should I have been watching?"

"I want to design a contribution system for our open source project that doesn't burn people out. Where do I start?"

"We're launching a community program and leadership wants metrics. What should I be measuring?"

"How do I design recognition that actually means something — not just badges and swag?"

Reference framework

File	Contents
`references/contribution-audit.md`	Full contribution surface mapping, audit questions, gap identification
`references/invisible-labor.md`	What invisible labor looks like, why it stays invisible, design interventions
`references/recognition-design.md`	Recognition hierarchy, design principles, common failure modes
`references/business-alignment.md`	Four alignment pathways, making the case to leadership, alignment audit
`references/sustainability.md`	Burnout pattern recognition, structural causes, sustainability interventions

Design philosophy

Contribution economies fail in predictable ways: they measure what's visible instead of what's valuable, they reward the loudest instead of the most consistent, they burn out their best people and don't understand why, and they can't explain their value to leadership when budgets tighten.

This skill is designed to fix all four — not as separate problems but as the single interconnected system they actually are.

About

Designed by Cassandra Ferrara — human systems designer, DevRel strategist, and community builder with experience across startups, enterprise organizations, and developer ecosystems.

License

MIT