rudder-profiles-understand

rudder-profiles-understand is a skill for Claude Code from rudderlabs/rudder-agent-skills. It costs 53 tokens per session (1,218 once invoked), scanned A, original, MIT.

A project-explanation tool for RudderStack Profiles, which builds unified customer or business records from data in different systems.

In plain words
What is it for?
Use it to understand an existing Profiles project, review its structure, summarize the latest run, or perform a basic project health check.
Why use it?
It turns configuration files and run results into a plain summary of the project’s data sources, identity matching, models, and outputs.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the rudder-profiles plugin — 5 skills shipped together

Good fit Use it to understand an existing Profiles project, review its structure, summarize the latest run, or perform a basic project health check.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add rudderlabs/rudder-agent-skills --skill rudder-profiles-understand
Clone the repo
git clone --depth 1 https://github.com/rudderlabs/rudder-agent-skills

Made for: Claude Code.

Or install rudder-profiles, the plugin that ships this one along with the rest of its 5 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for rudder-profiles-understand

README.md
[![agentmods](https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand/github.svg)](https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand)
Your own site
<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for rudder-profiles-understand

Your own site · 80×15
<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-profiles-understand.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,218 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01218
Opus 5 $0.00026 $0.00609
Sonnet 5 $0.00011 $0.00244
Haiku 4.5 $0.00005 $0.00122

Measured 12d ago against content hash 905fbf646f14, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

rudder-profiles-understand scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/rudder-profiles/skills/rudder-profiles-understand/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RudderStack Profiles Project Understanding

Read an existing Profiles project and summarize what it builds, how it resolves identities, and what the latest run produced.

Workflow

  1. Read project files:
    • pb_project.yaml — entities, id_types, connection, schema_version, and any feature_views (using_ids re-keys output for activation)
    • models/inputs.yaml — input tables, event streams, ID mappings
    • models/profiles.yaml — entity_vars, id_stitcher config, any entity_cohort models (filtered audiences) and feature_table_model selections; var_groups scoped with entity_cohort: compute over a cohort
    • models/sql_models.yaml (if present) — sql_template intermediate models
    • models/profiles-ml.yaml / models/attribution.yaml (if present) — propensity / attribution models
    • models/optimizations.yaml / models/macros.yaml (if present) — performance flags and reusable macros
  2. Run pb show models to get the model dependency structure.
  3. Check outputs (if the project has been run; these are profiles-mcp tools the agent calls, not pb CLI commands):
    • Call the profiles-mcp tool initialize_warehouse_connection(<connection_name>) once before any run_query() — a hard precondition documented in the MCP tool; skipping it produces "warehouse not initialized".
    • Call get_profiles_output_details() for output metadata (output schema, entity/id-graph materials, latest seq_no).
    • Run targeted SQL for health metrics (see references).
    • Identify the latest seq_no and output tables. Materials are named Material_<model>_<hash>_<seq_no>; pb also maintains stable views (e.g., <entity>_var_table) repointed at the latest material each run — prefer the view.
  4. Present a summary covering:
    • What entity the project resolves and which id_types it uses.
    • Which input tables feed data, how IDs map, and which are event streams vs dimensions.
    • Which features (entity_vars) are computed, with descriptions.
    • Whether the project is discrete or incremental: any entity_var with a merge: clause (or an id_stitcher / sql_template with run_type: incremental) makes the project incremental. Call this out — users who don't know their project is incremental are surprised by checkpoint behavior.
    • Model dependency structure from pb show models.
    • Latest run details: seq_no, output schema, output tables.
    • Identity resolution health: stitching ratio, over-stitching candidates.
    • Read-only graph lenses to offer: pb audit id_stitcher (interactive viewer), pb show idstitcher-report (pre/post-stitch counts, convergence, largest cluster), and pb show entity-lookup -v <id_value> (one entity's stitched IDs and features by any known ID).

Read the full file on GitHub · 80 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 80 lines · 53 tokens per session scan A 905fbf646f14

Subscribe to this mod's changes

rudder-profiles-understand is a skill published in the GitHub repository rudderlabs/rudder-agent-skills (18 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 1,218 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

pgvector-semantic-search

Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…

timescale/pg-aiguide · 190 tokens

postgres-hybrid-text-search

Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…

timescale/pg-aiguide · 162 tokens

chief-data-officer

Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when…

cbrock84/headcount · 88 tokens

ai-workflow-architect

Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a…

cbrock84/headcount · 89 tokens

ai-ml-governance

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…

cbrock84/headcount · 83 tokens

data-engineering

Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone…

cbrock84/headcount · 67 tokens