Memorb domain query
Skill iamjosuho/memOrb/skills/extensions/memorb-domain-query
Agent-Agnostic Second Brain memory framework inspired by movie and library science.
npx -y skills add iamjosuho/memOrb --skill memorb-domain-queryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when querying companies, employees, or contacts by email address, domain name, or company name, or when integrating Outlook/M365 email collection and company email status checks.
SKILL.md
5.3 KB, as published. Nobody here has run it
π Memory Domain Query & Email Integration
Overview
Bi-directional query workflow connecting Email Addresses, Domains, and Company Wikis in Second Brain, integrated with Outlook/M365 email operations.
Core Principle: Domain is the primary digital identifier linking company wikis (memorbs/Long-Term/Orgs/), employee profile notes (memorbs/Long-Term/People/), and external email systems (M365/Outlook).
When to Use
Trigger this skill when:
- User provides an email address (e.g.,
[email protected]) to identify the owner or company. - User provides a domain (e.g.,
acme.com), asking for associated company records and contacts. - User asks for a company's domains and employee contact list.
- Outlook/M365 Email Ingestion: Categorizing incoming emails based on sender domain.
- Company Email Status Checks: User asks "Are there any new emails from [Company Name]?"
π Workflows
flowchart TD
StartInput[Trigger / Event] --> CheckType{Trigger Type?}
CheckType -- Email / Domain --> ModeA[Mode A: Query Company & People by Domain/Email]
CheckType -- Company Name --> ModeB[Mode B: Query Domain & Emails by Company Name]
CheckType -- Email Ingestion --> ModeC[Mode C: Auto-attribute Sender Domain]
CheckType -- Company Email Check --> ModeD[Mode D: Domain List β Outlook Query]
ModeA --> QueryOrgByDomain[1. Grep memorbs/Long-Term/Orgs/ for domain]
QueryOrgByDomain --> QueryPeopleByEmail[2. Grep memorbs/Long-Term/People/ for contact info]
QueryPeopleByEmail --> CombineA[3. Return Company Wiki & Contacts]
ModeB --> FindCompanyWiki[1. Read Company Wiki frontmatter]
FindCompanyWiki --> ListPeopleEmail[2. Run Dataview for Employee Emails]
ListPeopleEmail --> CombineB[3. Return Domains & Employee Directory]
ModeC --> ExtractSenderDomain[1. Parse Sender Email @domain]
ExtractSenderDomain --> MatchCompany[2. Lookup Company Wiki by domain]
MatchCompany --> TagNote[3. Associate Email Note with Company Wiki]
ModeD --> LookupCompanyDomain[1. Retrieve Company domain list]
LookupCompanyDomain --> QueryOutlook[2. Search M365/Outlook using @domain]
QueryOutlook --> SummarizeEmails[3. Summarize & Report Recent Emails]
Mode A: Email / Domain β Company & People
- Search Company Wiki Domain:
Search
memorbs/Long-Term/Orgs/for YAMLdomainarray or body references:grep -ri "domain:.*acme.com" "$VAULT/memorbs/Long-Term/Orgs/" --include="*.md" - Search Employee Profile Notes:
Search
memorbs/Long-Term/People/forcontactChannels.emailor inline domain references:grep -ri "acme.com" "$VAULT/memorbs/Long-Term/People/" --include="*.md" - Output: Return matched Company Wiki link, company background, and list of associated personnel.
Mode B: Company Name β Domains & Emails
- Locate Company Wiki:
Open target note (e.g.,
memorbs/Long-Term/Orgs/12345678-Acme-Corp.md). - Extract
domainArray: Readdomainfrontmatter field (e.g.,[acme.com, acme.org]). - Query Employee Directory:
Run Dataview or Grep to aggregate employee emails:
TABLE title AS "Title", contactChannels.email AS "Email", domain AS "Domain" FROM "memorbs/Long-Term/People" WHERE (company = [[12345678-Acme-Corp]] OR contains(file.folder, "memorbs/Long-Term/People/Acme")) WHERE relationshipType != null OR contains(tags, "people")
Mode C: Outlook/M365 Email Ingestion Attribution
- Upon receiving an external email or daily ingestion, extract sender email (
sender_email = "[email protected]"). - Parse sender domain (
domain = "acme.com"). - Search
memorbs/Long-Term/Orgs/wheredomaincontainsacme.com. - Associate email summary with matched Company Wiki and Person Note.
Mode D: Querying Recent Emails for a Company
- User prompt: "Are there any new emails from Acme Corp?"
- Step 1 (Vault Lookup): Retrieve Acme Corp's
domainarray ([acme.com, acme.org]). - Step 2 (Outlook Query): Execute Outlook/M365 query with filter
from:acme.com OR from:acme.org. - Step 3 (Report): Summarize latest email subject, sender, timestamp, and key action items.
π Dataview Reference Template
To embed an employee directory in a Company Wiki note:
TABLE title AS "Title", contactChannels.email AS "Email", department AS "Department"
FROM "memorbs/Long-Term/People"
WHERE (company = [[12345678-Acme-Corp]] OR contains(string(company), "Acme") OR contains(file.folder, "memorbs/Long-Term/People/Acme"))
WHERE (relationshipType != null OR contains(tags, "people")) AND !contains(file.name, "Interview") AND !contains(file.name, "Review")
SORT department ASC
Common Mistakes & Red Flags
| Anti-Pattern | Correct Approach |
|---|---|
| String comparison failure on domain | YAML domain is an array. Use contains(string(domain), "domain.com") in Dataview |
Missing contactChannels.email | Check both YAML frontmatter and note body for email addresses |
| Querying emails by employee name | Always query Outlook by full domain list (from:domain.com) to catch new contacts |