Show Your Work Kleon Agent Skill

Core Philosophy

Austin Kleon's *Show Your Work!* makes a single counterintuitive argument: you don't need talent, credentials, or a finished body of work before you start sharing. You need to share the process of becoming. The audience finds you not because of what you've produced, but because they recognize themselves in how you work.

The fundamental reframe: stop thinking "I need to finish this before I can share it." Start thinking "sharing IS the work."

When to Use This Skill

Use this skill for queries that match the trigger phrases in the description and require applying the decision framework from *Show Your Work!* rather than summarizing the book.

The Framework

Principle 1: Scenius Over Genius

Kleon borrows the term "scenius" from Brian Eno — the idea that creativity is not the product of lone geniuses but of collaborative ecology: a group of people in the same scene who share ideas, steal from each other generously, build on each other's work.

Why this matters for sharing: You are not a solo creator broadcasting to an audience. You are a node in a scenius. When you share your process, your influences, your failures, and your questions, you contribute to a creative ecosystem that is larger than any individual. The scenius rewards contributors.

Practical implication: Credit your influences publicly. Show what you're learning from. Make your "scenius" visible — the books you're reading, the artists inspiring you, the problems you're wrestling with.

Principle 2: The Amateur Advantage

"Amateur" comes from the Latin for "lover." An amateur does work for the love of it, not for money or credentials. Kleon argues the amateur has a structural advantage over the professional:

• Less to lose by experimenting publicly
• Willing to ask "dumb" questions that experts have forgotten to ask
• Enthusiasm that is contagious (professionals often hide theirs)
• Learning in public at full speed, which is itself compelling to watch

The amateur's assignment: Share what you're learning as you learn it. The tutorial you write the week after learning something is better than the tutorial an expert writes years later — because you remember what it was like not to know.

Principle 3: You Are What You Share

"In the beginner's mind there are many possibilities, but in the expert's mind there are few." — Shunryu Suzuki

Your online presence is not a resume — it's a cabinet of curiosities. What you share signals who you are, what you care about, and who you want to attract. You don't need to brand yourself explicitly; you reveal yourself through what you find worth sharing.

The curation question: "Does this add value to the audience's day, or is it just noise?"

Kleon's "So What?" test: Before posting anything, ask: "So what? Who cares? What's interesting about this?" If you can't answer it, don't post it. If you can answer it clearly in one sentence, post it.

Principle 4: Open Up Your Process

Most creators show the finished product. Kleon argues you should show the work behind the work — the messy middle, the false starts, the revision history, the tools you use, the questions you're asking.

"Become a documentarian of what you do." Think of yourself as a filmmaker doing a behind-the-scenes documentary, not a marketing department. The behind-the-scenes footage is often more compelling than the film itself.

What to share from your process:

• Your current influences (what you're reading, watching, listening to)
• Problems you're trying to solve and how you're approaching them
• Work-in-progress — sketches, drafts, prototypes
• Your method: tools, routines, systems
• Failures and what you learned from them
• Questions you're genuinely wrestling with

The Chris Hadfield example: When Canadian astronaut Chris Hadfield went to the International Space Station, he began sharing daily glimpses of life in space — videos of how astronauts cry in zero gravity, how they brush their teeth, how Earth looks at sunset from orbit. By the time he recorded his cover of David Bowie's "Space Oddity" in space, he had 1 million followers who had been with him daily for months. The song video got 22 million views in the first month. He didn't wait until he had a finished product to share.

Principle 5: Share Something Small Every Day

Kleon's "daily dispatch" practice: Share one small thing every day. Not a finished piece — a scrap, an observation, a question, a photo of what's on your desk, a sentence that struck you while reading.

The consistency principle: Daily sharing over years creates something no single post can — familiarity and trust. An audience built through daily small shares is more resilient than one built by viral moments.

"One sentence a day is enough." The discipline is in showing up, not in producing great content every day.

Principle 6: The "So What?" Test

Before sharing anything, apply the "So What?" test:

• What is genuinely interesting about this?
• Who specifically would care about this?
• What does it add to them?

If the answer to question 1 is "nothing" or you can't articulate it, don't post it. If you can answer all three questions, you have something worth sharing — even if it feels small or unfinished.

The "stock and flow" model (from writer Robin Sloan):

• Flow = the daily stream: tweets, short posts, daily updates. These are ephemeral — they catch people in the moment.
• Stock = the durable work: essays, tutorials, portfolio pieces, long-form writing. These compound over time and remain findable years later.

Most creators default entirely to flow (social media posts) or entirely to stock (infrequent long-form work). The most powerful strategy is both: daily flow that builds a habit of sharing and relationships, plus regular investment in stock that gives those relationships something permanent to anchor to.

Principle 7: Turn Your Flow Into Stock

The flow/stock integration strategy:

• Share daily small observations (flow)
• When a theme emerges across multiple flow pieces, combine them into a more substantial stock piece
• The stock piece feeds back into flow (people share excerpts, respond, ask questions)

This is how newsletters work at their best. This is how blogs built readerships before social media. The pattern still works — the platforms change.

Principle 8: Build a "Human Spam" Filter

Kleon distinguishes between sharing and human spam — broadcasting without listening, promoting without contributing, taking without giving back.

The reciprocity test:

• Do you read other people's work in your space, or only share your own?
• Do you credit and amplify others' work genuinely, or only when it makes you look good?
• Are you interested in the conversation, or just in being heard?

Human spam behavior: posting constantly, never engaging with replies, promoting yourself in other people's comment sections, treating your audience as a distribution channel rather than people.

The fix: "When you find things you genuinely enjoy, share them." The audience can tell the difference between genuine enthusiasm and marketing.

Principle 9: Learn to Take a Punch

Sharing publicly means criticism. Kleon's framework for handling negative response:

• Strengthen your work so that you believe in it before it goes public
• Keep a "praise file" — genuine positive responses that ground you when criticism hits
• Separate useful signal from noise — criticism of the work is worth engaging; personal attacks are not
• Remember the click-away option: The internet audience is not a captive audience. If someone doesn't like what you share, they leave. This is a feature, not a bug — it means those who stay actually want to be there.

"Compulsive avoidance of embarrassment is a form of suicide." Share imperfect work. It's better than perfect silence.

Principle 10: Sell Out the Right Way

When your work finds an audience, you can monetize it without betraying it — but only if you do it in ways consistent with what people showed up for.

The sustainability test: Does this monetization serve the audience or exploit them?

• Good: selling access to deeper engagement (books, workshops, courses) that gives more of what they came for
• Good: offering paid work to a select few (freelance commissions, consulting)
• Bad: selling audience data or attention to advertisers whose values conflict with your work
• Bad: turning your sharing into a promotional channel once you've built trust

"If you want a patron, you don't need to find one patron to fund you for life — you need to find 1,000 true fans."

Supported Query Types

• What to share: What kinds of process documentation, work-in-progress, and behind-the-scenes content will resonate with your specific audience
• Daily dispatch design: What your daily sharing practice should look like — format, frequency, content type
• Stock and flow audit: How to balance ephemeral daily updates with durable long-form content
• "So What?" evaluation: Whether specific content ideas pass the test for genuine value
• Scenius participation: How to engage with your creative community rather than broadcasting at them
• Platform selection: Which platforms fit your sharing practice vs. which create obligation without payoff
• Audience building without self-promotion: How to become findable through sharing rather than marketing

Output Format

When evaluating content to share:

• Apply the "So What?" test
• Identify whether it's flow (ephemeral) or stock (durable)
• Recommend format and platform that fits its nature
• Identify who specifically would care about it
• Suggest how to frame it as "behind the scenes" rather than promotion

When designing a sharing practice:

• Define the daily dispatch (what to share each day, in what form)
• Define the stock creation rhythm (frequency, format)
• Identify the scenius to participate in (specific communities, publications, creators to engage with)
• Name the one specific person the creator is sharing for

Limitations

Kleon's framework is optimized for creators whose work has a visible process — artists, writers, makers, builders, designers. It applies with some translation to knowledge workers (consultants, researchers, analysts) but requires reinterpretation: "showing your work" when your work is confidential client deliverables means sharing the methodology, not the outputs.

The framework also assumes genuine enthusiasm for the work being shared. It does not work as a marketing strategy applied cold to content you don't actually care about. Audiences can detect performed enthusiasm. The prerequisite for showing your work is actually doing work you find interesting.

Architecture Justification

This is a single-file skill because the book supports one primary workflow: apply Austin Kleon's framework to diagnose a user-supplied situation and produce a practical recommendation. The dimensions are tightly coupled lenses inside that workflow rather than independent tools with different inputs or output formats.

Workflow Inventory

| Workflow | User question pattern | Inputs | Steps | Output | Independent trigger? | Distinct references? | Triage score | Should be subskill? | Reason |

|---|---|---|---|---|---|---|---:|---|---|

| Framework diagnosis | User asks for analysis using the book's method | Situation, goal, constraints | Route to relevant dimensions; apply checks; identify warnings | Diagnosis and recommendation | Yes | Uses shared quote files | 2 | No | Primary workflow; all dimensions share one output |

| Improvement plan | User asks how to improve a campaign, product, policy, or decision | Current state and desired outcome | Identify gaps; rank fixes; propose next actions | Prioritized action plan | Yes | Uses shared quote files | 2 | No | Same diagnostic workflow with prescriptive output |

| Critique or second opinion | User asks whether advice, strategy, or reasoning is sound | Claim/recommendation and context | Test assumptions; flag incentives or missing criteria | Verdict with caveats | Yes | Uses shared quote files | 2 | No | Same dimensions, different framing |

Query Response Framework

• Identify the user's decision or artifact.
• Route the query to the relevant dimensions.
• Apply the checklist questions explicitly.
• Flag missing inputs, incentive conflicts, or anti-patterns.
• Produce a concise verdict and next actions.

Critical Reminders

• Use the book-derived framework as a decision tool, not as a book summary.
• Do not reproduce long source passages in responses.
• Ask for missing context when the user's input is too thin to support a verdict.

CITATION RULES

Use quotes only when the user asks for source grounding or when a claim needs attribution. Reference quote anchors by topic file and anchor. Keep quoted excerpts short.

• sharing-process-quotes.md: #today-taking-advantage-internet-social, #kinds-distinction-between-painter-process, #used-just-seeing-outcome, #daily-dispatch-even-better-portfolio, #once-anything-copied-brought-contact, #going-give-damn-want-made, #over-starving-artist-romanticism-idea, #traditionally-artist-been-trained-regard
• audience-community-quotes.md: #alone-matters-process-experience-shaping, #standing-party-enjoying-drink-stranger, #almost-every-overnight-success-story, #fell-place-sons-explained-social, #these-deserve-rejections-undoubtedly-receive, #were-basically-trying-could-each, #actually-simple-easy-requires-incredible, #notice-pattern-technology-often-most