Individual skill

fondo-reference-architecture

Reference architecture for startup financial operations using Fondo as the bookkeeping backbone with complementary tools for banking, payroll, and reporting. Trigger: "fondo architecture", "startup finance stack", "fondo integration architecture".

plugins/saas-packs/fondo-pack/skills/fondo-reference-architecture/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Fondo Reference Architecture

## Overview

Reference architecture for a startup's financial operations with Fondo at the center, connecting payroll, banking, payments, and internal reporting.

## Prerequisites

- A data-flow inventory, authorized business purpose, system owners, access/retention policy, and professional-review boundary.
- Separate scoped identities for data sources, processing, storage, reporting, and support, plus synthetic integration fixtures.

## Instructions

1. Enforce field allowlists, access checks, encryption, and retention requirements at every financial-data boundary.
2. Keep financial/tax conclusions under the designated finance professional’s review; integrations may prepare evidence but not replace that review.
Back to top