Individual skill
mindtickle-webhooks-events
Select and govern a supported Mindtickle change-ingestion pattern: documented event delivery, managed connector, polling, or export. Use when downstream systems need timely updates. Trigger with "ingest Mindtickle changes".
skills/.curated/mindtickle-webhooks-events/SKILL.md
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,917
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- mindtickle Declared skill tag
- events Declared skill tag
- polling Declared skill tag
- webhooks Declared skill tag
- engineering Derived category
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
# Mindtickle Change Ingestion and Event Governance
## Overview
Choose the least risky supported delivery mode and make duplicates, ordering, authenticity, replay, privacy, reconciliation, and fallback explicit.
## Prerequisites
- A use case, source of truth, freshness objective, event or record volume, and downstream owner
- Current tenant documentation for available events, APIs, reports, exports, or managed connectors
- A data classification, retention policy, capacity contract, and recovery objective
## Tool Discipline
Use `Read`, `Glob`, and `Grep` to inspect consumers and schemas, `WebFetch` for current authorized contracts, and `Write` or `Edit` for ingestion code, fixtures, mappings, and redacted receipts.