Index of every page on this site: llms.txt
All skills
Run it yourself

Configure a least-privilege Clari identity and validate Revenue API or Copilot credentials without exposing secrets. Use when starting an integration or rotating access. Trigger with: "set up Clari auth", "configure a Clari token", "test Copilot credentials".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/clari-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesofficial-docs.md

≈476 tokens on demand. Your agent reads this file only when SKILL.md points to it.

First-party Clari evidence

Consulted on 2026-09-13 for clari-install-auth.

Source snapshots

  • Clari Revenue API reference: OpenAPI 3.0.0, published contract version 5.0.0, HTML SHA-256 3fa7e772eebc3b2461fa12561a82520d4069668c2c35220c6f54fd0dbda1b5e1
  • Clari Copilot API reference: OpenAPI 3.0.1, published contract version 1.0.0, spec.yaml SHA-256 e971686786068874001b8491189e233e634403e46bd3576a896cf02fb21774e6
  • Clari public GitHub organization: reviewed for a provider-maintained public Revenue or Copilot SDK; none was treated as authoritative for these workflows

Contracts used

  • Revenue API tokens are created in Account Settings and sent in the apikey header.
  • v2 ingestion requires both apikey and partnerkey.
  • Copilot requires X-Api-Key and X-Api-Password from workspace integration settings.

Scope

This skill turns the relevant public provider contracts into one bounded operator outcome. It does not claim Clari certification, private tenant access, commercial terms, webhook functionality absent from the published contract, or successful customer-data execution without a retained runtime receipt.

Verification boundary

  • Re-check hosts, versions, headers, endpoint shapes, permissions, limits, status values, and mutation semantics before execution.
  • Preserve exact forecast, job, event, call, workspace, and entity identifiers while redacting credentials and customer payloads.
  • Never include apikey, partnerkey, X-Api-Key, X-Api-Password, revenue values, participant data, transcripts, recordings, or signed URLs in evidence.
  • Treat export submission, job cancellation, ingestion, Copilot CRM writes, credential lifecycle changes, and downstream publication as explicit operator-approved mutations.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides secure procedures for setting up and validating Clari Revenue API and Copilot authentication. It emphasizes best practices such as using integration-specific identities, redacting credentials from all logs and receipts, and utilizing secret managers, with no malicious patterns detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
version
2.0.0
argument-hint
[surface-revenue-or-copilot-and-environment]
model
inherit
All 4 allowed tools
ReadGrepWriteEdit
Other metadata
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "clari",
  "authentication",
  "tokens",
  "integration-user"
]
compatibility
Requires an entitled Clari tenant, an approved integration owner, and access to the relevant Revenue API or conversation-intelligence workspace settings.

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/clari-install-auth