Menu

Individual skill

Cortex

0upvotes

LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people or company note, ingest, contradictions, knowledge graph, retrieve, mine conversations, distill, weekly digest, cortex digest, context search, prior work, recall, remember, remember when we, previous sessions, context recovery, what did we do, what did we do with, we just worked on, didn't we already fix, why did we change, find session, search history, resume, pick up where we left off, cold start, yesterday's work, last week, the one about. NOT FOR published-content search, or mining one piece of content for the system.

LifeOS/install/skills/Cortex/SKILL.md

Read pinned source

Source commit b7efec97d8c3885feee285bee468c35602fb0606

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
19,782
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Cortex

**Contents:** Ideal State · Anti-criteria · Intent Routing · Tool contract · Data & Config · Gotchas · Examples

Search and manage the typed Knowledge Archive, recall prior LifeOS work, or capture and digest problem-solving learnings. Every archive note is typed into one of six canonical entity domains (`KnowledgeSchema.ts` CANONICAL_TYPES): People (individuals, public figures, contacts with relationship context), Companies (organizations, businesses, teams with structure and positioning), Ideas (concepts, theses, frameworks, thought patterns across work and life), Research (findings, studies, deep-dive topics with source citations and evidence), Books (published works with claim summaries, key quotes, and implications), and Blogs (blog posts and articles with takeaways, relationships to other notes).

## Ideal State

- A recall answer names the prior sessions, ISAs and decisions that match, ranked, each with its date and path, and states what was decided or done there rather than only the topic; when nothing matches, it says so and names the query and the sources searched.
- An archive search returns a deduplicated table of matching notes (title, domain, status, tags), or an explicit "no matches" with a suggested next step; retrieve returns the top matching notes ranked, with compressed summaries.
- A captured learning tells the problem, assumption, reality, journey with its dead ends, solution and takeaway, filed under `LEARNING/SYSTEM/YYYY-MM/` or `LEARNING/ALGORITHM/YYYY-MM/`; a recent-history digest lists the files it read and says nothing they do not.
- All archive operations (`add`, `harvest`, `develop`, `ingest`) classify each note into one of the six canonical KNOWLEDGE note types and add typed cross-links (`related:` frontmatter) between notes to keep the graph connected: every new note carries the eight envelope fields and 2-4 typed `related:` links, each naming a slug that exists in the archive.
- Every result comes from the command's loaded deterministic tools, and any verification that was unavailable is named in the result as unavailable, never reported as passed.
Back to top