learn

Learn

PREREQUISITE: Read ../_mureo-shared/SKILL.md for auth, security rules, output format, and Tool Selection (Read/Write on Code, mureo_strategy_* / mureo_state_* MCP on Desktop / Cowork).

Save a marketing diagnosis insight to the pro-diagnosis knowledge base. Saved insights are loaded at the start of future sessions and applied across /daily-check, /rescue, /budget-rebalance, and the other diagnostic workflows.

The skill persists insights by shelling out to mureo learn add, which routes the write through the KnowledgeStore Protocol. The default backend writes to ~/.claude/skills/_mureo-pro-diagnosis/SKILL.md (preserving the prior file layout); an alternate backend registered via the mureo.runtime_context_factory entry-point group can redirect or split the write without changing this skill.

The knowledge base has two tiers — an operator tier shared across every workspace, and an optional workspace tier scoped to the current one. Use mureo learn tiers to find out which are available before deciding where an insight belongs (step 4).

When to use

• The user runs /learn followed by an insight, e.g.:
  • /learn CV少ないサイトではマイクロCVを活用すべき
  • /learn 予算5000円/日で広告グループ8個は多すぎる
  • /learn Target CPA を下げすぎると逆に CV が減る
• The user runs /learn with no argument — review the current conversation for corrections or marketing expertise the user shared and propose those as insights.

Steps

1. Identify the insight. If the user passed an insight as the argument, use it. Otherwise review the current conversation for moments where the user corrected the agent's analysis or supplied marketing expertise, and select the most reusable one(s).

2. Structure the insight using this template:

   ### [Short descriptive title]
   
   **Situation:** [When this insight applies]
   **Wrong assumption:** [What an inexperienced agent might think]
   **Correct approach:** [The right way to handle this situation]
   **Why:** [The reasoning behind the correct approach]
   
   Date learned: YYYY-MM-DD