engagements

Create and update Notion engagement rows with Stripe payment details.

40|5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ShawhinT/non-coding-skills --skill engagements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engagements
Source: https://github.com/ShawhinT/non-coding-skills/tree/main/engagements
Command: npx skills add https://github.com/ShawhinT/non-coding-skills --skill engagements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you consistently create, update, and close client paid engagements in Shaw’s Notion-based Engagements database, so project history, delivery tracking, and wrap-up records stay accurate and aligned with Stripe and CRM.

Core Features & Use Cases

  • Create Engagement Rows: Add a new Engagement (one row per won, invoiced project) with correct properties, body template, and relational linking to the client.
  • Maintain Lifecycle Status: Transition Sold → Active → Delivered, with controlled handling for Refunds and On Hold, including the correct End Date and wrap prompts.
  • Link Sessions and Calls: Append ABA Trainings and ABA Calls mention-pages into the right chronological sections, including reschedule updates.
  • Fill Stripe Payment Details: Look up Stripe invoices, determine Paid Status, set Price, and write the correct Stripe link line into the engagement body (including proxy/void/replacement edge cases).
  • Guard the Engagements vs CRM Boundary: Keep long-term relationship nurture and wrap-up 4Rs in the correct place (Clients (Nurture) after Delivered) to avoid data drift.

Quick Start

Ask the AI to create an Engagement for a client who just paid, then link the discovery call and prepare the engagement body so Stripe and session tracking can be filled in as delivery starts.

Frequently Asked Questions about engagements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track client invoices and project lifecycle status in Notion?

You can track client invoices and project lifecycle status in Notion by maintaining an engagement ledger that links Stripe payment details, delivery progress, and CRM signals to individual client rows. This ensures project history and wrap-up records remain accurate and aligned.

Can I sync Stripe payment details into a Notion client database?

Yes, you can sync Stripe payment details into a Notion client database by fetching invoice data to determine Paid Status, setting the Price, and writing the correct Stripe link line into the engagement body. It also handles proxy payer, void, and replacement edge cases.

What's the best way to manage a client engagement ledger end-to-end?

The best way to manage a client engagement ledger end-to-end is by creating a one-row-per-invoice tracking system for workshops. This enforces temporal engagement ID rules, aligns offer, price, and scope, and manages Delivered handoff boundaries with your CRM.

How do I handle client lifecycle transitions from Sold to Delivered?

You handle client lifecycle transitions from Sold to Delivered by enforcing controlled status changes within your tracking system. This includes setting the correct End Date and triggering wrap-up prompts, while keeping long-term relationship nurture in a separate Clients space to prevent data drift.

Does the engagement tracking approach work for linking calls and sessions chronologically?

Yes, the engagement tracking approach works for linking calls and sessions chronologically by appending mention-pages into the correct chronological sections of the engagement body. This includes handling reschedule updates for training sessions and client calls.

What are the limitations of using Notion for client engagement tracking?

A limitation of using Notion for client engagement tracking is the boundary between active delivery and long-term nurture. After a project is marked Delivered, relationship nurture and wrap-up activities must be moved to a separate CRM space to avoid data drift.