Real professional work depends on knowledge, procedures, rules, context, exceptions, and judgment. Today, that expertise is scattered across docs, prompts, playbooks, tickets, and internal memory.
Pagenti packages it.
Author knowledge, skills, playbooks, and execution instructions natively as Markdown. Keep content readable for humans and easily versionable in Git.
Use pagenti.json to describe files, assign skill codes, declare context dimensions, and define package exports.
Agents and applications use the Pagenti registry to retrieve and resolve the exact right knowledge payload at runtime based on context.
Pagenti v4 separates the model into three core axes:
What kind of expert knowledge is this? (e.g., procedural, risk, diagnostic).
Who, where, when, and in what situation does it apply? Modeled as smart properties.
Which product or domain does this belong to in the registry?
{
"code": "external-access-review",
"skillCode": "riskKnowledge",
"role": ["ciso", "securityAnalyst"],
"useCase": ["vendorAccessReview"],
"tool": ["entraId"],
"risk": ["externalAccess"]
}
Pagenti does not just store content. It knows exactly where the content applies.
Not tags—resolved context backed by governed target catalogs.
Smart properties connect item fields to target catalogs by stable code. When content is written, the underlying Catalox data layer resolves target rows, updates usage statistics, inherits scope, and indexes values for precision querying.
See how raw text is mapped into an agent-ready artifact.
{
"name": "@acme/vendor-risk",
"version": "1.0.0",
"knowledge": [
{
"code": "external-access-review",
"path": "./content/external-access-review.md",
"skillCode": "riskKnowledge",
"role": ["ciso"],
"useCase": ["vendorAccessReview"],
"tool": ["entraId"]
}
],
"execution": [
{
"code": "review-external-access",
"path": "./execution/review-external-access.md",
"skillCode": "proceduralKnowledge",
"role": ["securityAnalyst"],
"useCase": ["vendorAccessReview"]
}
]
}
# External Access Review ## Purpose Help a security analyst evaluate whether external access is justified. ## Critical Questions - Who has access? - Why do they need it? - When should it end?
# Execution: Review External Access ## Instructions 1. Check the recipient domain against the allowed vendors list. 2. Require a documented internal data owner for the share. 3. Escalate unknown external access to the CISO immediately. 4. Auto-revoke access after 30 days unless exception is filed.
{
"items": [
{
"type": "execution",
"code": "review-external-access",
"skillCode": "proceduralKnowledge",
"content": "# Execution: Review External Access\n\n## Instructions\n1. Check the recipient domain..."
},
{
"type": "knowledge",
"code": "external-access-review",
"skillCode": "riskKnowledge",
"content": "# External Access Review\n\n## Purpose\nHelp a security analyst evaluate..."
}
]
}
Knowledge tells the agent what matters. Execution tells it what to do.
Package CISO knowledge, access review flows, external sharing guidance, vendor risk procedures, and escalation rules.
Package regulatory knowledge, evidence requirements, policies, audit checks, and approval guidance.
Package objection handling, discovery playbooks, qualification flows, pricing logic, and vertical-specific messaging.
Package feature specs, decision rules, customer segments, roadmap heuristics, and support knowledge.
Create a private registry of reusable knowledge and execution packages for teams and agents across your organization.
Initialize a new package repository.
pagenti init @acme/security-risk
Add Markdown files and declare skillCode + context dimensions in the manifest.
Push the versioned package to the registry.
pagenti publish
Agents retrieve the package content at runtime.
const items = await pagenti.findKnowledge({ role: "ciso", useCase: "vendorAccessReview", skillCode: "riskKnowledge" });
Pagenti uses Catalox as its registry and data layer. Catalox stores the catalogs, descriptors, target vocabularies, smart properties, item records, references, validation rules, and searchable metadata.
Pagenti packages can be private, team-scoped, or public. Use them as internal agent capabilities, reusable industry packs, or open-source professional playbooks.
v2.1.0 • Updated 2 days ago
Core security principles, standard access review playbooks, and compliance baselines for general agent usage.
v1.0.4 • Updated 1 week ago
Internal Acme Corp procedures for evaluating third-party vendors, data sharing agreements, and external access requests.
v3.0.0 • Updated 3 weeks ago
Standardized execution instructions for tool-calling agents, reflection loops, and autonomous task planning.
v1.2.1 • Updated 1 month ago
Industry standard policies and agent instructions for monitoring and mitigating risks associated with external file sharing.
Learn how pagenti.json maps Markdown files into knowledge and execution records.
Understand skillCode and how the 12 context dimensions power resolution.
Retrieve the right knowledge for the agent, user, role, and use case via the SDK.
See how Pagenti stores packages, vocabularies, and item records natively.
Build reusable knowledge and execution packages for the agents you are shipping. Pagenti packages professional knowledge for the agents that need to use it.