菜单
Structured decision and pattern logging. Guides Solara through writing high-quality entries to memory/DECISIONS.md, memory/PATTERNS.md, or memory/MISTAKES.md with proper frontmatter, cross-links, and version tags.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Mandatory compliance gate before any outbound (email, SMS, blast). Verifies consent, opt-out status, CASL footer, send window, and daily cap.
Queue a cold outreach campaign to a segmented lead list via the cold_outreach_campaigns endpoint, with CASL compliance enforced before any send.
Generates the structured daily call sheet for Ezra — 6 prioritized categories, specific opening lines for each call, and a clear action order.
Surfaces overdue follow-ups, prioritizes the call list, and recommends specific outreach actions for each stuck deal or contact.
Domain literacy for MCA and alternative business funding. Reference glossary and clarifying-question guide for when operators use ambiguous terms.
Uses historical lender feedback data to recommend the best lenders for a specific deal profile and surfaces typical terms and decline patterns.
| name | memory-journaling |
| description | Structured decision and pattern logging. Guides Solara through writing high-quality entries to memory/DECISIONS.md, memory/PATTERNS.md, or memory/MISTAKES.md with proper frontmatter, cross-links, and version tags. |
| tags | ["skill","memory","journaling","decisions","patterns"] |
| triggers | ["log a decision","journal this","memory journal","log this pattern","record this","save this learning","memory-journaling"] |
| owner | solara |
| tier | stable |
| risk | low |
Memory drifts when entries are written ad-hoc — bullet here, paragraph there, no cross-links, no last_updated field, dates omitted. This skill enforces structure: every journal entry has a category, a date, a body shape per category, wiki-links to related files, and a freshness tag.
When to invoke:
Trigger: /journal <category>, "log a decision", "save this pattern"
Pick the right file. If unsure, ask Ezra.
| Category | File | Use for |
|---|---|---|
| Decision | memory/DECISIONS.md | Lender strategy choices, compliance calls, product bets, scope cuts |
| Pattern | memory/PATTERNS.md | Validated approaches that worked — repeat-worthy workflows |
| Mistake | memory/MISTAKES.md | Failure modes — what went wrong, why, prevention |
| Client Context | memory/CLIENT_CONTEXT.md | New facts about Ezra's team, lender book, deal volume |
## YYYY-MM-DD — <one-line title>
**Context:** What was the situation? Constraints?
**Decision:** What we chose. Be specific — names, numbers, lender names, deal IDs.
**Why:** The reasoning. Tradeoffs accepted.
**Alternatives rejected:** What else was on the table + why we passed.
**Related:** [[memory/CLIENT_CONTEXT]] | [[skills/lender-intelligence/SKILL.md]] | (commit or deal ID if applicable)
## [P] / [V] — <pattern name>
**Pattern:** One sentence — what the pattern is.
**When:** The trigger condition.
**How:** The step-by-step.
**Why it works:** The mechanism.
**Uses:** N (increment per re-use; promote [P] → [V] at 3)
**First seen:** YYYY-MM-DD | **Last validated:** YYYY-MM-DD
**Related:** [[skills/X/SKILL.md]]
Probationary [P] → validated [V] after 3 successful re-uses. Track the count in the body.
## YYYY-MM-DD — <short title>
**Failure:** What happened (1-2 sentences, observable).
**Root cause:** Why it happened — the actual cause, not the symptom.
**Prevention:** Concrete rule or system change that prevents recurrence.
**Tag:** [compliance | workflow | lender | data | communication]
If the mistake is a workflow gap (e.g., "forgot to run CASL check before sending"), add a check to the relevant skill's guardrails section.
[[wiki-link]] syntax.memory/MEMORY.md index if the entry is high-leverage (something future-Solara needs without grepping). One-line pointer: - [Title](file.md) — one-line hook.