Agent skill
user-content-skill
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/user-content-skill
SKILL.md
User Content Skill
=== PURPOSE ===
Procedures for creating user-facing content beyond microcopy.
=== USED BY ===
| Agent | Purpose |
|---|---|
| @agent(copywriter) @ref(CB-AGENT-COPY-001) | Primary skill for user content |
=== PROCEDURE: Onboarding Copy ===
Welcome Screen:
## Template
### Headline
Welcome to [Product]! (or persona-specific greeting)
### Subheadline
[One sentence about what they can do]
### CTA
Get started / Take a quick tour / Skip for now
Step-by-Step Onboarding:
## Step 1 of 3: [Action]
### Headline
[What to do]
### Body
[Why this matters - 1-2 sentences]
### CTA
[Action verb] / Skip
### Progress
Step 1 of 3
Checklist Onboarding:
## Get started with [Product]
Complete these steps to get the most out of [Product]:
- [ ] Connect your account
- [ ] Invite team members
- [ ] Create your first project
- [x] Completed step
=== PROCEDURE: Email Templates ===
Transactional Email Template:
## Subject Line
[Action-oriented, specific]
## Preview Text
[First 50 characters shown in inbox]
## Body
Hi [Name],
[One sentence about what happened/why we're emailing]
[Details if needed - keep brief]
[Clear CTA button]
[Closing]
[Team/Company name]
## Footer
[Unsubscribe link, address, etc.]
Email Types:
| Type | Subject Pattern | Tone |
|---|---|---|
| Welcome | "Welcome to [Product]!" | Warm, helpful |
| Confirmation | "Your [action] is confirmed" | Clear, factual |
| Password reset | "Reset your password" | Direct, urgent |
| Notification | "[Action]: [Details]" | Informative |
| Marketing | "[Benefit/News]" | Engaging |
=== PROCEDURE: Help Content ===
FAQ Format:
## Frequently Asked Questions
### How do I [common task]?
[Direct answer in 1-2 sentences]
[Steps if needed:]
1. First step
2. Second step
3. Third step
### Why can't I [problem]?
This usually happens because [reason].
To fix it:
1. Try [solution 1]
2. If that doesn't work, [solution 2]
3. Still stuck? [Contact support]
Troubleshooting Format:
## Troubleshooting: [Problem]
### Symptoms
- [What the user sees/experiences]
- [Another symptom]
### Cause
[Brief explanation]
### Solution
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Still having issues?
[Contact link or next steps]
=== PROCEDURE: Release Notes ===
User-Facing Format:
## What's New (Month YYYY)
### New Features
#### [Feature Name]
[One sentence benefit-focused description]
[Screenshot or GIF if helpful]
### Improvements
- **[Area]:** [What improved and why it matters]
- **[Area]:** [What improved and why it matters]
### Bug Fixes
- Fixed issue where [problem description]
- Resolved [problem] that caused [symptom]
Writing Guidelines:
- Lead with benefits, not features
- Use plain language (no tech jargon)
- Focus on what users can do now
- Keep it scannable
=== PROCEDURE: In-App Announcements ===
Banner:
[Icon] [Short message - max 100 chars] [CTA or Dismiss]
Modal:
## [Headline - what's new/important]
[1-3 sentences explaining the change/feature]
[Image/illustration if helpful]
[Primary CTA] [Secondary action or dismiss]
Tooltip/Coach Mark:
[Arrow pointing to element]
[What this is/does - max 100 chars]
[Got it / Next]
=== PROCEDURE: Content Audit ===
Review Checklist:
- Accurate and current
- Clear and concise
- Consistent with voice/tone
- Accessible language
- Action-oriented
- No jargon
- Proofread for errors
Questions to Ask:
- Who is reading this?
- What do they need to know?
- What should they do next?
- Is anything confusing or unclear?
- Can this be shorter?
=== RELATED SKILLS ===
| Skill | Relationship |
|---|---|
| @skill(microcopy) | Short-form UI text |
| @skill(voice-tone) | Consistency |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?