persona-scribe

Generates technical documentation, changelogs, and localized content using structured writing archetypes.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill persona-scribe-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persona-scribe
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/persona-scribe
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill persona-scribe-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical documentation is often inconsistent, outdated, or written without considering the audience and cultural context. This Skill provides a decision framework for producing clear, audience-appropriate documentation across English, Korean, and Japanese. ## Core Features & Use Cases - Audience-Adaptive Writing: Adjusts tone and detail level for developers, end users, and stakeholders, covering API docs, user guides, READMEs, changelogs, and PR descriptions. - Six Documentation Archetypes: Provides default structures for technical references, tutorials, decision records, changelogs, runbooks, and user guides when no existing style references exist. - Multilingual Localization: Applies language-specific conventions for English, Korean, and Japanese, including formality levels, date formats, and technical term handling. - Use Case: When drafting a README for a new API library, the Skill structures the document with prerequisites, usage examples, and troubleshooting sections, then adapts it into Korean with proper -습니다체 formality. ## Quick Start Write a user guide for the authentication feature of my project, including a Korean localized version.

Frequently Asked Questions about persona-scribe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write technical documentation for multiple audiences?▼

Identify the audience first, then adjust tone and detail: developers get technical, concise content with code examples; users get friendly step-by-step instructions; stakeholders get business-focused outcomes and metrics. Structure with headings, bullets, and tables for scannability.

How to localize technical docs into Korean or Japanese?▼

Use formal polite register (-습니다체) for Korean and desu/masu form for Japanese. Keep technical terms in original English with parentheses on first use in Korean, and use katakana for foreign terms in Japanese. Localize date formats, numbers, and cultural references, not just the words.

What documentation structure should I use without existing style guides?▼

Choose from six archetypes: technical reference, tutorial walkthrough, decision record, changelog narrator, internal runbook, or user guide. Each provides default section flow, tone, and length targets that you tune to project context.

When should I not use this documentation framework?▼

Avoid it for marketing copy, persuasive content, or non-technical prose where conversion and engagement matter more than clarity and technical accuracy. It is designed for documentation, not promotional writing.

Does this skill support languages beyond English, Korean, and Japanese?▼

The language support reference covers English, Korean, and Japanese with specific conventions for each. Other languages are not covered by the built-in localization checklist and formality rules.