mureo-strategy

Manage STRATEGY.md and STATE.json files for strategy-driven ad operations.

37|3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/logly/mureo --skill mureo-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mureo-strategy
Source: https://github.com/logly/mureo/tree/main/skills/mureo-strategy
Command: npx skills add https://github.com/logly/mureo --skill mureo-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategy context management to keep STRATEGY.md and STATE.json aligned with business goals across ad operations.

Core Features & Use Cases

  • Read STRATEGY.md sections and map to context types (persona, usp, target_audience, brand_voice, market_context, operation_mode, custom, deep_research, sales_material, goal).
  • Maintain and upsert STATE.json campaign snapshots and action logs to support iterative optimization.
  • Drive strategy-guided decisions by providing a consistent context for AI agents.

Quick Start

Create STRATEGY.md with Persona, USP, and Goals, then allow the agent to use STATE.json to guide strategy-driven ad operations.

Frequently Asked Questions about mureo-strategy

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

FAQPage Schema
How do I manage strategy context for AI-driven ad operations?

You can manage strategy context by structuring STRATEGY.md with business goals and mapping its sections to specific context types. This ensures your AI agents receive consistent strategy-driven guidance for campaigns.

What is the best way to maintain campaign state for iterative ad optimization?

Maintaining campaign state involves upserting STATE.json snapshots and action logs. This tracks iterative optimization progress and provides a historical record for strategy-guided decisions.

How do I map STRATEGY.md sections to specific campaign contexts like persona and USP?

You map STRATEGY.md sections by assigning them to defined context types such as persona, usp, target_audience, brand_voice, market_context, operation_mode, custom, deep_research, sales_material, and goal.

Do I need a STRATEGY.md file to run strategy-driven ad operations?

Yes, creating a STRATEGY.md file with Persona, USP, and Goals is required. The agent then uses this file alongside STATE.json to align ad operations with your business strategy.

What's the difference between STATE.json and STRATEGY.md in campaign planning?

STRATEGY.md defines your static business strategy and context mappings, while STATE.json manages the dynamic campaign snapshots and action logs for ongoing iterative optimization.

Can I log ad operations actions using STATE.json for strategy alignment?

Yes, STATE.json supports action logs and lifecycle management. Logging actions in STATE.json keeps your ad operations aligned with the defined strategy context over time.