ChurchTools Extension Developer Skill

Guide developers in building, testing, and deploying ChurchTools extensions with the official boilerplate.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ct-mg/Time-Tracker --skill churchtools-extension-developer-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ChurchTools Extension Developer Skill
Source: https://github.com/ct-mg/Time-Tracker/tree/main
Command: npx skills add https://github.com/ct-mg/Time-Tracker --skill churchtools-extension-developer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides expert guidance for developers to create, develop, and deploy ChurchTools extensions using the official boilerplate, helping teams adopt standard practices and avoid common pitfalls.

Core Features & Use Cases

  • Comprehensive knowledge of the extension boilerplate, including repository structure, entry points, and test environments.
  • Guidance on essential concepts like extension points, the bidirectional event system, and the KV store usage for safe persistence.
  • Practical use cases and best practices for building production-ready extensions, with references to docs.

Quick Start

Clone the boilerplate, install dependencies, configure environment variables, register entry points, and run the dev server to start building.

Frequently Asked Questions about ChurchTools Extension Developer Skill

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

FAQPage Schema
How do I build a ChurchTools extension using the official boilerplate?

To build a ChurchTools extension, clone the official boilerplate, install dependencies, configure environment variables, register entry points, and run the dev server to start local development and testing workflows.

What are entry points in ChurchTools extension development?

Entry points in ChurchTools extension development are registration mechanisms defined in the manifest that connect your custom code to specific extension points within the platform architecture.

Does the ChurchTools extension boilerplate support TypeScript?

Yes, the ChurchTools extension boilerplate fully supports TypeScript, providing a typed development environment for creating robust extensions, configuring manifests, and managing entry-point registration.

How do I use the KV store for safe persistence in a ChurchTools extension?

The KV store provides safe persistence for ChurchTools extensions by offering a structured key-value storage mechanism, ensuring data consistency across bidirectional event system interactions and extension points.

What is the recommended workflow for testing ChurchTools extensions?

The recommended workflow for testing ChurchTools extensions involves utilizing the boilerplate's integrated test environments, running the dev server locally, and validating entry-point registration before production deployment.

When do I need to configure environment variables for ChurchTools extension development?

You need to configure environment variables for ChurchTools extension development during the initial setup of the official boilerplate, enabling the dev server to connect and run local testing workflows properly.