expert-persona-skills

Expert Persona Skills

Overview

A technique for writing short, focused skill files (often under 50 lines) that prime Claude to operate as a domain expert. The key insight: you are not teaching the LLM new knowledge. You are activating latent knowledge it already has. A small bag of context — the right terminology, constraints, mental models, and reference points — is enough to shift Claude from generic assistant into a credible domain practitioner.

Core principle: Short, focused priming beats long instruction sets. Even 40 lines can unlock deep expertise if those lines contain the right activation signals.

Dependency: None. These are plain Markdown skill files. Optionally pair with MCP servers for tool access in the target domain.

When to Use

• You need Claude to work in a non-coding domain (legal, marketing, finance, security, PM)
• You want consistent expert-level output across multiple conversations
• You are building a skill for a domain you are not personally expert in
• You want to package domain knowledge for a team so everyone gets the same quality
• You are creating a library of reusable personas for different project phases

When NOT to Use

• The task is a one-off question with no need for consistency across sessions
• You need legally binding advice (skills improve quality but do not replace licensed professionals)
• The domain requires access to proprietary data that cannot be described in a skill file

Common Mistakes

Mistake	Why it's wrong
Writing a 500-line skill that tries to teach the LLM everything	You are activating, not teaching. Claude already knows trademark law — it just needs the right framing to apply it. Long files dilute the signal.
Omitting concrete constraints and defaults	"Be a good PM" activates nothing. "Default to RICE scoring, timebox discovery to 1 week, require a one-pager before any spec" activates a specific PM style.
Copying a textbook instead of curating activation signals	A paragraph of terminology, a list of common pitfalls, and a decision framework will outperform ten pages of reference material.
Skipping reference examples from real projects	Well-executed open source projects are the best design references for unfamiliar domains. Point Claude at one instead of writing your own spec from scratch.
Making the skill only about instructions, ignoring tools	Skills are bags of context plus MCP servers. A trademark skill paired with a USPTO search tool is dramatically more useful than either alone.