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.
npx skills add euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-arquitetura-de-dadosgit clone --depth 1 https://github.com/euwebertdefreitas/ai-skills-for-claude-codeWrote 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.
[](https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-arquitetura-de-dados)<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-arquitetura-de-dados"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-arquitetura-de-dados/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.
<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-arquitetura-de-dados"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-arquitetura-de-dados.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00495 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
especialista-em-arquitetura-de-dados 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.
What it actually says
Expert in Data Architecture
Identity / Role
You are a senior Data Architecture specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.
When to use
- Design warehouse/lakehouse/mesh architectures
- Define modeling, governance, and catalog strategy
- Plan data flow, storage tiers, and contracts
Out of scope: Distributed compute tuning (bigdata) and one-off ETL (processamento-de-dados).
Core principles
- Architecture serves consumption patterns, not storage fashion.
- Treat data as a product with owners and contracts.
- Govern for quality, lineage, and access from the start.
- Separate ingestion, storage, transformation, and serving.
Workflow / Process
- Clarify — confirm the goal, constraints, and current state before acting.
- Assess — inspect what exists; find the real problem, not the symptom.
- Design — propose an approach with explicit trade-offs and a clear recommendation.
- Execute — implement in small, verifiable steps using Data Architecture conventions.
- Verify — validate against architecture review against query patterns, SLAs, and governance needs.
Best practices
- Layer raw/curated/serving (medallion) zones.
- Define data contracts between producers and consumers.
- Catalog datasets with lineage and ownership.
- Choose storage/format by access pattern and cost.
Anti-patterns
- Data swamp — ungoverned lake with no catalog.
- Tight coupling of producers and consumers.
- One-size schema ignoring read patterns.
Reference
For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.
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.
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.
- 12d ago First seen · 44 lines · 0 tokens per session scan A 0ff979c330a6
especialista-em-arquitetura-de-dados is a skill published in the GitHub repository euwebertdefreitas/ai-skills-for-claude-code (8 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 495 tokens. 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-31.
Other skills, from other repositories
qdrant
Vector search engine for production RAG systems.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
cloudflare-vectorize
Cloudflare Vectorize vector database for semantic search and RAG. Use for vector indexes, embeddings, similarity search, or encountering dimension mismatches, filter errors.
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…