SkillsAdd

jordanhindo/lore · Archived

lore-brief

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.

First seen Jun 20, 2026

Installation

$ npx skills add jordanhindo/lore --skill lore-brief
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

lore Same source · more installs
jordanhindo/lore

Use to recall anything from past agent sessions with the server-free `lore` CLI — the "what did…

4 installs
lore-recall Same source
jordanhindo/lore

Plans and executes bounded Lore memory recall with status checks, query expansion, context dril…

2 installs
lore-handoff Same source
jordanhindo/lore

Builds compact Lore continuation handoff packets with verified/open/stale/risky sections, cited…

2 installs
lore-dev-verification Same source
jordanhindo/lore

Verifies changes to the Lore repo and Lore workflow skills.

2 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from jordanhindo/lore.

npx skills add jordanhindo/lore
lore 4 lore-recall 2 lore-handoff 2 lore-dev-verification 2

Browse all from jordanhindo/lore

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 14
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,616 B
  • docs SUMMARY.md 377 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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

  1. Compute retrieval bounds: local date label for humans, explicit ISO fromIso/toIso values for output and --since/--until values for Lore commands.
  2. 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.
  3. Use lore-recall evidence packet rules for searches and citations.
  4. Produce a brief with sideEffects: false.
  5. 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.