GuruSup Brain

Offer to save newly stated durable company facts. Write only after a user request, confirmation, or client approval. Never save chat, drafts, temporary preferences, speculation, inference, or sensitive personal data unless explicitly designated as company memory. After success, hide ids, status, and backend details.

add_company_knowledge

Primary company-memory read; returns authorized evidence and claims. Compact is the normal response. Use full only for debugging. Answer only from returned evidence and keep diagnostics internal unless requested. If falling back, reuse the returned audit.activity_id in search and retrieve.

ask_company_memory

Check whether the GuruSup Brain API is reachable.

health

Load the full content for one available GuruSup Brain skill.

skills_get

Signed-in account profile.

get_profile

Initialize the agent with the Company Brain MCP usage contract.

init

Publish only a user-authored skill, as pending_review, when explicitly asked.

skills_publish

Report a Brain failure you can point to: a tool error, something the user says exists that retrieval did not return, or an answer contradicting its evidence. Report once confirmed, not on first suspicion. No permission needed; tell the user in one line. Pass audit.activity_id when you have one. Not for wrong company facts or denied_context.

report_issue

Ask a configured Knowledge Contact for missing company information. Use whenever Company Memory leaves any requested fact unsupported, including a partial answer, explicit gaps, or request_human_info in recommended_next_tools. When the question or gap uses a Company Memory result, pass its audit.activity_id to request_human_info in both the preview and confirmed dispatch. Reuse the same activity used by the originating ask/search/retrieve calls. Omit activity_id only for a new user-authored question that does not use retrieved context. Never retry a denied activity by dropping or replacing its activity_id. Company Memory is not a contact directory. A person mentioned in Company Memory, retrieved evidence, or the conversation is not necessarily a configured Knowledge Contact. Never infer that such a person can be contacted. Before naming or proposing any person as a contact, or asking the user for confirmation, always call request_human_info with dispatch=false. Use only the selected_contact returned by that preview as a contactable person. If the user explicitly directs outreach to a particular person, validate that person in the preview. Populate requested_contact_name or requested_contact_id only when the user explicitly directs outreach to that person; otherwise leave both unset so the backend selects exclusively from configured organization contacts. Never populate either from Company Memory, retrieved evidence, or inferred ownership. If validation fails, explain that the person is not configured as a Knowledge Contact. After explicit user confirmation, call request_human_info with dispatch=true and requested_contact_id set to the selected_contact_id returned by the preview. Never substitute a person inferred from Company Memory or the conversation. If the user explicitly asks to be contacted themselves so they can provide the missing information, first call request_human_info with dispatch=false. Inspect the preview's selected_contact.is_requester value. Only when is_requester=true, immediately call request_human_info a second time with dispatch=true, requester_directed=true, and requested_contact_id bound to that preview's selected_contact_id, without asking for another confirmation: the original self-contact instruction is the confirmation. Identity match alone is not consent. If the original user request did not explicitly ask to contact themselves, keep the preview pending even when is_requester=true and wait for explicit confirmation; that later normal confirmation must use requester_directed=false. If an explicit self-contact preview instead selects someone else, explain that the authenticated requester is not available as the configured Knowledge Contact and do not dispatch the request to someone else. If coordinated Human Information is unavailable, report the temporary failure; the backend will not use legacy dispatch for requester-directed outreach. A dispatched request may use any configured channel and is asynchronous. After it returns human_info_request, tell the user the process may take several minutes plus the call and offer to continue with something else meanwhile.

request_human_info

Fetch 1-3 exact evidence ids, preferring chunk ids from focused search. Pass the originating ask audit.activity_id. Use diagnostics only for an explicit investigation that needs the broader 20-id backend limit.

retrieve_company_memory