meier-gen-z-participation
Diagnose and improve recruitment, retention, products, brands, and intergenerational collaboration using Yaël Meier's public participation approach. Use when an organization needs to involve young people in decisions that affect them.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- meier-gen-z-participation
- description
- Diagnose and improve recruitment, retention, products, brands, and intergenerational collaboration using Yaël Meier's public participation approach. Use when an organization needs to involve young people in decisions that affect them.
02 资源文件 7
- 参考文档checklists/review-checklist.md6.2 KB
- 参考文档DERIVATION.json2.8 KB
- 参考文档examples/worked-examples.md9.1 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md17.5 KB
- 参考文档references/sources.md4.8 KB
- 参考文档templates/output-template.md6.9 KB
03 SKILL.md 正文
Meier Gen Z Participation
Based on Yaël Meier's public method. Not affiliated with or endorsed by Yaël Meier.
When to use
Use this skill to turn a youth-facing organizational problem into an evidence-led decision brief: improving applications or retention, changing a product or customer experience, reviewing employer branding, or building collaboration across generations. The deliverable connects what affected young people experience to a change the organization can make, an accountable owner, and a test.
Begin with the relevant segment and decision, rather than a universal Gen Z persona. Age alone does not establish needs, skills, purchasing power, or channel preference. This package applies public interviews, posts, and a reported talk; it does not reproduce the jointly edited book or claim access to ZEAM's proprietary instruments. See references/sources.md for the source boundary. [S1]
The participation principle is central: young people help interpret evidence and shape choices before the final recommendation. If participant access is missing, deliver a provisional brief with a recruitment plan and explicit uncertainties. Do not invent interviews or present illustrative findings as research. Source-backed advice, actual participant evidence, and the agent's operational recommendations must remain distinguishable. [S2] [S3]
Procedure
-
Define the decision. Read the scope rules in references/method.md. Write the outcome, affected group, observed friction, changeable lever, and decision owner in one sentence. Choose employer, customer, or intergenerational work; keep separate decisions separate even when one organization owns them. [S4]
-
Define the segment and evidence limits. Use the evidence rules in references/method.md. Describe life stage, context, relevant needs, and exclusions. Classify supplied claims as observations, participant accounts, hypotheses, or public-method guidance. Treat executive family anecdotes as hypotheses. [S2]
-
Bring affected people into discovery. Follow references/method.md. Include contrasting experiences such as declined candidates or abandoned purchases. Ask about recent decisions and obstacles. Specify how participants can influence the work and what the organization cannot change. [S3] [S6]
-
Interpret findings together. Use the evidence table in templates/output-template.md. Record context, a theme, a counterexample, uncertainty, and the decision implication. Give participants an opportunity to correct interpretations. If evidence is absent or conflicting, narrow the recommendation or plan further discovery.
-
Diagnose the underlying offer. Apply the relevant branch in references/method.md. For employers inspect money, internal appreciation, and external appreciation; for customers inspect benefit, experience, and reputation. Connect each gap to observed friction before proposing communications. [S4] [S7]
-
Make participation operational. Follow references/method.md. Define a real contribution, bounded responsibility, support, feedback, and decision rights. If mentoring fits the problem, make it voluntary, reciprocal, personally matched, structured, and visibly supported by senior leaders. [S5] [S8]
-
Develop and compare changes. Consult examples/worked-examples.md for the reasoning pattern. Invite young contributors to shape feasible options. Compare the current approach with changes to the offer, process, or participation. Explain tradeoffs and why the selected option addresses the evidence. Examples are illustrations, not benchmarks.
-
Choose channels and content when needed. Apply references/method.md. Use the segment's actual attention and decision journey. Let connected contributors shape content, show concrete benefits, and ensure every promise is deliverable. Specify ownership of a continuing presence rather than assuming one campaign establishes relevance. [S4] [S6]
-
Design a bounded test. Follow references/method.md. Define a comparison, outcome metric, baseline, review date, and scale, revise, or stop rule. Include behavioral evidence and participant feedback; revise the generation hypothesis when findings contradict it. [S6] [S9]
-
Deliver and review the brief. Fill templates/output-template.md, then apply checklists/review-checklist.md. Assign owners and dates, label unresolved evidence gaps, and cite Meier-specific assertions. Hand back a decision the organization can act on, with a clear next review and no invented certainty.
Files in this skill
- SKILL.md: Entry point, use cases, and the ten-step application loop.
- references/method.md: Principles, branches, decision rules, explicit warnings, and edge cases.
- references/sources.md: Nine fetched public sources, their contributions, and evidence limitations.
- examples/worked-examples.md: Two invented before-and-after illustrations with rule explanations.
- templates/output-template.md: Fill-in decision brief with guidance for every field.
- checklists/review-checklist.md: Pass/fail review, common failure modes, and practical fixes.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.