growth-os-read

Reads and updates marketing memory stored in the private growth-os GitHub repository.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/chrisschouk/chrisscho-uk-marketing-skills --skill growth-os-read-chrisschouk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: growth-os-read
Source: https://github.com/chrisschouk/chrisscho-uk-marketing-skills/tree/main/skills/shared/growth-os-read
Command: npx skills add https://github.com/chrisschouk/chrisscho-uk-marketing-skills --skill growth-os-read-chrisschouk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Marketing agents lose context between sessions, repeating past mistakes and ignoring customer intel. This Skill defines how to read and update the private growth-os repository so brand knowledge, market feedback, and eval corrections persist across tasks. ## Core Features & Use Cases - Structured memory layout: Documents the growth-os repo structure covering brand folders, daily notes, eval corrections, and market synthesis files. - Read-before-write rules: Specifies which files to check before drafting outreach, customer-facing copy, or brand content for chrisscho.uk, Total Audio Promo, NewsJack, or SpotCheck. - Update conventions: Defines when and how to log corrections, customer quotes, and brand notes with sources and dates. - Use Case: Before writing a cold outreach email for Total Audio Promo, check the tap brand folder for artist excludes and pricing, then review eval corrections to avoid repeating a failed message pattern. ## Quick Start Read the growth-os repo brand notes and eval corrections for Total Audio Promo before drafting my outreach email.

Frequently Asked Questions about growth-os-read

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent persistent marketing memory?▼

Store brand intel, customer quotes, and corrections in a structured repository like growth-os, then instruct the agent to read relevant folders before drafting and append updates after interactions. This keeps context across sessions without retraining.

What should I check before writing outreach copy with an agent?▼

Check the brand folder for excludes, pricing, and voice notes, review the market synthesis file for current customer feedback, and read eval corrections if the task type has failed before. This prevents repeated mistakes and off-brand messaging.

How do I document agent failures so they don't repeat?▼

Log each failure in an eval corrections file with what went wrong, the root cause, and the fix. Agents read this file before repeating similar tasks, creating a feedback loop that improves output over time.

Can I store API keys in a marketing memory repo?▼

No. Credentials and API keys belong in your harness's secrets or environment variables, never in the memory repository. The repo should hold only brand intel, market notes, and corrections.

What content should not go into a marketing knowledge base?▼

Exclude generic marketing frameworks, copy-pasted playbooks, and anything already documented in your public skills pack. The memory repo is for specific customer intel, quotes with sources, and lessons from failures.