{ "schemaVersion": "1.0", "item": { "slug": "persona-docs", "name": "Persona Docs", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/wpank/persona-docs", "canonicalUrl": "https://clawhub.ai/wpank/persona-docs", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/persona-docs", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=persona-docs", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "references/template.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/persona-docs" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/persona-docs", "agentPageUrl": "https://openagent3.xyz/skills/persona-docs/agent", "manifestUrl": "https://openagent3.xyz/skills/persona-docs/agent.json", "briefUrl": "https://openagent3.xyz/skills/persona-docs/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Persona Docs", "body": "Create user-centered documentation that defines who a product is for and how they interact with it. Persona docs establish the foundation for product-driven development — every feature decision, design choice, and prioritization call flows from understanding your users." }, { "title": "OpenClaw / Moltbot / Clawbot", "body": "npx clawhub@latest install persona-docs" }, { "title": "When to Create", "body": "Persona docs should be the first thing fleshed out for any product. Even minimal documentation about who uses the product helps direct development and design decisions.\n\nProject inception — before writing code, define who you're building for\nPivoting to a new audience — document the shift so the team aligns\nTeam lacks clarity on target users — when people disagree on \"who is this for?\"\nBefore major feature planning — validate that planned features serve actual users\nNew team member onboarding — give them context on who they're building for" }, { "title": "Process", "body": "Analyze the codebase — look for existing documentation, README, landing pages, or marketing copy that hints at the target audience\nAsk clarifying questions if the target user isn't clear:\n\n\"Who is the primary user of this product?\"\n\"What problem does this solve for them?\"\n\"How would they discover this product?\"\n\"What's the first thing they'd do after finding it?\"\n\n\nStart minimal — a few sentences per section is better than nothing\nRead the template — see references/template.md for the full structure\nIterate — revisit and expand as you learn more about actual users" }, { "title": "1. Target User Profile", "body": "Who they are, their background, their context. Be specific enough to be useful.\n\nGood: \"Backend engineers at mid-size SaaS companies who debug production issues under time pressure, typically 3-8 years of experience, comfortable with command-line tools.\"\n\nToo vague: \"Developers.\"\n\nInclude:\n\nRole, job title, or archetype\nTechnical level and relevant skills\nIndustry or domain context\nWhen and where they'd use this product\nTeam size and organizational context" }, { "title": "2. User Needs and Pain Points", "body": "The problems this product solves. What frustrations or gaps exist in their current workflow?\n\nStructure as:\n\nPrimary pain point — the single biggest problem you solve\nSecondary pain points — additional problems you address\nCurrent workarounds — what they do today without your product\nWhy existing solutions fail — what alternatives exist and why they're insufficient" }, { "title": "3. Discovery Path", "body": "How they find the product. This informs marketing, positioning, and first-impression design.\n\nSearch — what queries lead them here?\nReferral — word of mouth, colleague recommendation?\nContent — blog posts, tutorials, conference talks?\nMarketplace — app store, plugin directory, package registry?\nThe hook — what makes them click \"sign up\" or \"download\"?" }, { "title": "4. Onboarding Flow", "body": "The simplest possible path from \"I found this\" to \"I'm getting value.\"\n\nDefine:\n\nFirst encounter — landing page, app store listing, GitHub README\nRegistration/Login — minimum viable auth (email-only? OAuth? no account?)\nTime to value — how quickly can they experience the core benefit?\nFirst success moment — the specific action that makes them think \"this is useful\"\nFriction points — where do users drop off, and how do you minimize that?\n\nExample flow:\n\nUser lands on homepage → clicks \"Try it\" → pastes their data → sees result in <30 seconds → decides to create account" }, { "title": "5. User Journey Map", "body": "Key touchpoints and interactions across the user lifecycle.\n\nNew User (Day 1):\n\nDiscovers product via [channel]\nTakes [first action]\nAchieves [first success]\n\nReturning User (Week 1):\n\nKey repeated action they perform\nFeatures they explore\nIntegrations or customizations they set up\n\nPower User (Month 1+):\n\nAdvanced features they rely on\nWorkflows they've established\nHow they'd describe the product to others" }, { "title": "6. Feature Touchpoints", "body": "Map where users encounter key features in their journey:\n\nFeatureWhen EncounteredUser Need at That Moment[Feature 1][Journey stage][What they're trying to do][Feature 2][Journey stage][What they're trying to do]" }, { "title": "Multi-Persona Products", "body": "If your product serves multiple distinct user types:\n\nIdentify the primary persona first — who must you serve to survive?\nDocument secondary personas separately — one file per persona\nNote conflicts — where persona needs clash, document the tradeoff\nPrioritize ruthlessly — you can't optimize for everyone simultaneously" }, { "title": "Output Location", "body": "Place persona docs at:\n\ndocs/PERSONA.md — single file for simple products\ndocs/personas/ — directory for multiple personas\n\nKeep it in the repo so it evolves with the product." }, { "title": "Quality Criteria", "body": "A good persona doc should:\n\nBe specific enough that two team members would build the same feature from it\nInclude evidence — data, quotes, or observations, not just assumptions\nBe actionable — reading it should change how you build\nBe maintained — outdated personas are worse than none\nBe honest — don't describe aspirational users; describe actual users" }, { "title": "NEVER Do", "body": "NEVER skip personas for a new product — building without knowing your user is guessing, and guessing is expensive\nNEVER describe users as demographics alone — \"25-34 male\" tells you nothing about what they need; describe behaviors and goals\nNEVER create personas in isolation — involve the team; one person's assumptions become the whole product's blind spots\nNEVER treat personas as permanent — users change, markets shift; review personas quarterly\nNEVER create more than 3 personas initially — if you try to serve everyone, you serve no one; start with your primary user\nNEVER write aspirational personas — document who actually uses your product, not who you wish did" } ], "body": "Persona Docs\n\nCreate user-centered documentation that defines who a product is for and how they interact with it. Persona docs establish the foundation for product-driven development — every feature decision, design choice, and prioritization call flows from understanding your users.\n\nInstallation\nOpenClaw / Moltbot / Clawbot\nnpx clawhub@latest install persona-docs\n\nWhen to Create\n\nPersona docs should be the first thing fleshed out for any product. Even minimal documentation about who uses the product helps direct development and design decisions.\n\nProject inception — before writing code, define who you're building for\nPivoting to a new audience — document the shift so the team aligns\nTeam lacks clarity on target users — when people disagree on \"who is this for?\"\nBefore major feature planning — validate that planned features serve actual users\nNew team member onboarding — give them context on who they're building for\nProcess\nAnalyze the codebase — look for existing documentation, README, landing pages, or marketing copy that hints at the target audience\nAsk clarifying questions if the target user isn't clear:\n\"Who is the primary user of this product?\"\n\"What problem does this solve for them?\"\n\"How would they discover this product?\"\n\"What's the first thing they'd do after finding it?\"\nStart minimal — a few sentences per section is better than nothing\nRead the template — see references/template.md for the full structure\nIterate — revisit and expand as you learn more about actual users\nCore Components\n1. Target User Profile\n\nWho they are, their background, their context. Be specific enough to be useful.\n\nGood: \"Backend engineers at mid-size SaaS companies who debug production issues under time pressure, typically 3-8 years of experience, comfortable with command-line tools.\"\n\nToo vague: \"Developers.\"\n\nInclude:\n\nRole, job title, or archetype\nTechnical level and relevant skills\nIndustry or domain context\nWhen and where they'd use this product\nTeam size and organizational context\n2. User Needs and Pain Points\n\nThe problems this product solves. What frustrations or gaps exist in their current workflow?\n\nStructure as:\n\nPrimary pain point — the single biggest problem you solve\nSecondary pain points — additional problems you address\nCurrent workarounds — what they do today without your product\nWhy existing solutions fail — what alternatives exist and why they're insufficient\n3. Discovery Path\n\nHow they find the product. This informs marketing, positioning, and first-impression design.\n\nSearch — what queries lead them here?\nReferral — word of mouth, colleague recommendation?\nContent — blog posts, tutorials, conference talks?\nMarketplace — app store, plugin directory, package registry?\nThe hook — what makes them click \"sign up\" or \"download\"?\n4. Onboarding Flow\n\nThe simplest possible path from \"I found this\" to \"I'm getting value.\"\n\nDefine:\n\nFirst encounter — landing page, app store listing, GitHub README\nRegistration/Login — minimum viable auth (email-only? OAuth? no account?)\nTime to value — how quickly can they experience the core benefit?\nFirst success moment — the specific action that makes them think \"this is useful\"\nFriction points — where do users drop off, and how do you minimize that?\n\nExample flow:\n\nUser lands on homepage → clicks \"Try it\" → pastes their data → sees result in <30 seconds → decides to create account\n\n5. User Journey Map\n\nKey touchpoints and interactions across the user lifecycle.\n\nNew User (Day 1):\n\nDiscovers product via [channel]\nTakes [first action]\nAchieves [first success]\n\nReturning User (Week 1):\n\nKey repeated action they perform\nFeatures they explore\nIntegrations or customizations they set up\n\nPower User (Month 1+):\n\nAdvanced features they rely on\nWorkflows they've established\nHow they'd describe the product to others\n6. Feature Touchpoints\n\nMap where users encounter key features in their journey:\n\nFeature\tWhen Encountered\tUser Need at That Moment\n[Feature 1]\t[Journey stage]\t[What they're trying to do]\n[Feature 2]\t[Journey stage]\t[What they're trying to do]\nMulti-Persona Products\n\nIf your product serves multiple distinct user types:\n\nIdentify the primary persona first — who must you serve to survive?\nDocument secondary personas separately — one file per persona\nNote conflicts — where persona needs clash, document the tradeoff\nPrioritize ruthlessly — you can't optimize for everyone simultaneously\nOutput Location\n\nPlace persona docs at:\n\ndocs/PERSONA.md — single file for simple products\ndocs/personas/ — directory for multiple personas\n\nKeep it in the repo so it evolves with the product.\n\nQuality Criteria\n\nA good persona doc should:\n\nBe specific enough that two team members would build the same feature from it\nInclude evidence — data, quotes, or observations, not just assumptions\nBe actionable — reading it should change how you build\nBe maintained — outdated personas are worse than none\nBe honest — don't describe aspirational users; describe actual users\nNEVER Do\nNEVER skip personas for a new product — building without knowing your user is guessing, and guessing is expensive\nNEVER describe users as demographics alone — \"25-34 male\" tells you nothing about what they need; describe behaviors and goals\nNEVER create personas in isolation — involve the team; one person's assumptions become the whole product's blind spots\nNEVER treat personas as permanent — users change, markets shift; review personas quarterly\nNEVER create more than 3 personas initially — if you try to serve everyone, you serve no one; start with your primary user\nNEVER write aspirational personas — document who actually uses your product, not who you wish did" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/wpank/persona-docs", "publisherUrl": "https://clawhub.ai/wpank/persona-docs", "owner": "wpank", "version": "0.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/persona-docs", "downloadUrl": "https://openagent3.xyz/downloads/persona-docs", "agentUrl": "https://openagent3.xyz/skills/persona-docs/agent", "manifestUrl": "https://openagent3.xyz/skills/persona-docs/agent.json", "briefUrl": "https://openagent3.xyz/skills/persona-docs/agent.md" } }