Install
$ agentstack add skill-jordanhindo-lore-lore-brief ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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/toIsovalues for output and--since/--untilvalues for Lore commands. - Run
lore status --json --since --untiland stop on unhealthy status. If status ispossibly_unsyncedandschemaVersionis greater thansupportedSchemaVersion, do not recommend barelore syncas sufficient; say Lore must be updated before write/sync recovery can refresh the window. - Use
lore-recallevidence 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 usingreferences/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.mdfor structure.references/proposal-vocabulary.mdfor shared proposal/candidate shapes reused by handoff.examples/for good and bad outputs.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jordanhindo
- Source: jordanhindo/lore
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.