← ClaudeAtlas

learnlisted

Save a marketing diagnosis insight to the pro-diagnosis knowledge base so it is applied in future operations across all platforms. Use when the user runs /learn, explicitly teaches the agent a marketing insight, corrects the agent's analysis, or asks to remember/record an operational learning for next time.
logly/mureo · ★ 9 · AI & Automation · score 75
Install: claude install-skill logly/mureo
# 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. ## 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