`/knowledge/tools/`¶

Per-tool reference pages for every SaaS application, API service, and software product the eco|monetize™ operating system uses.

What goes here¶

One markdown file per tool. Each file is the canonical reference for that tool: what it is, how we use it, how it's set up, which agent owns it, where credentials live, what related tools it talks to, and any gotchas or lessons learned.

Tools are distinct from platforms: - Tools (this folder) — SaaS applications and services you interact with through a UI, API, or MCP server. Examples: Monday.com, Apollo.io, Make.com, Slack, Figma. - Platforms (/knowledge/platforms/) — infrastructure layers things run ON. Examples: AWS, Supabase, Cloudflare, 1Password, Tailscale.

The line is fuzzy (Supabase is both a tool and a platform depending on use), but the test is: "do I use this AS a product, or does my product run ON it?" If the former, tool. If the latter, platform.

Frontmatter convention¶

Every tool page starts with this YAML block so Dataview queries can index the catalog:

---
title: "{Tool Name}"
type: tool
category: {crm | prospecting | automation | communication | productivity | design | ai-llm | dev-tools | knowledge | content-marketing | monitoring | other}
vendor: "{Company}"
owner_agent: {agent_id or tbd}
integration_type: {MCP | API | manual | embedded | N/A}
credentials_location: "{1password path | env var | TBD | N/A}"
status: {active | evaluating | deprecated | archived}
pricing_tier: "{free | paid | TBD}"
docs_url: "{external URL}"
last_updated: YYYY-MM-DD
seeded_by: {agent_id}
tags: []
---

Page structure¶

Every tool page follows this structure for consistency and Dataview cross-linking:

# {Tool Name}

## Purpose
_Why we use this tool. One paragraph._

## How we use it
_Specific workflows and integrations in our system._

## Setup & credentials
_Configuration steps, where credentials live, rotation cadence._

## Owner
_Primary responsible agent and escalation path._

## Related
_Wikilinks to related tools, platforms, SOPs, playbooks, best practices._

## Notes
_Gotchas, historical context, lessons learned, version quirks._

Dashboard¶

A live catalog view at /dashboards/tools-catalog.md renders this folder via Dataview — grouped by category, filterable by status and owner, with gallery and table views.

Adding a new tool¶

Copy the template at _template.md (once seeded)
Fill in frontmatter + Purpose paragraph at minimum
Assign an owner agent (or leave as tbd for chief.staff to route)
File in this folder with kebab-case slug: apollo-io.md, monday-com.md, etc.
The Dataview catalog auto-indexes on next refresh — no manual update needed

Inventory¶

The master list of tools in this catalog lives at INVENTORY.md. It's chief.staff's source-of-truth for what exists and what's been stub-seeded vs. fully documented.

/knowledge/tools/¶