oneafrikan/the-grid / agent-factory/roles/martech
martech
Unverified| File | Kind | Size |
|---|---|---|
| AGENTS.md | markdown | 3.7 KB |
| IDENTITY.md | markdown | 914 B |
| MEMORY.md | markdown | 1.9 KB |
| SKILL.md | skill md | 7.5 KB |
| SOUL.md | markdown | 4.9 KB |
| USER.md | markdown | 841 B |
| role.yaml | config | 1.4 KB |
MEMORY.md
View on GitHub<!--
MEMORY.md — Marketing Technology Specialist role memory seed (flat-file / signals model).
This file is APPENDED to _core/MEMORY_base.md at compose time.
Headings match MEMORY_base.md where they overlap so the merge reads cleanly.
Phase-1: plain markdown. A queryable DB (gbrain) replaces this later —
keep sections dumb and portable. No SQL, no structured query syntax.
A specialist CONSUMES stack/priority decisions (set by the operator /
growth-hacker); it records the systems it audited, what it specified, and what
was verified. Leave a section blank rather than guessing — blank is honest;
wrong breaks tracking or messages the wrong people. No PII here.
-->
# Memory (Marketing Technology Specialist seed)
## Stack inventory
<!--
The systems in play and how they connect, as configured (not assumed).
Format: - `<system / property / portal>` → role: <what it does> | feeds: <downstream> | owner: <who approves changes>
-->
_None yet._
## Audit findings
<!--
Open and resolved findings from tracking, consent and data-flow audits, ranked by risk.
Format: - [open|resolved] <severity> — <finding> → <fix> (owner: <agent/human>) | verify: <step>
-->
_None yet._
## Naming & schema decisions
<!--
Agreed event names, UTM conventions, field names, lifecycle definitions.
Format: - <convention> → <rule> (source of truth: <doc>)
-->
_None yet._
## Active work
<!-- What is in flight. Format: - **<System/Property>** — goal: <audit/design/fix> | Status: <status> | PR: #<n> -->
_None yet._
## Recent changes
<!-- Dated log of specs handed off and what was verified. Append; do not overwrite.
Format: - YYYY-MM-DD: <what was specified/applied> — <verification result, or "not yet verified"> -->
_None yet._
## Learned preferences
<!-- Observed preferences of the operator — approval chain, regions and consent
policy, how much to ask vs proceed, report shape and cadence. -->
_None yet._
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |