Ask Across Everything
SkillDocs & knowledgeLets your agent answer questions by combining stored company knowledge with live data from analytics, mail, and dispatch.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Ask Across Everything skill
About this skill
Use when a Brain question asks across company memory plus live/app-owned data such as metrics, email threads, workspace grants, or secrets.
What this skill tells your AI
The instructions your AI receives, as published by builderio/agent-native in templates/brain/.agents/skills/ask-across-everything/SKILL.md and read by ahel’s review.
Rule
Search Brain first, inspect federatedCoverage, then delegate live app-owned
questions to the owning specialist agent with call-agent.
Why
Brain owns cited company memory: reviewed knowledge, accessible raw captures,
and source records. It does not directly search Analytics, Mail/Gmail,
Dispatch, or sibling app databases. federatedCoverage is deterministic routing
metadata, not retrieved evidence.
Workflow
- Call
search-everythingfor broad questions, or useask-brainwhen the user asks a direct cited-memory question and wants an answer immediately. - Read the Brain results and
federatedCoverage.scopeNote. - Inspect
federatedCoverage.delegationHintsandfederatedCoverage.discoveredAgents.agents.delegationHints[].targetis typed to exactly three values today:"analytics","mail","dispatch"(FederatedDelegationTargetinserver/lib/search.ts) — there is no delegation hint for other templates yet, even if one is installed in the workspace. Each hint also carriesmatchedSignals(which words in the question triggered it) and a human-readablereason. - If the user asked for live/app-owned data and a hint matches the request,
call the specialist app agent with
call-agent. Keep the prompt narrow and include the user question plus any Brain context needed for names, dates, or citations. - Synthesize the final answer with clear source boundaries:
- Brain knowledge/captures are cited company memory.
- Specialist agent results are app-owned live data or app-native search.
- Coverage metadata only explains where you routed next.
- If no specialist agent is available, say Brain found a delegation hint but you could not query that app in this workspace.
Routing Examples
- Product decision, policy, process, or "why did we decide..." -> Brain only.
Search Brain, open
get-knowledge/get-captureas needed, cite evidence. - Dashboard metric, KPI, funnel, cohort, revenue, or chart -> Brain +
Analytics. Use Brain for context, then
call-agentAnalytics for live dashboard/data-source facts. - Email, customer thread, sender/recipient, Gmail, inbox, or mailbox state ->
Brain + Mail/Gmail. Use Brain for durable context, then
call-agentMail/Gmail for mailbox-native search. - Integration grants, reusable connections, secrets, approvals, recurring jobs,
workspace resources, or cross-app routing -> Brain + Dispatch. Use Brain for
documented decisions, then
call-agentDispatch for current control-plane state.
Don't
- Do not claim Brain searched sibling app databases directly.
- Do not treat
federatedCoverage.delegationHintsas answer evidence. - Do not invent live metrics, mailbox state, grants, or secrets from Brain memory.
- Do not put A2A calls inside Brain actions; cross-app delegation happens in the agent loop.
Related Skills
braindelegate-to-agenta2a-protocolsecurity
Signals
- GitHub stars
- 7k
- Forks
- 613
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
ask-across-everything- Source
- github.com/builderio/agent-native