Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Company Knowledge Brain

    1

    Turn scattered company documents into a traceable, governed knowledge system with clear sources, ownership, conflicts, and gaps.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Company Knowledge Brain

    Company Knowledge Brain

    Example session with this skill installed

    We have three fictional company knowledge sources: an employee handbook, an old onboarding checklist, and meeting notes describing a newer process. Create a first-pass knowledge map and source register. Distinguish official policy from observed practice and proposed changes, identify conflicts and gaps, recommend owners and review dates, and outline a retrieval packet for the question ‘How do new support hires handle an escalation?’ Do not assume the documents say anything beyond the supplied summaries.

    • Read your context and instructions
    • Compiled the company knowledge brain

    First-pass knowledge map — illustrative, based only on the supplied source summaries

    Objective

    Organize onboarding and escalation knowledge for support hires. The actual files were not provided here, so no policy details or process steps can be asserted.

    Sources reviewed

    SourceTypeAuthorityCurrencyCoverage
    Employee handbookFormal documentPotentially official; owner and approval status to verifyUnknownCompany-wide policies; escalation coverage unknown
    Old onboarding checklistOperational aidStatus and owner unknownKnown to be described as oldSupport onboarding; steps to verify
    Meeting notesInformal recordEvidence of discussion, not automatically policyDate and participants neededDescribes a newer process; adoption unknown

    Knowledge map

    • Support escalation → may connect to the handbook, checklist, and newer process notes.
    • New support hire → needs a clear, current, approved procedure and escalation owner.
    • Process owner, approver, effective date, and source-of-truth link → missing for all three sources.

    Process status distinction

    • Documented official process: not established from these summaries. Confirm approved source and owner.

    Observed or supplied practice: meeting notes describe a newer process; details and actual adoption need verification.

    Proposed process: reconcile the documents, obtain owner approval, then publish one canonical guide with version and review date.

    Conflict and gap register

    ItemIssueNext action
    Checklist vs. meeting notesPotentially outdated steps; exact differences unknownCompare source passages and dates; ask process owner which steps are current
    HandbookMay define governance or escalation dutiesLocate relevant section and confirm approval status
    OwnershipNo owner or approver identifiedAssign Support Operations owner and policy approver
    Access and sensitivityNot suppliedPreserve source permissions and classify before indexing

    Retrieval packet: “How do new support hires handle an escalation?”

    • Intent: find current, approved escalation steps for a new support hire.
    • Entities: Support Hire; Escalation; Support Operations; handbook; onboarding checklist; process notes.
    • Canonical knowledge: unresolved pending source comparison and owner approval.
    • Supporting evidence: cite exact passages and page/section from each source.
    • Conflicts: flag differences between old checklist and newer notes.
    • Temporal context: dates and effective versions required.
    • Permissions/sensitivity: inherit source-level access; do not expose restricted notes.
    • Answer constraint: if no approved current source exists, say so and route to the process owner.

    Next steps

    Provide the documents, confirm access rules, identify the process owner, reconcile the sources, and approve a canonical version before presenting it as policy.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Company Knowledge Brain helps organizations structure fragmented institutional knowledge across documents, policies, SOPs, project records, meeting notes, decisions, product and customer information, research, operational procedures, and lessons learned. It goes beyond summaries to identify where knowledge came from, who owns it, how current and reliable it is, how it connects to other facts, which decisions depend on it, and what remains unknown.

    The workflow inventories sources, extracts and resolves entities, builds a taxonomy and relationships, records source authority and sensitivity, captures decision and process memory, maps expertise when authorized, designs retrieval packets, identifies gaps and continuity risks, and defines governance and lifecycle practices. Deliverables can include a knowledge map, source register, decision log, process library, retrieval design, conflict register, and prioritized maintenance plan.

    The agent does not invent company facts, decisions, employees, policies, customers, owners, access, integrations, approvals, or source authority. It distinguishes official documented process from supplied operational practice and proposed process. Use only materials and systems the user is authorized to provide or connect; preserve sensitivity labels and access limits.

    Knowledge maps depend on the documents and metadata supplied. Conflicting, outdated, incomplete, or inaccessible sources can leave gaps. The agent cannot verify source authority or organizational practice without evidence and owner confirmation. It does not change permissions, publish, synchronize, or create a live knowledge base unless appropriate tools are separately connected and authorized.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files

    Read only user-provided or explicitly authorized documents. Preserve source labels, locators, sensitivity, and access rules. Do not publish, synchronize, or change source files unless separately authorized and supported by connected tools.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    It maps documents and organizational knowledge to sources, entities, owners, authority, dates, sensitivity, decisions, processes, gaps, and retrieval needs.

    No. It documents conflicts and evidence, distinguishes policy from observed or proposed practice, and identifies the owners who must resolve and approve the source of truth.

    No. It can design and prepare knowledge structures. Any connected-system access, edits, or publication require authorized tools and explicit review.

    New in Business & Operations