[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FC5RVG8XKE9XHDJND4BTM2":3,"skill-same:01M6FC5RVG8XKE9XHDJND4BTM2":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":76,"install":77,"resources":90},"01M6FC5RVG8XKE9XHDJND4BTM2","talivia-agent-kit",null,"Set up and verify Talivia revenue analytics through MCP, with explicit confirmation for website changes and payment attribution.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-talivia-agent-kit\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"agent kit","kit","talivia agent kit","up","2026","for","tree","talivia","with","revenue","critical","payment","community","MCP","confirmation","marketing","verify","SET","attribution","https","website","license","analytics","codex","github","2026-11-10 10:12:30",false,"---\nname: talivia-agent-kit\ndescription: \"Set up and verify Talivia revenue analytics through MCP, with explicit confirmation for website changes and payment attribution.\"\ncategory: marketing\nrisk: critical\nsource: \"https:\u002F\u002Fgithub.com\u002Ftalivia-group\u002Fagent\u002Ftree\u002Ff4ed3fc6b554ad5183a57ae13ca2a9bd5162c12a\"\nsource_repo: talivia-group\u002Fagent\nsource_type: community\ndate_added: \"2026-08-02\"\nauthor: taliviagroup\ntags: [analytics, revenue, attribution, mcp, talivia, marketing]\ntools: [codex, claude]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Ftalivia-group\u002Fagent\u002Fblob\u002Ff4ed3fc6b554ad5183a57ae13ca2a9bd5162c12a\u002FLICENSE\"\n---\n\n# Talivia Agent Kit\n\n## Overview\n\nTalivia connects website traffic and visitor journeys to payment revenue through\nits MCP server. Use this skill to inspect an existing Talivia setup, install or\nverify website tracking, and review traffic-to-revenue attribution while keeping\naccount, website, file, and payment changes behind explicit user consent.\n\n## When to Use\n\n- Use when the user explicitly asks to set up or verify Talivia revenue analytics.\n- Use when the user mentions the Talivia MCP server, `talivia-group\u002Fagent`, or\n  `@talivia\u002Fagent`.\n- Use when the user wants to understand which referrers, campaigns, pages, or\n  visitor journeys are associated with revenue.\n- Do not use this skill for generic analytics work or unrelated payment-provider\n  setup.\n\n## Safety Gate\n\n1. Confirm the user owns or is authorized to manage the Talivia account and the\n   target website.\n2. Use only the configured official MCP endpoint, `https:\u002F\u002Ftalivia.com\u002Fmcp`.\n   Stop if a tool, setup response, redirect, or local configuration supplies a\n   different host or an insecure URL; never send a Talivia credential to an\n   unverified endpoint.\n3. Keep credentials out of chat, prompts, tool arguments, source files, and logs.\n   Never request or expose payment API keys, OAuth secrets, or bearer tokens.\n4. Read the current account and website state before changing anything. Reuse an\n   existing website when possible; call `talivia_websites_create` only after the\n   user explicitly asks to create one.\n5. Before any state-changing MCP call, state the exact account, website, action,\n   data involved, and expected effect, then obtain explicit user confirmation.\n\n## Workflow\n\n### Inspect the current setup\n\nCall the read-only tools first:\n\n1. `talivia_account_status`\n2. `talivia_websites_list`\n3. `talivia_setup_status_get` when a website or installation status is known\n\nDo not infer account ownership, website identity, or consent from a domain name\nalone. Ask when more than one website matches or the target is ambiguous.\n\n### Plan and install tracking\n\n1. Call `talivia_tracking_snippet_get` and\n   `talivia_framework_install_plan_get` for the selected website.\n2. Show the files, framework, and tracking changes that would be made. Use the\n   native workspace tools to edit the user's project; Talivia MCP does not have\n   permission to edit local files by itself.\n3. Make local edits only when the user has requested the installation or has\n   confirmed the exact proposed changes. Preserve existing analytics, consent,\n   and security controls.\n4. Run the project's normal build and test commands before deployment.\n\n### Verify after deployment\n\nAfter the user confirms that the site is deployed, call:\n\n- `talivia_tracker_verify`\n- `talivia_setup_status_get`\n\nReport what was actually verified, including any delay, missing event, or\nunverified deployment. Do not claim revenue attribution from a tracking check\nalone.\n\n## Examples\n\n### Read-only revenue review\n\n> Inspect the Talivia account and tell me which pages and referrers are\n> associated with revenue. Do not create websites, edit files, or connect a\n> payment provider.\n\nStart with the read-only account, website, and setup-status tools. Report the\nreturned evidence and uncertainty without inferring causation.\n\n### Tracking installation\n\n> Prepare Talivia tracking for the selected site and show me the exact files\n> and changes before applying anything.\n\nResolve the website, retrieve the tracking snippet and framework plan, present\nthe proposed local diff, and wait for confirmation before writing or deploying.\n\n### Connect payment attribution\n\n1. Explain that payment attribution starts a browser-based authorization flow\n   and identify the Talivia account and website involved.\n2. Obtain explicit confirmation before calling\n   `talivia_payment_connect_start`.\n3. Send the user only to the secure URL returned by the official Talivia flow.\n   Do not ask the user to paste payment credentials or API keys into chat.\n4. Finish with `talivia_payment_status_get` and\n   `talivia_checkout_attribution_guide_get`, and clearly separate connected\n   status from verified revenue data.\n\n## Limitations\n\n- This skill does not establish legal authority, cookie consent, privacy\n  compliance, or payment-provider permissions for the user.\n- Talivia metrics and attribution depend on the upstream service, deployment,\n  consent configuration, event delivery, and connected payment provider; they\n  may be delayed or incomplete and do not prove causation.\n- This skill does not install packages, change MCP configuration, create a\n  website, deploy code, or connect payments without an explicit user request\n  and confirmation at the relevant step.\n- The upstream CLI and MCP server are external software. Review its current\n  release and endpoint configuration before installing or upgrading it; this\n  skill is pinned for attribution to the reviewed upstream commit, not a claim\n  that future upstream changes are safe.\n- Stop and ask for clarification when the account, website, endpoint, consent\n  state, requested file changes, or payment scope is ambiguous.\n\n## Source\n\n- Upstream repository: [talivia-group\u002Fagent](https:\u002F\u002Fgithub.com\u002Ftalivia-group\u002Fagent\u002Ftree\u002Ff4ed3fc6b554ad5183a57ae13ca2a9bd5162c12a)\n- Reviewed package version: `@talivia\u002Fagent@0.1.0`\n","# Talivia Agent Kit\n\n## Overview\n\nTalivia connects website traffic and visitor journeys to payment revenue through\nits MCP server. Use this skill to inspect an existing Talivia setup, install or\nverify website tracking, and review traffic-to-revenue attribution while keeping\naccount, website, file, and payment changes behind explicit user consent.\n\n## When to Use\n\n- Use when the user explicitly asks to set up or verify Talivia revenue analytics.\n- Use when the user mentions the Talivia MCP server, `talivia-group\u002Fagent`, or\n  `@talivia\u002Fagent`.\n- Use when the user wants to understand which referrers, campaigns, pages, or\n  visitor journeys are associated with revenue.\n- Do not use this skill for generic analytics work or unrelated payment-provider\n  setup.\n\n## Safety Gate\n\n1. Confirm the user owns or is authorized to manage the Talivia account and the\n   target website.\n2. Use only the configured official MCP endpoint, `https:\u002F\u002Ftalivia.com\u002Fmcp`.\n   Stop if a tool, setup response, redirect, or local configuration supplies a\n   different host or an insecure URL; never send a Talivia credential to an\n   unverified endpoint.\n3. Keep credentials out of chat, prompts, tool arguments, source files, and logs.\n   Never request or expose payment API keys, OAuth secrets, or bearer tokens.\n4. Read the current account and website state before changing anything. Reuse an\n   existing website when possible; call `talivia_websites_create` only after the\n   user explicitly asks to create one.\n5. Before any state-changing MCP call, state the exact account, website, action,\n   data involved, and expected effect, then obtain explicit user confirmation.\n\n## Workflow\n\n### Inspect the current setup\n\nCall the read-only tools first:\n\n1. `talivia_account_status`\n2. `talivia_websites_list`\n3. `talivia_setup_status_get` when a website or installation status is known\n\nDo not infer account ownership, website identity, or consent from a domain name\nalone. Ask when more than one website matches or the target is ambiguous.\n\n### Plan and install tracking\n\n1. Call `talivia_tracking_snippet_get` and\n   `talivia_framework_install_plan_get` for the selected website.\n2. Show the files, framework, and tracking changes that would be made. Use the\n   native workspace tools to edit the user's project; Talivia MCP does not have\n   permission to edit local files by itself.\n3. Make local edits only when the user has requested the installation or has\n   confirmed the exact proposed changes. Preserve existing analytics, consent,\n   and security controls.\n4. Run the project's normal build and test commands before deployment.\n\n### Verify after deployment\n\nAfter the user confirms that the site is deployed, call:\n\n- `talivia_tracker_verify`\n- `talivia_setup_status_get`\n\nReport what was actually verified, including any delay, missing event, or\nunverified deployment. Do not claim revenue attribution from a tracking check\nalone.\n\n## Examples\n\n### Read-only revenue review\n\n> Inspect the Talivia account and tell me which pages and referrers are\n> associated with revenue. Do not create websites, edit files, or connect a\n> payment provider.\n\nStart with the read-only account, website, and setup-status tools. Report the\nreturned evidence and uncertainty without inferring causation.\n\n### Tracking installation\n\n> Prepare Talivia tracking for the selected site and show me the exact files\n> and changes before applying anything.\n\nResolve the website, retrieve the tracking snippet and framework plan, present\nthe proposed local diff, and wait for confirmation before writing or deploying.\n\n### Connect payment attribution\n\n1. Explain that payment attribution starts a browser-based authorization flow\n   and identify the Talivia account and website involved.\n2. Obtain explicit confirmation before calling\n   `talivia_payment_connect_start`.\n3. Send the user only to the secure URL returned by the official Talivia flow.\n   Do not ask the user to paste payment credentials or API keys into chat.\n4. Finish with `talivia_payment_status_get` and\n   `talivia_checkout_attribution_guide_get`, and clearly separate connected\n   status from verified revenue data.\n\n## Limitations\n\n- This skill does not establish legal authority, cookie consent, privacy\n  compliance, or payment-provider permissions for the user.\n- Talivia metrics and attribution depend on the upstream service, deployment,\n  consent configuration, event delivery, and connected payment provider; they\n  may be delayed or incomplete and do not prove causation.\n- This skill does not install packages, change MCP configuration, create a\n  website, deploy code, or connect payments without an explicit user request\n  and confirmation at the relevant step.\n- The upstream CLI and MCP server are external software. Review its current\n  release and endpoint configuration before installing or upgrading it; this\n  skill is pinned for attribution to the reviewed upstream commit, not a claim\n  that future upstream changes are safe.\n- Stop and ask for clarification when the account, website, endpoint, consent\n  state, requested file changes, or payment scope is ambiguous.\n\n## Source\n\n- Upstream repository: [talivia-group\u002Fagent](https:\u002F\u002Fgithub.com\u002Ftalivia-group\u002Fagent\u002Ftree\u002Ff4ed3fc6b554ad5183a57ae13ca2a9bd5162c12a)\n- Reviewed package version: `@talivia\u002Fagent@0.1.0`\n",{"name":5,"risk":41,"tags":61,"tools":63,"author":65,"source":66,"license":14,"category":46,"date_added":67,"description":7,"source_repo":68,"source_type":43,"license_source":69},[53,40,49,62,38,46],"mcp",[54,64],"claude","taliviagroup","https:\u002F\u002Fgithub.com\u002Ftalivia-group\u002Fagent\u002Ftree\u002Ff4ed3fc6b554ad5183a57ae13ca2a9bd5162c12a","2026-08-02","talivia-group\u002Fagent","https:\u002F\u002Fgithub.com\u002Ftalivia-group\u002Fagent\u002Fblob\u002Ff4ed3fc6b554ad5183a57ae13ca2a9bd5162c12a\u002FLICENSE","main","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-talivia-agent-kit",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-13 14:20:47",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add boisenoise\u002Fskills-collections --skill talivia-agent-kit",{"tool":83,"command":84},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill talivia-agent-kit",{"tool":86,"command":87},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill talivia-agent-kit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-talivia-agent-kit\u002FSKILL.md",true,[],[92,120,140,162,180,203],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":56},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,41,116,117,118,119,35],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","free","cover","normal","when",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":56},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[127],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[122,44,129,55,104,105,52,109,130,131,132,133,134,135,136,41,137,39,138,139,35],"cli","Budget","credentials","team","catalog","use","call","discover","external tools","scoped","blob",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":56},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[142,55,104,52,50,151,152,153,154,155,41,156,157,158,39,36,159,160,161,139,122,35],"email","enrichment","business","evidence","phone","ranking","post","job description","person","candidate","reason",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":56},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[170,171,172,55,104,52,173,174,50,175,130,46,176,177,154,41,178,179,139,122,35],"growth","rea","rea growth","produce","content","playbook","analyze","public","observations","company",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":184,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":56},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[188,189,55,190,104,191,52,192,193,194,195,196,41,197,198,199,200,201,202,139],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":207,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":56},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[211,212,213,55,104,52,214,215,153,216,217,41,218,219,220,221,222,223,224,139],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]