realtime-cinema-data-engineering-pipeline: Claude Code skill
Instructions for assembling a streaming pipeline that routes simulated ticket transactions through message queues and warehouse layers.
npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a claude-codeWhat realtime-cinema-data-engineering-pipeline does
This skill guides your coding assistant through setting up event streaming for cinema box office records. Synthetic ticket purchases generated via Faker land in an Apache Kafka topic, while a background consumer loads raw payloads directly into PostgreSQL.
Data organization follows a tiered setup. The bronze tier keeps raw JSON payloads, the silver tier breaks details into normalized third-normal-form relational tables, and the gold tier prepares materialized aggregates for Streamlit reports. Airflow schedules and runs the downstream transformations.
Running this setup requires Python 3.8+ alongside Docker Compose. Without waiting two or three minutes after starting the containers, Airflow will not finish its boot process and scheduled tasks will fail.
What it helps with
- ingest continuous event streams from Kafka into PostgreSQL
- structure database storage into bronze, silver, and gold tiers
- mock ticket purchasing events using Python and Faker
- orchestrate relational transformations with Apache Airflow
Example prompts for the agent
- Set up a streaming event pipeline using Kafka, PostgreSQL, and Airflow
- Show me how to split cinema event payloads into normalized silver tables
- Generate synthetic movie ticket sales with a Kafka producer script
How to install realtime-cinema-data-engineering-pipeline
1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a claude-code2Manually: put the files in place
~/.claude/skills/realtime-cinema-data-engineering-pipeline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/realtime-cinema-data-engineering-pipeline/
1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a codex2Manually: put the files in place
.agents/skills/realtime-cinema-data-engineering-pipeline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a cursor2Manually: put the files in place
.cursor/skills/realtime-cinema-data-engineering-pipeline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/data-skills realtime-cinema-data-engineering-pipeline2Manually: put the files in place
.github/skills/realtime-cinema-data-engineering-pipeline/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/data-skills --path skills/realtime-cinema-data-engineering-pipelineManually: put the files in place
.devin/skills/realtime-cinema-data-engineering-pipeline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about realtime-cinema-data-engineering-pipeline
How to install realtime-cinema-data-engineering-pipeline in Claude Code?
Run npx skills add reason-machines/data-skills --skill realtime-cinema-data-engineering-pipeline -a claude-code. This links the skill configurations directly to your agent.
What does realtime-cinema-data-engineering-pipeline do?
It supplies reference code, database schemas, and orchestration setups for processing live event streams through message brokers and analytical database layers.
What system dependencies are required?
You need Python 3.8 or newer, Docker, and Docker Compose installed locally. Airflow containers also require two to three minutes to initialize before accepting workloads.