review-htt
Cross-campaign analysis -- find patterns in what works, with whom, and in what medium. Use when user says 'review campaigns', 'what works', 'show me patterns', 'how am I doing'.
What this skill does
<purpose>
Analyze patterns across all campaigns and outcomes. Surface insights about what communication strategies work, with which audiences, in which mediums, and for which kinds of goals. Uses outcome data, audience profiles, and professional profile to generate actionable insights.
</purpose>
<steps>
<step id="load-config" number="1">
<description>Load Configuration</description>
<load-config>
Resolve the user's home directory (run `echo $HOME` via Bash). Use this absolute path for all file operations below -- never pass `~` to the Read tool.
1. Read `<home>/.things/config.json`
<if condition="config-missing">Tell the user: "Run `/things:setup-things` first." Then stop.</if>
2. Read `<home>/.things/shared/professional-profile.json`
</load-config>
</step>
<step id="load-data" number="2">
<description>Load All Campaign Data</description>
<phase name="campaigns" number="1">
Scan `<home>/.things/heres-the-thing/campaigns/*/campaign.json`. Read all campaigns.
</phase>
<phase name="outcomes" number="2">
Scan `<home>/.things/heres-the-thing/campaigns/*/outcomes/*.json`. Read all outcomes.
</phase>
<if condition="no-campaigns">
Tell the user: "No campaigns found. Create one with `/heres-the-thing:pitch-htt`." Then stop.
</if>
<if condition="no-outcomes">
Note: "No outcomes logged yet. Campaign data available for structure analysis only."
</if>
</step>
<step id="parse-filters" number="3">
<description>Parse Filters</description>
Parse `$ARGUMENTS` for optional filters:
- `--audience <name>`: Filter to campaigns/outcomes involving this person or segment
- `--medium <type>`: Filter to goals using this medium
- `--tag <tag>`: Filter to campaigns/outcomes with this tag
- `--goal-type <type>`: Filter to short_term or long_term goals
Apply filters to the loaded data set.
</step>
<step id="analyze" number="4">
<description>Generate Analysis</description>
<phase name="overview" number="1">
**Campaign Overview**:
- Total campaigns: <n>
- Active: <n>, Delivered: <n>, Closed: <n>
- Total goals: <n> (succeeded: <n>, failed: <n>, active: <n>, pivoted: <n>)
- Total outcomes logged: <n>
</phase>
<phase name="success-patterns" number="2">
**Success Patterns** (from outcomes where result = succeeded or approved_with_conditions):
- What framings/approaches appear in `what_landed` across successful outcomes?
- Common threads in successful strategies
- Which mediums have the best success rate?
</phase>
<phase name="failure-patterns" number="3">
**Failure Patterns** (from outcomes where result = failed):
- What appears in `what_didnt` across failed outcomes?
- Common pitfalls
- Which audience types are hardest to reach?
</phase>
<phase name="audience-insights" number="4">
**Audience Insights**:
- For each person/segment with multiple outcomes:
- Success rate
- What works with them (aggregated from what_landed)
- What doesn't work (aggregated from what_didnt)
- Receptiveness accuracy (predicted vs. actual)
</phase>
<phase name="medium-effectiveness" number="5">
**Medium Effectiveness**:
- Success rate by medium type
- Average prep level at delivery by medium
- Which mediums the user seems strongest in
</phase>
<phase name="skill-progression" number="6">
**Skill Progression** (from feedback_to_system across all outcomes):
- Strengths trending: appearing in recent what_landed
- Weaknesses trending: appearing in recent what_didnt or user_reflections
- Comparison with professional profile strengths/weaknesses
</phase>
<phase name="tag-analysis" number="7">
**Tag Analysis** (if --tag filter or general):
- Most common tags across campaigns
- Tag-specific success rates
- Tag co-occurrence patterns
</phase>
</step>
<step id="present" number="5">
<description>Present Results</description>
Present the analysis in a structured format. Highlight:
- Top 3 actionable insights
- Recommended focus areas
- Suggested next campaigns or prep activities
<template name="review-output">
```
heres-the-thing Review
═══════════════════════
Overview:
Campaigns: <n> (active: <n>, delivered: <n>, closed: <n>)
Goals: <n> total (succeeded: <n>, failed: <n>, pivoted: <n>)
Outcomes: <n> logged
Top Insights:
1. <insight with evidence>
2. <insight with evidence>
3. <insight with evidence>
Success Patterns:
<patterns>
Audience Insights:
<per-audience analysis>
Medium Effectiveness:
<medium> -- <success_rate>% success (<n> goals)
<medium> -- <success_rate>% success (<n> goals)
Skill Progression:
Strengths: <trending strengths>
Areas to work on: <trending weaknesses>
Recommendations:
<actionable next steps>
```
</template>
</step>
</steps>
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".