Run any Skill in Manus with one click

lore-brief

Stars12

Forks2

UpdatedJune 19, 2026 at 23:49

Produces proposal-only Lore continuity briefs for the last 24 hours by default, with cited evidence, open work, learned signals, memory-card candidates, contradiction candidates, and sideEffects:false. Use for daily briefs, recap/continuity summaries, scheduled read-only synthesis, or proposing next actions from Lore without creating anything automatically.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jordanhindo

jordanhindo/lore

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

8 files

SKILL.md

readonly

name	lore-brief
description	Produces proposal-only Lore continuity briefs for the last 24 hours by default, with cited evidence, open work, learned signals, memory-card candidates, contradiction candidates, and sideEffects:false. Use for daily briefs, recap/continuity summaries, scheduled read-only synthesis, or proposing next actions from Lore without creating anything automatically.

Lore Brief

Use this when the user wants a continuity brief, daily recap, or proposal-only synthesis from Lore. Default window is the rolling last 24 hours ending at run time unless the user supplies a window.

Workflow

Compute retrieval bounds: local date label for humans, explicit ISO fromIso/toIso values for output and --since/--until values for Lore commands.
Run lore status --json --since <iso> --until <iso> and stop on unhealthy status. If status is possibly_unsynced and schemaVersion is greater than supportedSchemaVersion, do not recommend bare lore sync as sufficient; say Lore must be updated before write/sync recovery can refresh the window.
Use lore-recall evidence packet rules for searches and citations.
Produce a brief with sideEffects: false.
Propose follow-up objects only. Do not create jobs, issues, wiki pages, skills, tasks, memory cards, code, or automations unless the user asks as a follow-up.

Output Sections

window: fromIso, toIso, timeZone, localDateLabel.
completedActivity: evidence-backed work that finished in the window.
openWork: unresolved work with cited ids or marked uncited.
changes: evidence-backed changes to code, docs, skills, workflow, setup, or state.
learnedSignals: things discovered while briefing.
proposals: read-only suggestions using references/proposal-vocabulary.md.
memoryCardCandidates: decision, claim, commitment, artifact, contradiction, open_question.
contradictionCandidates: both sides with evidence, no averaging.
gaps: optional notes for what Lore could not prove.

Rules

Always state sideEffects: false.
Scheduled use is read-only synthesis, never mutation authority.
Date labels shown to the user use local timezone; retrieval filters use explicit ISO instants.
Contradictions preserve both sides and evidence. Do not resolve unless current artifacts prove a side.
If evidence is stale, label it and propose verification instead of acting.

References

references/brief-schema.md for structure.
references/proposal-vocabulary.md for shared proposal/candidate shapes reused by handoff.
examples/ for good and bad outputs.

More from this repository

same repository

lore

jordanhindo/lore

Use to recall anything from past agent sessions with the server-free `lore` CLI — the "what did we decide", "how did we build X", "why did we drop Y", "find that earlier conversation", "pull context from my last session" task. Trigger whenever you need memory of prior work (yours or another harness's) — searching transcripts by keyword or recency, reading a remembered message back in full, seeing what surrounded it, skimming or jumping around a past session, listing recent sessions, or charting when a project was active. Also covers writing new memory in live (`lore push`). This skill is self-bootstrapping — if the CLI isn't installed or your sessions aren't indexed yet, it covers setup too (detail in references/setup/index.md) — installing lore, indexing or backfilling a harness (Claude Code, Codex, Cursor, Cline, openclaw, Hermes, or any tool that records transcripts), teaching lore a new format by writing and proving an adapter, registering the MCP server, wiring freshness hooks, or feeding a live process

2026-06-2512

lore-handoff

jordanhindo/lore

Builds compact Lore continuation handoff packets with verified/open/stale/risky sections, cited evidence, artifacts, shared proposal vocabulary, unresolved questions, and no transcript dumps. Use when handing work to another agent, resuming later, compacting active work, or preparing next-agent context from Lore.

2026-06-1912

lore-recall

jordanhindo/lore

Plans and executes bounded Lore memory recall with status checks, query expansion, context drill-down, freshness labels, cited evidence packets, and retrieval-failure recovery. Use whenever an agent needs to answer from past Lore sessions, recall decisions, inspect last-session context, verify what happened before, or explain gaps without dumping transcripts.

2026-06-1912

lore-dev-verification

jordanhindo/lore

Verifies changes to the Lore repo and Lore workflow skills. Use when working on Lore PRs, issue slices, recall/brief/handoff skills, CLI/MCP retrieval, store migrations, adapters, privacy/destructive-memory behavior, packaging, or any change that needs proof before it is called done.

2026-06-1912

name	lore-brief
description	Produces proposal-only Lore continuity briefs for the last 24 hours by default, with cited evidence, open work, learned signals, memory-card candidates, contradiction candidates, and sideEffects:false. Use for daily briefs, recap/continuity summaries, scheduled read-only synthesis, or proposing next actions from Lore without creating anything automatically.

Lore Brief

Use this when the user wants a continuity brief, daily recap, or proposal-only synthesis from Lore. Default window is the rolling last 24 hours ending at run time unless the user supplies a window.

Workflow

Compute retrieval bounds: local date label for humans, explicit ISO fromIso/toIso values for output and --since/--until values for Lore commands.
Run lore status --json --since <iso> --until <iso> and stop on unhealthy status. If status is possibly_unsynced and schemaVersion is greater than supportedSchemaVersion, do not recommend bare lore sync as sufficient; say Lore must be updated before write/sync recovery can refresh the window.
Use lore-recall evidence packet rules for searches and citations.
Produce a brief with sideEffects: false.
Propose follow-up objects only. Do not create jobs, issues, wiki pages, skills, tasks, memory cards, code, or automations unless the user asks as a follow-up.

Output Sections

window: fromIso, toIso, timeZone, localDateLabel.
completedActivity: evidence-backed work that finished in the window.
openWork: unresolved work with cited ids or marked uncited.
changes: evidence-backed changes to code, docs, skills, workflow, setup, or state.
learnedSignals: things discovered while briefing.
proposals: read-only suggestions using references/proposal-vocabulary.md.
memoryCardCandidates: decision, claim, commitment, artifact, contradiction, open_question.
contradictionCandidates: both sides with evidence, no averaging.
gaps: optional notes for what Lore could not prove.

Rules

Always state sideEffects: false.
Scheduled use is read-only synthesis, never mutation authority.
Date labels shown to the user use local timezone; retrieval filters use explicit ISO instants.
Contradictions preserve both sides and evidence. Do not resolve unless current artifacts prove a side.
If evidence is stale, label it and propose verification instead of acting.

References

references/brief-schema.md for structure.
references/proposal-vocabulary.md for shared proposal/candidate shapes reused by handoff.
examples/ for good and bad outputs.