setup-htt
Initialize heres-the-thing -- create campaign directories, preferences, deliverable type registry, notification system, and register collections with things. Use when user first uses heres-the-thing or says 'set up heres-the-thing'.
What this skill does
<purpose>
Configure heres-the-thing and register its collections with things. Creates the `~/.things/heres-the-thing/` directory structure, initializes the deliverable type registry with builtin types, sets notification preferences, and optionally installs the macOS launchd notification agent.
</purpose>
<steps>
<step id="check-prerequisites" number="1">
<description>Check Prerequisites</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 to initialize your .things directory." Then stop.</if>
2. Read `<home>/.things/registry.json`
<if condition="registry-missing">Tell the user: "Run `/things:setup-things` first." Then stop.</if>
3. Check if `<home>/.things/heres-the-thing/preferences.json` exists
<if condition="preferences-exist">Show current settings and ask (via AskUserQuestion) if they want to reconfigure.</if>
</load-config>
</step>
<step id="create-directories" number="2">
<description>Create Directory Structure</description>
```bash
mkdir -p <home>/.things/heres-the-thing/campaigns
mkdir -p <home>/.things/heres-the-thing/audiences
mkdir -p <home>/.things/heres-the-thing/deliverable-types
mkdir -p <home>/.things/heres-the-thing/scripts
```
</step>
<step id="gather-preferences" number="3">
<description>Gather Preferences</description>
Use AskUserQuestion:
Do you want to enable scheduled notifications for campaign check-ins?
<options>
- Yes -- remind me about upcoming target dates and post-delivery check-ins
- No -- I'll check manually
</options>
<if condition="notifications-enabled">
Use AskUserQuestion:
When should notifications be quiet?
<options>
- Default (9pm - 8am)
- Custom (I'll specify)
</options>
<if condition="custom-quiet-hours">Ask for start and end times.</if>
</if>
</step>
<step id="write-preferences" number="4">
<description>Write Preferences</description>
<output-path>`<home>/.things/heres-the-thing/preferences.json`</output-path>
```json
{
"notifications": {
"enabled": true,
"check_interval_minutes": 60,
"reminder_windows": ["7d", "2d", "1d", "3h", "1h"],
"post_delivery_checkin_days": [1, 3, 7],
"quiet_hours": { "start": "21:00", "end": "08:00" }
}
}
```
<rule>Adjust `enabled` and `quiet_hours` based on user answers.</rule>
</step>
<step id="write-deliverable-types" number="5">
<description>Initialize Deliverable Type Registry</description>
<output-path>`<home>/.things/heres-the-thing/deliverable-types/index.json`</output-path>
```json
{
"version": "1.0.0",
"types": {
"strategy_brief": {
"id": "strategy_brief",
"name": "Strategy Brief",
"description": "Full 5-page positioning strategy document",
"builtin": true,
"template": null,
"output_format": "md",
"requires": { "tools": ["Write"], "mcp_servers": [], "external": [] }
},
"meeting_prep_doc": {
"id": "meeting_prep_doc",
"name": "Meeting Prep Doc",
"description": "Printable reference document with talking points, key phrases, and traps to avoid",
"builtin": true,
"template": null,
"output_format": "md",
"requires": { "tools": ["Write"], "mcp_servers": [], "external": [] }
},
"objection_map": {
"id": "objection_map",
"name": "Objection Map",
"description": "Anticipated pushback with prepared responses, ordered by likelihood",
"builtin": true,
"template": null,
"output_format": "md",
"requires": { "tools": ["Write"], "mcp_servers": [], "external": [] }
},
"artifact_draft": {
"id": "artifact_draft",
"name": "Artifact Draft",
"description": "The actual deliverable -- email, proposal, document, slide outline",
"builtin": true,
"template": null,
"output_format": "md",
"requires": { "tools": ["Write"], "mcp_servers": [], "external": [] }
},
"prep_plan": {
"id": "prep_plan",
"name": "Prep Plan",
"description": "Time-boxed preparation schedule with milestones and checkpoints",
"builtin": true,
"template": null,
"output_format": "md",
"requires": { "tools": ["Write"], "mcp_servers": [], "external": [] }
},
"follow_up_template": {
"id": "follow_up_template",
"name": "Follow-Up Template",
"description": "Post-delivery follow-up draft based on goals and anticipated outcomes",
"builtin": true,
"template": null,
"output_format": "md",
"requires": { "tools": ["Write"], "mcp_servers": [], "external": [] }
}
}
}
```
</step>
<step id="install-notify-script" number="6">
<description>Install Notification Script</description>
<if condition="notifications-enabled">
Copy the notification script to the data directory:
Read the notify.sh script from the plugin source (use Glob to find it under the plugin's `scripts/` directory).
Write it to `<home>/.things/heres-the-thing/scripts/notify.sh`.
```bash
chmod +x <home>/.things/heres-the-thing/scripts/notify.sh
```
Use AskUserQuestion:
Install macOS launchd agent for scheduled notifications?
<options>
- Yes -- run every hour (Recommended)
- No -- I'll run the script manually
</options>
<if condition="install-launchd">
Read the install-launchd.sh script from the plugin source.
Run it:
```bash
bash <plugin-source>/scripts/install-launchd.sh <home>/.things/heres-the-thing/scripts/notify.sh <check_interval_minutes>
```
</if>
</if>
</step>
<step id="register-collections" number="7">
<description>Register Collections with things</description>
Read `<home>/.things/registry.json`. Add the following collection definitions:
```json
{
"heres-the-thing/campaigns": {
"plugin": "heres-the-thing",
"description": "Positioning campaigns with goals, audience, and tracked outcomes",
"tags_field": "json.tags",
"item_structure": {
"type": "directory_per_item",
"required_files": ["campaign.json"],
"optional_file_patterns": ["strategy/*.md", "artifacts/*", "outcomes/*.json"]
},
"index_schema": {
"required_fields": {
"id": "string",
"status": "string",
"created": "date",
"tags": "string[]"
},
"optional_fields": {
"subject": "object",
"goals": "object[]"
}
},
"master_index": null,
"rebuild_command": null
},
"heres-the-thing/audiences": {
"plugin": "heres-the-thing",
"description": "Reusable audience segment profiles",
"tags_field": "json.tags",
"item_structure": {
"type": "flat_files",
"file_pattern": "*.json"
},
"index_schema": {},
"master_index": null,
"rebuild_command": null
},
"heres-the-thing/outcomes": {
"plugin": "heres-the-thing",
"description": "Outcome logs across all campaigns",
"tags_field": "json.tags",
"item_structure": {
"type": "flat_files",
"file_pattern": "campaigns/*/outcomes/*.json"
},
"index_schema": {},
"master_index": null,
"rebuild_command": null
}
}
```
Write the updated rRelated 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".