agent-persona-creator

Design and draft AI agent persona documents for agent marketplaces, especially agency-agents style profiles. Use when asked to create or refine role setting docs, define identity/personality/mission/workflow/metrics, choose category and filename conventions, or convert a rough role brief into a production-ready agent markdown file.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-sequenced with a validation checkpoint, and uses progressive disclosure effectively with real reference files. The main gap is actionability: it references a scaffolding script that does not exist in the bundle.

Suggestions

Either add the missing `scripts/create_agent_profile.py` to the bundle or replace the reference with inline, copy-paste-ready scaffold instructions (frontmatter + section headings) so the step is executable without a non-existent file.

Verify `scripts/lint-agents.sh` is also bundled or note explicitly that it lives in the target agency-agents repository, to avoid pointing Claude at a missing artifact.

Consider showing a minimal agent-profile template inline in Step 4 so the draft step is actionable even when the script is unavailable.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven with no over-explanation of concepts Claude already knows; every line (Inputs To Collect, the five workflow steps, Output Contract) carries operational value, matching the score-3 lean-and-efficient anchor.	3 / 3
Actionability	Guidance is concrete in places (named sections, a verification checklist, `bash scripts/lint-agents.sh`), but it directs the user to `scripts/create_agent_profile.py` which is not present in the bundle, leaving a key step without a working executable artifact — the score-2 "incomplete / missing key details" anchor rather than fully copy-paste ready.	2 / 3
Workflow Clarity	A clear five-step sequence culminates in Step 5: Self-Review Before Handover with explicit validation checks (frontmatter fields, required sections, measurable KPI with a number, no generic filler), matching the score-3 anchor for a clear sequence with explicit validation steps and a checklist.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview with a dedicated Reference Map pointing one level deep to two real, existing files (references/agency-agents-patterns.md, references/persona-design-canvas.md), each clearly signaled, matching the score-3 clear-overview-with-well-signaled-one-level-deep-references anchor.	3 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-scoped to a distinct niche, with an explicit "Use when" trigger clause. Its only weakness is a reliance on repository-specific jargon that limits the breadth of natural trigger terms a general user would say.

Suggestions

Broaden trigger terms with more generic phrasings a non-repository user might say, e.g. "create an agent profile", "define an agent's role and personality", or "write a role-setting document".

Consider adding a short synonym list (e.g. "agent profile, role setting doc, persona brief") to increase natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as "Design and draft AI agent persona documents", "define identity/personality/mission/workflow/metrics", and "convert a rough role brief into a production-ready agent markdown file", matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Design and draft AI agent persona documents") and when ("Use when asked to create or refine role setting docs..."), matching the score-3 anchor for clearly answering both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Includes relevant natural phrases like "create or refine role setting docs" and "convert a rough role brief", but leans on repository-specific jargon ("agency-agents style profiles", "category and filename conventions") and misses more common variations a general user might say, fitting score 2 rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (agent marketplace persona documents, agency-agents profiles) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 clear-niche anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: Jamailar/Beav
Path: desktop/electron/system-skills/agent-persona-creator/SKILL.md
Commit: 0b80606

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.