fsbtactic-code/marketing-brain-skill / skills/marketing-brain
marketing-brain
FlaggedCreate, improve, research, or audit marketing strategy and execution using a bundled marketing library, verified live primary sources for volatile facts, and clearly labeled agent judgment. Use for full marketing systems, audits, landing pages and CRO, competitor intelligence, brand voice, audience and JTBD research, email sequences, SMM and social content systems, paid ads, headlines, copywriting, positioning, offers, launches, GTM, growth, funnels, retention, pricing, SEO, analytics, attribution, experiments, and consumer or buyer psychology. Trigger for English and Russian requests, including requests for ready-to-use assets.
assets/templates/issue-registry.md
View on GitHub# Marketing Issue Registry
Use one row per observable issue. Keep facts separate from the proposed mechanism.
| Issue ID | Priority | Observation | Exact location | Evidence | Funnel stage | Loss mechanism | Confidence | Recommended change | Minimum validation | Primary metric | Guardrail | Owner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| I-001 | P1 | [what is visible] | [URL, screen, event, file] | [source] | [stage] | [why it may matter] | high, medium, low | [change] | [test] | [metric] | [guardrail] | [role] |
## Priority rubric
- `P1`: blocks conversion, measurement, launch safety, or a critical customer path.
- `P2`: high-value fix with strong evidence and manageable effort.
- `P3`: useful improvement that depends on P1 or P2 work.
- `P4`: experiment with meaningful uncertainty.
- `P5`: monitor, document, or revisit when inputs change.
## Coverage status
| Surface | Access | Evidence coverage | Status | Missing data |
|---|---|---|---|---|
| [surface] | full, partial, none | strong, mixed, weak | PASS, NEEDS_DATA, BLOCKED | [data] |
Do not assign a numeric score when a surface could not be inspected. Use `NEEDS_DATA` or `BLOCKED`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |