audience-analyst
Analyze your audience demographics, behavior, and preferences for targeted content.
git clone --depth 1 https://github.com/holaboss-ai/holaOS /tmp/audience-analyst && cp -r /tmp/audience-analyst/apps/desktop/electron/default-skills/audience-analyst ~/.claude/skills/audience-analystSKILL.md
# Audience Analyst Work like a growth analyst who turns raw audience data into a clear picture of who's actually out there and what they respond to. The output should change what the team makes and who they make it for — not just describe the followers. ## When to use this skill Use Audience Analyst when there's audience or engagement data to interpret: follower demographics, interaction patterns, segment behavior, content preferences. The goal is to build usable personas and segment-level recommendations. If the task is reporting on content/account performance over time, use Performance Reporter instead. ## What to look for - **Segments, not averages.** A single "average follower" hides the truth. Find the distinct groups inside the audience by behavior, demographics, and needs. - **Behavior over vanity.** Weight what people *do* (save, share, reply, convert, return) above raw follower counts. - **Value, not just size.** A small segment that engages and converts can matter more than a large passive one. Identify the high-value groups. - **Preference signals.** Tie segments to the content themes, formats, and times that actually move them. ## How to approach the analysis 1. Confirm what data you have (demographics, engagement metrics, timestamps, source platform) and its limits. 2. Identify 2-4 meaningful segments — enough to be actionable, few enough to act on. 3. For each segment, build a profile: who they are, how they behave, what they want, when they're active. 4. Rank segments by value to the brand's goals. 5. Translate each profile into concrete content recommendations: themes, formats, timing, and messaging that fit that group. Be explicit about confidence. Small samples and platform-reported demographics are directional, not gospel — say so rather than over-claiming. ## Output format Return an actionable audience read: - **Segments** — for each: a short name, who they are, key behaviors, and what they want (their job-to-be-done). - **Priority** — which segments to focus on and why. - **Recommendations** — per segment, the content themes, formats, timing, and tone to use. - **Caveats** — sample size and data-quality limits worth knowing. Lead with the segments and the "so what," not with a data dump.
Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.
Use when working in the embedded browser and you want the cheapest reliable interaction loop.
Use when validating or debugging a workflow in the embedded browser and you need a reproducible, evidence-first loop.
Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a `src/client/` UI surface. NOT for marketing pages, NOT for snapshot HTML reports.
Guide for assembling a workspace capability (skills + integrations). Use when the user wants to create a capability.
Research competitors and produce a weekly digest of their positioning, launches, and messaging.
Plan and organize your content calendar with AI-driven scheduling and topic suggestions.
Generate high-quality written content for any platform with AI-powered drafting and editing.