Bring the domain knowledge your investigation needs
A context package carries curated knowledge for an operational domain: reference material, skills, prompts, playbooks, and methodology. It helps an agent interpret the evidence available in your environment without treating generic model knowledge as a substitute for observation.
Current package domains include Model Authoring, Cybersecurity Risk, Threat Hunting, Network Traffic Analysis, Security Configuration, Infrastructure Reliability, Cisco Networking, and Juniper Networking. Availability and compatibility depend on the package release and your entitlements.
Load the relevant skill, not an entire library
Assigned skill summaries help an agent find guidance relevant to the current question. The skill protocol requires loading the selected knowledge body before relying on it, with a reference to the package, version, and resource.
Skills are knowledge-only resources. They have no executable filesystem path and cannot supply new connector permissions. Loaded instructions remain subordinate to product policy, the agent’s scope, and current evidence.
Assign knowledge to the right roles and tasks
Package assignment and retrieval policy can narrow which agent roles, run types, and product surfaces may use a resource. An analysis specialist and a model author can receive different guidance for the same environment.
Agent Teams preserve those boundaries: a consultation uses the receiving agent’s applicable packages and authorization. Task text cannot grant a package, widen source access, or override the declared egress policy.
Check provenance, trust, and entitlement
Signed archives carry package identity, version, resource hashes, and compatibility information. Installation validates archives using the configured trust settings; activation checks package readiness and any required entitlement. Assignment and retrieval also depend on current package state and policy.
Packages are released independently from CyberStitch and its connectors. That allows domain guidance to evolve without requiring the same release schedule as the application. The same distribution model can support a planned disconnected update process.
Control what leaves the environment
Resources can be restricted to local inference or explicitly permitted destinations. Generation and embeddings are separate egress decisions; allowing one does not automatically allow the other.
Choose the provider, model, and package configuration together. A local-only resource does not become eligible for an external provider because that provider has a local-looking endpoint name.
Measure the value of the knowledge
A signed package provides provenance, not a guarantee that every recommendation is correct. Evaluate it against representative tasks and your operational standards.
Package evaluation resources are excluded from normal agent retrieval. To compare results, hold the model, settings, question, tool grants, and data snapshot constant, then test with the package assignment enabled and disabled.