Context WikiTeam standards and pages every agent follows
Agents follow your team's standards on every task
Write your team's standards and procedures once, and every agent follows them on every task. Runbooks and notes live as pages in Drive that agents open with the permissions of the person who asked.
Write your standards once
Set instructions for your org, each workspace and each agent once, and every agent task starts by reading them.
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
- Place the flagged companies first, Northwind, Fenwick, Alder
- Render q3-portfolio-review.pptx, 4.1 MB
- Wrote q3-portfolio-review.pptx, 4.1 MB
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesAdd the covenant headroom chart from the workbook to the Fenwick slide.
Added. Slide 5 now carries the interest-cover chart with the 2.0x test line; the appendix table is unchanged.
Q3 portfolio review deck
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
Added. Slide 5 now carries the interest-cover chart with the 2.0x test line; the appendix table is unchanged.
What was checked
Read q3-portfolio-updates.docx: 14 companies
Read q3-valuation-bridge.xlsx: 3 scenarios
Draft slides from the Q2 template: 18 slides
How access works
Atlas works in the channels it is a member of and reads the workspace Drive. Runs that need more ask first.
Skills
Quarterly portfolio review · Board pack extraction · LP letter draft
Keep runbooks where agents find them
Store runbooks, decisions and notes as pages in Drive folders, and agents open them by link, search or the CLI when a task needs them.
See who changed a procedure
Each procedure an agent follows is saved as a version with its author, so you can see who changed a step and restore an earlier one.
Version history
- Version 3Current
- Version 2Restore
- Version 1Restore
Build the quarterly review deck from the updates doc and the valuation bridge, flagged companies first.
- Scope
- Brindle Capital
- Tags
- portfolio
- Files
- SKILL.md deck-template.pptx Add files
- Connectors
- + Attach
- Scorecards
- Deck quality
Steps
- Read the quarter's updates doc and the valuation bridge workbook.
- Draft the slides from last quarter's template, one company per slide.
- Place every company more than 10% off plan first, on slides 3 to 5.
- Render the deck and post it to the review channel with the flagged companies named.
Written by
Atlas · from the Q3 review deck task
Store runbooks and notes as pages in Drive
Write pages in Drive folders, edit them in place and share them with one permission decision for people, groups and agents.
Make every agent follow your standards
Agents start every task from the instructions your team wrote, follow the procedures you assign and open your pages when the task needs them.
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
- Place the flagged companies first, Northwind, Fenwick, Alder
- Render q3-portfolio-review.pptx, 4.1 MB
- Wrote q3-portfolio-review.pptx, 4.1 MB
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesAdd the covenant headroom chart from the workbook to the Fenwick slide.
Added. Slide 5 now carries the interest-cover chart with the 2.0x test line; the appendix table is unchanged.
Q3 portfolio review deck
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
Added. Slide 5 now carries the interest-cover chart with the 2.0x test line; the appendix table is unchanged.
What was checked
Read q3-portfolio-updates.docx: 14 companies
Read q3-valuation-bridge.xlsx: 3 scenarios
Draft slides from the Q2 template: 18 slides
How access works
Atlas works in the channels it is a member of and reads the workspace Drive. Runs that need more ask first.
Skills
Quarterly portfolio review · Board pack extraction · LP letter draft
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
- Place the flagged companies first, Northwind, Fenwick, Alder
- Render q3-portfolio-review.pptx, 4.1 MB
- Wrote q3-portfolio-review.pptx, 4.1 MB
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesAdd the covenant headroom chart from the workbook to the Fenwick slide.
Added. Slide 5 now carries the interest-cover chart with the 2.0x test line; the appendix table is unchanged.
How access works
Atlas works in the channels it is a member of and reads the workspace Drive. Runs that need more ask first.
Skills
Quarterly portfolio review · Board pack extraction · LP letter draft
See how your procedures change
Every change to a procedure is saved as a new version with its author, and every file an agent writes is stored with the task that made it.
Version history
- Version 3Current
- Version 2Restore
- Version 1Restore
Build the quarterly review deck from the updates doc and the valuation bridge, flagged companies first.
- Scope
- Brindle Capital
- Tags
- portfolio
- Files
- SKILL.md deck-template.pptx Add files
- Connectors
- + Attach
- Scorecards
- Deck quality
Steps
- Read the quarter's updates doc and the valuation bridge workbook.
- Draft the slides from last quarter's template, one company per slide.
- Place every company more than 10% off plan first, on slides 3 to 5.
- Render the deck and post it to the review channel with the flagged companies named.
Written by
Atlas · from the Q3 review deck task
Version history
- Version 3Current
- Version 2Restore
- Version 1Restore
Build the quarterly review deck from the updates doc and the valuation bridge, flagged companies first.
- Scope
- Brindle Capital
- Tags
- portfolio
- Files
- SKILL.md deck-template.pptx Add files
- Connectors
- + Attach
- Scorecards
- Deck quality
Steps
- Read the quarter's updates doc and the valuation bridge workbook.
- Draft the slides from last quarter's template, one company per slide.
- Place every company more than 10% off plan first, on slides 3 to 5.
- Render the deck and post it to the review channel with the flagged companies named.
Written by
Atlas · from the Q3 review deck task
Agents see only what the person who asked can see
Your pages, instructions and procedures share one set of permissions, search shows only what you can open and every agent action is recorded.
How access works
- Atlas can only see channels it has been added to.
- Everything Atlas does is recorded under its name, with the task it was working on.
Approvals
Always allowed
Things you have told this agent it can always do, so it stops asking. Remove one and it goes back to asking.
How access works
- Atlas can only see channels it has been added to.
- Everything Atlas does is recorded under its name, with the task it was working on.
Approvals
Always allowed
Things you have told this agent it can always do, so it stops asking. Remove one and it goes back to asking.
Read and edit pages on any device
Read and edit pages on web, phone and desktop, and use the CLI to list, pull, push, search and share pages in the same folders.
Work across Context with shared permissions
Your pages, files, chat, procedures and scores share one permission system, so a page you share once has the same access in every Context product.
- DriveEvery wiki page is a Drive file, stored in your bucket and shared under the same grants as the rest of your files.
- SkillsThe procedures your agents follow are versioned skills, readable and editable by your team beside the pages that explain them.
- TeamsThe people, groups and agents on your org share one directory, so a page shared with a group reaches its agents too.
- RLGraded agent runs suggest better versions of your procedures for your team to accept.
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Deploy in your environment
Run Context Wiki in your own cloud or on your own hardware. Your pages stay in your S3 or MinIO bucket, inside your deployment.
- Your cloud or hardwarePages are stored in your S3 or MinIO bucket, in your cloud or on your own hardware.
- Self-hosted through KOTSInstall Context in your own environment with KOTS self-hosting.
- Air-gapped installationInstall without internet access, with the air-gapped installation tested in CI.
- Your identity providerSign people in with SAML or OIDC and provision them with SCIM.
Context runs in production at Qualcomm. Read the case study
- Amazon S3
- MinIO
- Your own hardware
- Air-gapped
Context Wiki is included in every Context workspace, including the Free plan.
- Free$0Includes Context Wiki
- Plus$20Per person per month
- EnterpriseCustomEnterprise deployments run in your own cloud.Talk to us about a plan
Questions
How does Context Wiki relate to Drive?
Context Wiki is built on Context Drive. Every page is a file in your Drive folders, stored in your bucket and shared under the same permissions as your other files.
What does an agent read before every task?
Every task reads the instructions set for your org, workspace and agent, from the broadest to the most specific, and the procedures assigned to that agent. Agents open other pages through links, search and the CLI when a task needs them.
Can an agent change a page?
An agent writes with the permissions of the person who asked, and the files it writes are stored in the task's folder. Changes to a procedure are saved as a new skill version that records who made it and can be restored.
Does search cover what is inside my pages?
Keyword and content search run on every deployment. Your org admin decides whether to enable semantic search by meaning for each folder, and results always respect permissions.
Where are my pages stored?
Your pages are stored in your S3 or MinIO bucket, in your cloud or on your own hardware, inside your Context deployment.
