resolve-before-asking

Resolves entity identities via brain lookup chain before escalating questions to users.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill resolve-before-asking-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-before-asking
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/resolve-before-asking
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill resolve-before-asking-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often ask users "who is X?" when the answer already exists in their knowledge base, wasting user attention on questions the system can answer itself. This Skill gates every identity, role, or relationship question behind an exhaustive lookup chain so the user is only bothered as a last resort. ## Core Features & Use Cases - Ordered Lookup Chain: Runs think/synthesis, search plus full page reads, mounted source queries (email, calendar, chat), timeline and graph traversal, then web search before any escalation. - Hypothesis-Led Escalation: When asking is justified, the question leads with a best-guess hypothesis, states what was searched and found, and uses a 2-4 option choice gate. - No-Placeholders-at-Ingest Rule: Post-ingestion passes resolve relationship and role fields on newly created people/company pages, eliminating placeholder text like "[To be filled by content analysis]". - Use Case: During a bulk email import that creates 100+ contact pages, run this Skill to fill each person's relationship and role from the imported signals, so briefings never show "unknown relationship" entries. ## Quick Start Before asking me who a contact is, run the full brain lookup chain and only escalate with a hypothesis if nothing resolves them.

Frequently Asked Questions about resolve-before-asking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an AI agent from asking who a contact is?

Route identity questions through a lookup chain that checks the knowledge base first: synthesis, page reads, mounted sources, timeline, and graph. Only escalate to the user after all steps return nothing conclusive, and always lead with a hypothesis.

How to resolve unknown relationships in a knowledge base automatically?

Run a post-ingestion pass over created pages: scan for placeholder markers, synthesize across the batch's signals, extract relationship type and role, then update the page's frontmatter and context section. Batch 10-20 pages at a time for large imports.

When should an AI agent escalate a question to the user?

Escalate only after synthesis, search, mounted source queries, timeline/graph traversal, and web search all fail to produce a clear answer. The escalation must state what was searched, what was found, and offer a confirmable hypothesis.

Does this work with email and calendar data sources?

Yes, the chain queries whatever sources are mounted, including email archives, calendar imports, chat transcripts, and meeting notes. Subject lines and meeting titles typically reveal the relationship, and sender domains seed hypotheses.

What are the limitations of automated entity resolution?

Contradictory or very sparse signals produce low confidence, requiring user confirmation with a stated hypothesis. A nonzero search hit count is not proof; pages must be read and synonym phrasings queried before concluding an entity is unknown.