Skip to main content
This feature is in development and not yet available.

​
What It Does

Custom Knowledge lets admins create instruction files that Monk agents follow when operating within an organization. Each file contains rules, playbooks, and preferred defaults so Monk behaves consistently with team standards.

​
How It Works

Admins create instruction files at different scopes:
  • Organization: Applies to all members and clusters in the org.
  • Environment: Applies when deploying to that environment.
  • Cluster: Applies when connected to that cluster.
Instruction files are written in Markdown and can contain any guidance Monk should follow, such as:
  • “Do not spawn instances larger than t3.large”
  • “Always use AWS RDS for PostgreSQL, never self-hosted”
  • “Require approval before deploying to production”
  • “Use our internal container registry at registry.example.com”

​
Example Instruction File

# Team Deployment Rules

## Instance Sizing
- Use t3.medium for staging, t3.large for production.
- Never use instances larger than t3.xlarge without approval.

## Database
- Always use AWS RDS for PostgreSQL.
- Do not deploy self-hosted databases.

## Secrets
- Never store secrets in environment variables directly.
- Use team-scoped secrets for all credentials.

​
Key Benefits

  • Consistency: Monk follows the same rules for every team member.
  • Compliance: Enforce policies automatically without manual review.
  • Knowledge retention: Team standards persist as members change.

​
Availability

Available on the Team plan only.