Menu

Individual skill

talivia-agent-kit

Set up Talivia revenue-first website analytics with MCP, then verify live traffic and revenue attribution.

plugins/talivia-group/agent/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 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)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

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

# Talivia Agent Kit

Talivia connects website traffic and visitor journeys to payment revenue. Use it when the user wants to install revenue-first analytics, discover which traffic becomes revenue, connect checkout attribution, or verify a Talivia setup.

1. Call `talivia_account_status` and `talivia_websites_list`.
2. Reuse the correct website, or ask before calling `talivia_websites_create` if creation was not explicit.
3. Call `talivia_tracking_snippet_get` and `talivia_framework_install_plan_get`.
4. Edit the user’s project with your native workspace tools. Talivia MCP does not edit local files.
5. Build/test the project.
6. After deployment, call `talivia_tracker_verify` and `talivia_setup_status_get`.
7. For payments, call `talivia_payment_connect_start` and send the user to the returned secure URL.
8. Never request or expose payment API keys in chat, MCP tool arguments, code, or logs.
9. Use `talivia_payment_status_get` and `talivia_checkout_attribution_guide_get` to finish verification.