Stripe Best Practices
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…
Install Triggers Guide
$ npx skills add OtoDock/oto-dock --skill triggers-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OtoDock/oto-dock triggers-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/mcps/custom/triggers-mcp/docs/triggers-guide .claude/skills/triggers-guide && rm -rf skills-srcUse ~/.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/
Install the "triggers-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guide into .claude/skills/triggers-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triggers-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OtoDock/oto-dock --skill triggers-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OtoDock/oto-dock triggers-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .agents/skills && cp -r skills-src/mcps/custom/triggers-mcp/docs/triggers-guide .agents/skills/triggers-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triggers-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guide into .agents/skills/triggers-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triggers-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OtoDock/oto-dock --skill triggers-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OtoDock/oto-dock triggers-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/mcps/custom/triggers-mcp/docs/triggers-guide .cursor/skills/triggers-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triggers-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guide into .cursor/skills/triggers-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triggers-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OtoDock/oto-dock.git --path mcps/custom/triggers-mcp/docs/triggers-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OtoDock/oto-dock --skill triggers-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OtoDock/oto-dock triggers-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/mcps/custom/triggers-mcp/docs/triggers-guide .gemini/skills/triggers-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triggers-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guide into .gemini/skills/triggers-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triggers-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OtoDock/oto-dock triggers-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OtoDock/oto-dock --skill triggers-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .github/skills && cp -r skills-src/mcps/custom/triggers-mcp/docs/triggers-guide .github/skills/triggers-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triggers-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guide into .github/skills/triggers-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triggers-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OtoDock/oto-dock --skill triggers-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OtoDock/oto-dock triggers-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/mcps/custom/triggers-mcp/docs/triggers-guide .opencode/skills/triggers-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triggers-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/triggers-mcp/docs/triggers-guide into .opencode/skills/triggers-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triggers-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triggers-guide- GitHub stars
- 190
- Token cost
- ~3k tokens
- SKILL.md length
- 1,355 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…
- Works in 2 steps: Create a task with task_type='trigger'… → Create the trigger pointing at it
- Eventfilter rules
- SKILL.md covers The trigger ↔ task pattern, The trigger ↔ app handler…, The trigger ↔ notification… and Vendor-subscribed triggers…, plus 5 more sections
- Calls curl; reaches github.com
What it does
Triggers Guide is an agent skill from OtoDock/oto-dock. Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders, external-system setup and API keys, debounce, and worked examples. Load before creating or editing a webhook trigger.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Webhooks, MCP servers and OAuth and OpenID Connect. The repository describes itself as: The agentic company OS. The brains of your company, built on Claude Code and Codex, working on your Anthropic and OpenAI subscriptions.
When your agent uses it
- Eventfilter rules
- Payload placeholders
- External-system setup and API keys
- Worked examples
Example prompts
- “/triggers-guide”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Create a task with task_type='trigger' (no schedule, no run_at — it only runs when something fires it)
- Create the trigger pointing at it
What it can do on your machine
Read from SKILL.md and the folder at commit 5308f5a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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.
Context cost
Triggers Guide loads about 3k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 1,355 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,355 words (~2,975 tokens).
“The trigger-instructions card in your instructions carries the rules (which tool for which request, the two scopes, exact event_type values, what to tell the user). This guide is the reference behind them.”
- name
- triggers-guide
Files
Just SKILL.md in mcps/custom/triggers-mcp/docs/triggers-guide of OtoDock/oto-dock.
Open the folder on GitHubat commit 5308f5a
Compare with similar skills
Triggers Guide 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triggers Guide this skillOtoDock/oto-dock | 190 | — | ~3k | Automated safety check: Pass | Custom licence | |
| Stripe Best Practiceskanchengw/cnllm | 175 | 3 repos | ~925 | Automated safety check: Pass | Apache-2.0 | |
| X Twitter ScraperXquik-dev/x-twitter-scraper | 209 | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Zalo AgentPhucMPham/zalo-agent-cli | 163 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Xquik MCPXquik-dev/x-twitter-scraper | 209 | 1 repos | ~997 | Automated safety check: Pass | MIT | |
| Discord Php Bot Securitydiscord-php/DiscordPHP | 1.1k | — | ~1.2k | Automated safety check: Notes | MIT |
Similar skills
X Twitter Scraper
Xquik-dev/x-twitter-scraper
Use Xquik to fetch X (Twitter) data or act through a connected account: search, profiles, followers, replies, threads, timelines, media downloads, bulk exports, trends, monitors, signed webhooks…
Zalo Agent
PhucMPham/zalo-agent-cli
Automate Zalo messaging, Official Account (OA), and MCP server integration via zalo-agent-cli.
Xquik MCP
Xquik-dev/x-twitter-scraper
Connect, verify, and troubleshoot Xquik's remote MCP server.
Discord Php Bot Security
discord-php/DiscordPHP
Audit checklist for DiscordPHP bots and API libraries — stop the bot token leaking to third-party APIs or logs, keep secrets out of customids and exception messages, use constant-time comparison and…
GitHub OAuth Nango Integration
AgentWorkforce/relay
A skill your agent uses when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling
More from OtoDock/oto-dock
All 19 skills in this repoAgent Creation
OtoDock/oto-dock
How to author an agent template folder and install it as a new agent - folder layout, manifest fields, persona rules, shipped apps and checks, and the scaffold-validate-create flow.
Checks
OtoDock/oto-dock
How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives…
Image Search Usage
OtoDock/oto-dock
Search the web for images with filters and download them. An agent skill from OtoDock/oto-dock.
Subtitle Burning
OtoDock/oto-dock
Transcribe audio and burn styled subtitles into videos. An agent skill from OtoDock/oto-dock.
MCP Authoring
OtoDock/oto-dock
Author an MCP package for OtoDock: the manifest.json fields and their rules, the package layout, what the installer refuses or drops, credentials and instances, skills bundled with an MCP, and the…
Otodock Platform
OtoDock/oto-dock
How the OtoDock platform itself works and where every setting lives — installing and first-run setup, agents, AI engines, sessions, apps and sharing, checks, departments and delegation, shared…
Related
Categories
Questions about Triggers Guide
What does Triggers Guide do?
Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…. Triggers Guide is an agent skill from OtoDock/oto-dock. Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders, external-system setup and API keys, debounce, and worked examples.
When should I use Triggers Guide?
Triggers Guide fits situations like: eventfilter rules; payload placeholders; external-system setup and API keys; worked examples.
How do I install Triggers Guide in Claude Code?
Run `npx skills add OtoDock/oto-dock --skill triggers-guide -a claude-code`. Or copy the skill folder (mcps/custom/triggers-mcp/docs/triggers-guide in OtoDock/oto-dock) into .claude/skills/triggers-guide in your project. Claude Code loads it when a task matches its description.
How do I install Triggers Guide in Codex?
Run `npx skills add OtoDock/oto-dock --skill triggers-guide -a codex`. Or copy the skill folder (mcps/custom/triggers-mcp/docs/triggers-guide in OtoDock/oto-dock) into .agents/skills/triggers-guide in your project. Codex loads it when a task matches its description.
Can I use Triggers Guide 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 OtoDock/oto-dock --skill triggers-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triggers-guide, .gemini/skills/triggers-guide, .github/skills/triggers-guide and .opencode/skills/triggers-guide in your project.
What does Triggers Guide need to run?
Going by SKILL.md and its folder, Triggers Guide needs the command-line tools its instructions call (curl).
Does Triggers Guide access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Triggers Guide 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 Triggers Guide use?
Triggers Guide has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Triggers Guide use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Triggers Guide?
Skills that share tags, products or a category with Triggers Guide: Stripe Best Practices (kanchengw/cnllm, 175 stars), X Twitter Scraper (Xquik-dev/x-twitter-scraper, 209 stars), Zalo Agent (PhucMPham/zalo-agent-cli, 163 stars) and Xquik MCP (Xquik-dev/x-twitter-scraper, 209 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triggers Guide?
OtoDock (a GitHub organization) maintains it in OtoDock/oto-dock, which has 190 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: OtoDock/oto-dock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.