跳到正文
cccskills
免费在 GitHub 公开

persona-updater

Update user personas from new feedback, pilot data, or research. Use this skill when: - New pilot data or feedback reveals changed user behaviors or pain points - Annual persona review is due (1-2x per year) - New user segments are discovered that need persona documentation - Existing personas need validation against recent data

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md4.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Persona Updater

Systematically update user persona files when new data (pilot observations, feedback, research) reveals changes in user behaviors, pain points, goals, or context. Generates diffs and preserves existing persona structure.

When to Use

  • After pilot rounds with new user observations (1-2x per year)
  • After significant feedback collection rounds
  • When expanding to new user segments or geographies
  • During annual persona review cycles

Workflow

  1. Read existing personas — Load all persona files from your persona directory
  2. Read new data sources — Pilot debrief reports, feedback, research
  3. Compare — Identify what's new, changed, or no longer relevant
  4. Generate diff — Structured change list per persona
  5. Propose updates — Show the diff to the user for approval
  6. Apply updates — Edit persona files preserving existing structure

Persona Dimensions to Track

DimensionWhat to Look For
DemographicsAge range, role, geography, segment
GoalsWhat they're trying to achieve
Pain PointsCurrent frustrations and blockers
BehaviorsHow they use the product, daily routines, device usage
ContextEnvironment, connectivity, device type
MotivationsWhat drives engagement
BarriersWhat prevents usage
Mental ModelsHow they think about the domain

Output Format

# Persona Update Report

**Date:** {DD-MM-YYYY}
**Data Sources:** {list sources reviewed}
**Personas Reviewed:** {count}
**Changes Found:** {count}

---

## Persona: {Persona Name} ({file path})

### New Findings

| # | Dimension | Finding | Source | Confidence |
|---|-----------|---------|--------|-----------|
| 1 | Pain Points | {new pain point discovered} | {source} | High/Med/Low |

### Changed Findings

| # | Dimension | Current Text | Proposed Update | Source | Rationale |
|---|-----------|-------------|-----------------|--------|-----------|
| 1 | Goals | "{current}" | "{updated}" | {source} | {why} |

### Removed / No Longer Relevant

| # | Dimension | Current Text | Reason for Removal | Source |
|---|-----------|-------------|-------------------|--------|
| 1 | Pain Points | "{old}" | Resolved by {feature} | {evidence} |

### No Change (Validated)

| # | Dimension | Current Text | Validation Source |
|---|-----------|-------------|------------------|
| 1 | Goals | "{goal}" | Confirmed in pilot |

---

## Summary

| Persona | New | Changed | Removed | Validated | Action |
|---------|-----|---------|---------|-----------|--------|
| {name} | 2 | 1 | 0 | 5 | Update |

Update Rules

  1. Always generate the diff first — Never edit persona files without showing proposed changes
  2. Preserve existing structure — Match the heading hierarchy and writing style
  3. Mark confidence levels — Single observation is "Low"; data from 50 users is "High"
  4. Don't remove without evidence — Only mark as "no longer relevant" with explicit evidence
  5. Add source citations — Every change must cite where the new data came from
  6. Version the update — Add a note: Last updated: {date} — Source: {data source}
  7. Flag new segments — If data reveals uncovered user segments, flag as new persona candidates

Anti-Patterns

  • Don't update personas without new data — that's just editing, not updating
  • Don't merge multiple personas without evidence they overlap
  • Don't remove pain points just because a fix was shipped — verify the fix worked

Quality Checklist

  • Every change has a data source citation
  • Confidence levels marked on all findings
  • Diff shown to user before applying changes
  • Existing persona structure preserved
  • New segments flagged if discovered

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

查看 qa-aman 的全部技能

报告此技能的问题