CtrlK
BlogDocsLog inGet started
Tessl Logo

audience-analyst

Analyze your audience demographics, behavior, and preferences for targeted content.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./apps/desktop/electron/default-skills/audience-analyst/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The content is a well-structured, concise analytical playbook with concrete steps and a clear output spec. It earns high marks for token efficiency and organization; the only soft spot is the absence of an explicit validation feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, giving analytical framing without explaining what demographics or engagement metrics are; every section earns its place.

5 / 5

Actionability

Concrete, specific guidance ("Identify 2-4 meaningful segments", "build a profile: who they are, how they behave, what they want, when they're active") with a defined output format; minor gaps since it is framing rather than copy-paste procedure.

4 / 5

Workflow Clarity

A clear five-step sequence with soft checkpoints ("Confirm what data you have and its limits", "Be explicit about confidence"), though no explicit validate-fix-retry feedback loop is present.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no bundle files needed; the well-organized sections (When to use, What to look for, How to approach, Output format) satisfy the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

56%Weight 40%Scale 1-5

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 communicates the skill's purpose and domain clearly but lacks an explicit use-trigger clause and uses second-person voice. It is reasonably distinct from sibling skills but would benefit from concrete trigger phrases.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when interpreting follower demographics, engagement patterns, or segment behavior to build personas."

Rewrite in third person ("Analyzes audience demographics...") to match the expected description voice.

Include natural synonyms users would say, such as "audience analysis", "personas", or "segmentation".

DimensionReasoningScore

Specificity

Names the audience domain and a few analysis targets ("demographics, behavior, and preferences") but the single verb "Analyze" is generic; reduced by 1 for second-person voice ("your audience").

2 / 5

Completeness

Clearly states what the skill does but has no "Use when..." trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"audience demographics, behavior, preferences, targeted content" are natural terms a user would say, though a few common synonyms (e.g. "audience analysis", "personas") are missing.

4 / 5

Distinctiveness Conflict Risk

"audience demographics, behavior, and preferences for targeted content" carves a clear niche distinct from general analytics skills, with only minor overlap risk.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
Reviewed

Table of Contents

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.