New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Granola Reference Architecture

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Enterprise reference architecture for meeting management with Granola.

MITAuto-check passedSales & Support

Install Granola Reference Architecture

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-reference-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace granola-reference-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/granola-reference-architecture .claude/skills/granola-reference-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
granola-reference-architecture
GitHub stars
2.8k
Token cost
~2.3k tokens
SKILL.md length
354 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Enterprise reference architecture for meeting management with Granola.

  • Works in 6 steps: Core Pipeline Architecture → Folder-Based Routing Topology → Multi-Workspace Topology → …
  • Designing org-wide meeting workflows
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Granola Reference Architecture is an agent skill from jeremylongshore/tons-of-skills-marketplace. Enterprise reference architecture for meeting management with Granola. Use when designing org-wide meeting workflows, planning integration topology, or architecting meeting-to-action pipelines across departments. Trigger: "granola architecture", "granola enterprise design", "granola system design", "meeting system architecture".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Sales & Support. It works with Slack and Notion. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Designing org-wide meeting workflows
  • Planning integration topology
  • Architecting meeting-to-action pipelines across departments

Example prompts

  • “granola architecture”
  • “granola enterprise design”
  • “granola system design”
  • “/granola-reference-architecture”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Core Pipeline Architecture
  2. Folder-Based Routing Topology
  3. Multi-Workspace Topology
  4. Security Architecture
  5. Integration Data Flow Patterns
  6. Disaster Recovery & Data Export

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.granola.ai
    • granola.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Granola Reference Architecture loads about 2.3k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 354 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 354 words, ~2,315 tokens.

Download SKILL.mdSave it as .claude/skills/granola-reference-architecture/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
granola-reference-architecture
description
Enterprise reference architecture for meeting management with Granola. Use when designing org-wide meeting workflows, planning integration topology, or architecting meeting-to-action pipelines across departments. Trigger: "granola architecture", "granola enterprise design", "granola system design", "meeting system architecture".
allowed-tools
Read, Write, Edit
compatibility
Designed for Claude Code
version
1.13.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, granola, architecture, enterprise

Granola Reference Architecture

Overview

Enterprise reference architecture for deploying Granola as the meeting intelligence platform across an organization. Covers the core capture pipeline, Zapier middleware routing, multi-workspace topology, security layers, and integration patterns for Slack, Notion, CRM, and task management.

Prerequisites

  • Granola Enterprise plan ($35+/user/month)
  • Zapier Professional or higher (for multi-step Zaps and Paths)
  • Destination systems provisioned (Slack, Notion, CRM, Linear/Jira)
  • IT architecture review completed

Instructions

Step 1 — Core Pipeline Architecture
┌─────────────────────────────────────────────────────────┐
│                    MEETING PLATFORMS                      │
│  Zoom  |  Google Meet  |  Microsoft Teams  |  Slack Huddle│
└──────────────────────┬──────────────────────────────────┘
                       │ System audio capture (no bot)
                       ▼
┌─────────────────────────────────────────────────────────┐
│                    GRANOLA PLATFORM                       │
│                                                          │
│  ┌──────────┐  ┌──────────────┐  ┌─────────────────┐   │
│  │ Audio    │→ │ Transcription │→ │ AI Enhancement  │   │
│  │ Capture  │  │ (GPT-4o/     │  │ (Notes + Trans- │   │
│  │ (local)  │  │  Claude)     │  │  cript merge)   │   │
│  └──────────┘  └──────────────┘  └────────┬────────┘   │
│                                            │             │
│  ┌────────────────┐  ┌──────────────────┐  │            │
│  │ People &       │  │ Folders          │  │            │
│  │ Companies      │  │ (routing rules)  │←─┘            │
│  │ (built-in CRM) │  └────────┬─────────┘              │
│  └────────────────┘           │                         │
└───────────────────────────────┼─────────────────────────┘
                                │
            ┌───────────────────┼───────────────────┐
            │           ZAPIER MIDDLEWARE            │
            │                                       │
            │  ┌─────────┐  ┌─────────┐  ┌──────┐ │
            │  │ Filter  │→ │ Route   │→ │ Act  │ │
            │  │ (type/  │  │ (paths  │  │      │ │
            │  │ attendee)│  │ /rules) │  │      │ │
            │  └─────────┘  └─────────┘  └──────┘ │
            └──────┬──────────┬──────────┬─────────┘
                   │          │          │
        ┌──────────┴──┐ ┌────┴────┐ ┌───┴────────┐
        │ COMMUNICATE │ │ ARCHIVE │ │ ACT        │
        │ Slack       │ │ Notion  │ │ Linear/Jira│
        │ Email       │ │ Drive   │ │ Asana      │
        │ Teams       │ │ GCS/S3  │ │ HubSpot    │
        └─────────────┘ └─────────┘ └────────────┘
Step 2 — Folder-Based Routing Topology

Design folder structure to drive automated routing:

FolderTrigger TypeDestinationsPermissions
Sales / DiscoveryAutoSlack #sales + HubSpot Deal + Follow-up EmailSales team
Sales / DemoAutoSlack #sales + HubSpot ContactSales team
Engineering / SprintAutoSlack #eng + Linear tasks + Notion wikiEngineering
Engineering / ArchitectureAutoSlack #eng-arch + Notion ADR databaseSenior engineers
Product / Customer FeedbackAutoSlack #product + Notion feedback DBProduct team
Leadership / All-HandsAutoSlack #general + Google Drive archiveAll
Leadership / BoardManual onlyPrivate Notion, no SlackExecutives only
HR / InterviewsManual shareGreenhouse scorecardHiring managers
HR / 1-on-1sNonePrivate, no automationIndividual
Step 3 — Multi-Workspace Topology
Organization (Enterprise)
├── Engineering Workspace
│   ├── Folders: Sprint, Architecture, Standup, Retro
│   ├── Integrations: Linear, Notion, Slack #engineering
│   └── Retention: 2 years notes, 90 days transcripts
│
├── Sales Workspace
│   ├── Folders: Discovery, Demo, Pipeline Review
│   ├── Integrations: HubSpot, Slack #sales, Gmail
│   └── Retention: 1 year notes, 90 days transcripts
│
├── Product Workspace
│   ├── Folders: Customer Feedback, Design Review, PRD
│   ├── Integrations: Notion, Linear, Slack #product
│   └── Retention: 2 years notes, 90 days transcripts
│
├── HR Workspace (Confidential)
│   ├── Folders: Interviews, 1-on-1s, Performance
│   ├── Integrations: Greenhouse (via Zapier)
│   ├── Retention: 30 days notes, 7 days transcripts
│   └── Restrictions: No external sharing, MFA required
│
└── Executive Workspace (Confidential)
    ├── Folders: Board, Strategy, M&A
    ├── Integrations: Private Notion only
    ├── Retention: Custom (legal hold capable)
    └── Restrictions: IP allowlist, 4-hour session timeout
Step 4 — Security Architecture
Authentication Layer:
  SSO (Okta/Azure AD) → SCIM provisioning → JIT workspace assignment

Data Protection:
  In Transit: TLS 1.3 (all API calls)
  At Rest: AES-256 (server-side storage)
  Local: FileVault/BitLocker (cache-v3.json encryption)

Access Control:
  Org Owner → Workspace Admin → Team Lead → Member → Viewer → Guest
  ↓
  SSO groups mapped to Granola roles per workspace

Data Classification:
  Confidential: HR, Legal, Board (restricted sharing, short retention)
  Internal: Engineering, Product (team sharing, standard retention)
  External-Facing: Sales, Customer Success (CRM sync allowed)

Compliance:
  SOC 2 Type 2: Certified (July 2025)
  GDPR: DPA available, data export/deletion supported
  AI Training: Opt-out enforced org-wide (Enterprise default)
Step 5 — Integration Data Flow Patterns

Pattern A: Standard Meeting (Parallel)

Note enhanced → Folder trigger fires
  ├─→ Slack notification (immediate)
  ├─→ Notion archive (immediate)
  └─→ Linear tasks (per action item)

Pattern B: Sales Meeting (Sequential)

Note enhanced → "Sales / Discovery" folder
  │
  ├─→ HubSpot: Find Contact by attendee email
  │     ├─→ Found: Log meeting note on Contact
  │     └─→ Not found: Create Contact, then log note
  │
  ├─→ ChatGPT: Generate BANT analysis + follow-up email
  │     └─→ Gmail: Create draft to external attendees
  │
  └─→ Slack: Post summary to #sales with deal context

Pattern C: Executive Meeting (Restricted)

Note enhanced → "Board" folder (no auto-trigger)
  │
  └─→ Manual share to private Notion database only
       └─→ Link expires in 7 days
Step 6 — Disaster Recovery & Data Export
Backup Strategy:
  Primary: Granola cloud storage (server-side, encrypted)
  Secondary: Local cache (cache-v3.json on each user's device)
  Tertiary: Nightly export to cloud storage (via Zapier + GCS/S3)

Recovery Procedures:
  1. User device loss: Re-authenticate, data syncs from server
  2. Integration outage: Zapier retries automatically; monitor Zap history
  3. Granola service outage: Manual notes during outage; capture resumes on recovery
  4. Data export request: Enterprise API bulk export or per-user Settings > Data > Export
Show full SKILL.md (146 more words)Show less

Output

  • Complete meeting ecosystem architecture documented
  • Folder-based routing configured per department
  • Multi-workspace topology deployed with appropriate isolation
  • Security and compliance controls mapped to org requirements
  • Disaster recovery plan established

Error Handling

ErrorCauseFix
Notes routing to wrong destinationFilter logic error in Zapier PathsReview path conditions, test with sample data
Cross-workspace access deniedPermission boundaries working correctlyElevate user role or add to target workspace
Integration sync delay > 5 minZapier queue or destination rate limitAdd delay step, check destination API limits
Missing CRM updates for new contactsNative integration doesn't auto-createAdd Zapier "Find or Create" step
Audit log gapsLogging not enabled on workspaceEnable in Workspace Settings > Security

Examples

source=synthetic-calendar; event=meeting-completed; consent=test-only; destination=staging-actions; retention=none; allowlist=pass; rollback=arch-r17 is a reviewable integration receipt.

Resources

Next Steps

Proceed to granola-multi-env-setup for workspace creation and configuration.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/granola-reference-architecture of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Granola Reference Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Granola Reference Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Granola Reference Architecture this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.3kAutomated safety check: PassMIT
Integrationsbutterbase-ai/butterbase-skills534—~832Automated safety check: PassMIT
AirweaveCraftOS-dev/CraftBot392—~1.1kAutomated safety check: PassMIT
Omh Appsrlaope/oh-my-hermes3.2k—~1.9kAutomated safety check: PassMIT
Meeting Preptechwolf-ai/ai-first-toolkit132—~1kAutomated safety check: PassMIT
Connect Apps with ComposioComposioHQ/awesome-claude-skills77k3 repos~557Automated safety check: PassNone

Similar skills

  • Integrations

    butterbase-ai/butterbase-skills

    Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…

    534 GitHub stars~832 tokensUpdated 5 days ago
    Sales & SupportAuto-check passed

  • Airweave

    CraftOS-dev/CraftBot

    Context retrieval layer for AI agents across users' applications.

    392 GitHub stars~1.1k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Omh Apps

    rlaope/oh-my-hermes

    [omh] Email, Slack, or Jira action to perform: external app actions - email, Slack, Discord, Notion, Linear, Jira, CRM, and similar providers, scoped with auth, payload, confirmation, and…

    3.2k GitHub stars~1.9k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Meeting Prep

    techwolf-ai/ai-first-toolkit

    Comprehensive pre-meeting briefing that gathers all relevant context from Slack, email, Google Docs, Notion, and calendar.

    132 GitHub stars~1k tokensUpdated 11 days ago
    Productivity & AutomationAuto-check passed

  • Connect Apps with Composio

    ComposioHQ/awesome-claude-skills

    Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.

    77k GitHub starsUsed in 3 repos~557 tokens
    Productivity & AutomationAuto-check passed

  • Claap Weekly Recap

    Othmane-Khadri/YALC-the-GTM-operating-system

    Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.

    318 GitHub stars~5.4k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Granola Reference Architecture

What does Granola Reference Architecture do?

Enterprise reference architecture for meeting management with Granola. Granola Reference Architecture is an agent skill from jeremylongshore/tons-of-skills-marketplace. Enterprise reference architecture for meeting management with Granola.

When should I use Granola Reference Architecture?

Granola Reference Architecture fits situations like: designing org-wide meeting workflows; planning integration topology; architecting meeting-to-action pipelines across departments.

How do I install Granola Reference Architecture in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-reference-architecture -a claude-code`. Or copy the skill folder (skills/.curated/granola-reference-architecture in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/granola-reference-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Granola Reference Architecture in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-reference-architecture -a codex`. Or copy the skill folder (skills/.curated/granola-reference-architecture in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/granola-reference-architecture in your project. Codex loads it when a task matches its description.

Can I use Granola Reference Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-reference-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/granola-reference-architecture, .gemini/skills/granola-reference-architecture, .github/skills/granola-reference-architecture and .opencode/skills/granola-reference-architecture in your project.

What does Granola Reference Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Granola Reference Architecture is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code.

Does Granola Reference Architecture access the network?

SKILL.md names 2 domains. As links in the text: docs.granola.ai and granola.ai. This is read from the text; nothing was executed.

Is Granola Reference Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Granola Reference Architecture use?

Granola Reference Architecture is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Granola Reference Architecture use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Granola Reference Architecture?

Skills that share tags, products or a category with Granola Reference Architecture: Integrations (butterbase-ai/butterbase-skills, 534 stars), Airweave (CraftOS-dev/CraftBot, 392 stars), Omh Apps (rlaope/oh-my-hermes, 3.2k stars) and Meeting Prep (techwolf-ai/ai-first-toolkit, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Granola Reference Architecture?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.