clari-reference-architecture
Reference architecture for Clari revenue intelligence integrations. Use when designing a forecast data platform, planning Clari integration architecture, or establishing team patterns for revenue analytics. Trigger with phrases like "clari architecture", "clari data platform", "clari integration design", "clari best practices". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clari-reference-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Clari Reference Architecture ## Overview Production architecture for Clari revenue intelligence integrations: export pipeline design, data warehouse schema, analytics layer, and alerting. ## Architecture Diagram ``` ┌──────────────┐ ┌─────────────────┐ ┌──────────────────┐ │ Clari App │ │ Clari Export │ │ Data Warehouse │ │ (SaaS) │────▶│ API (v4) │────▶│ (Snowflake/BQ) │ └──────────────┘ └─────
What does the clari-reference-architecture skill do?
Reference architecture for Clari revenue intelligence integrations. Use when designing a forecast data platform, planning Clari integration architecture, or establishing team patterns for revenue analytics. Trigger with phrases like "clari architecture", "clari data platform", "clari integration design", "clari best practices". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clari-reference-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
