persona-usage

persona-usage is a skill for Claude Code from studiomeyer-io/studiomeyer-marketplace. It costs 48 tokens per session (1,175 once invoked), scanned A, original, MIT.

A guide for choosing and combining Crew personas, where each persona gives Claude a specific role, decision method, and answer format.

In plain words
What is it for?
Use it to select a persona for tasks such as strategy, finance, marketing, or product work, and to plan workflows that use several personas together.
Why use it?
It helps you decide when a specialist role will improve the work and prevents choosing the wrong role or switching roles unnecessarily.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the studiomeyer-crew plugin — 1 skill, 5 commands shipped together

Good fit Use it to select a persona for tasks such as strategy, finance, marketing, or product work, and to plan workflows that use several personas together.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/studiomeyer-io/studiomeyer-marketplace/persona-usage
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add studiomeyer-io/studiomeyer-marketplace --skill persona-usage
Clone the repo
git clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplace

Made for: Claude Code.

Or install studiomeyer-crew, the plugin that ships this one along with the rest of its 1 skill, 5 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for persona-usage

README.md
[![agentmods](https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage/github.svg)](https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage)
Your own site
<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for persona-usage

Your own site · 80×15
<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,175 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01175
Opus 5 $0.00024 $0.00588
Sonnet 5 $0.00010 $0.00235
Haiku 4.5 $0.00005 $0.00118

Measured 6d ago against content hash a899b65780d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

persona-usage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/studiomeyer-crew/skills/persona-usage/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Persona Usage Guide

Crew turns Claude into a specialist with a focused prompt, decision framework, and output format. This skill is the decision tree for picking the right one.

When to use a persona at all

A persona is worth activating when one specialist perspective will produce a better answer than general Claude. Good signals:

  • The user asks a question framed from a specific role's viewpoint ("how would a CFO evaluate this?")
  • The task has a canonical framework in that domain (RICE/ICE for PM, DORA for CTO, AARRR for CMO)
  • The output format matters (financial tables for CFO, user stories for PM, creative briefs for Creative Director)
  • The conversation will span multiple messages in that role, 5+ minutes of specialist work

Bad signals for activation:

  • Simple factual question: stay in default Claude
  • Mixed-domain question: do not switch mid-answer, stay general
  • User just wants information, not a decision: default works

When to pick which persona

User asks about... Activate
Strategy, vision, delegation, board-level priorities CEO
Pricing, ROI, budgets, financial modeling, revenue decisions CFO
Marketing, growth, SEO, content strategy, positioning CMO
Architecture, code review, tech debt, system design CTO
Feature prioritization, PRDs, user stories, JTBD, roadmaps PM
Market research, competitive analysis, data interpretation Research Analyst
Brand voice, visual direction, copy, storytelling Creative Director
Customer communication, docs, FAQ, onboarding flow Support Lead

Workflows: when one persona is not enough

Three built-in workflows chain personas for complex tasks:

strategy-review (CEO → CFO → CTO)

Use when the user has a strategic option and needs a go/no-go. CEO articulates the strategic case, CFO evaluates financial viability, CTO checks technical feasibility. Output is a unified verdict.

content-pipeline (CMO → Analyst → Creative)

Use when the user wants to produce content but has only a topic. CMO sets the strategic angle, Analyst fact-checks, Creative polishes for voice and hook. Output is a ready-to-publish piece.

Read the full file on GitHub · 91 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago Changed a899b65780d7
  2. 11d ago First seen · 91 lines · 48 tokens per session scan A 120ea95ac1fc

Subscribe to this mod's changes

persona-usage is a skill published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 1,175 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

geo-prospect

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi…

zubair-trabzada/geo-seo-claude · 87 tokens

gemini

Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…

nowork-studio/notfair-plugin · 184 tokens

google-ads-landing

Score and diagnose Google Ads landing pages. Use when asked to audit a landing page, check landing page quality, diagnose high-CTR but low-conversion-rate ad groups, improve Quality Score's Landing Page Experience component, or compare an ad group's messaging against its landing page. Trigger on "landing page audit"…

nowork-studio/notfair-plugin · 121 tokens

content-planner

GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…

nowork-studio/notfair-plugin · 123 tokens

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

schema-markup-generator

Generate JSON-LD structured data markup for rich results in Google Search. Supports FAQ, HowTo, Article, Product, LocalBusiness, and multi-type schemas. Validates against Google requirements and provides implementation guidance. Use when asked to "add schema markup", "generate structured data", "JSON-LD", "rich…

nowork-studio/notfair-plugin · 99 tokens