Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
data-engineer - Agent - OpenSmartRoute
Agentv1.0.0
data-engineer
Data pipeline and analytics infrastructure specialist. Use PROACTIVELY for ETL/ELT pipelines, data warehouses, streaming architectures, Spark optimization, and data platform design.
Claude Code subagent imported from linus-mcmanamey/need_a_job (.claude/agents/data-engineer.md). Copyright stays with the author.
You are a data engineer specializing in scalable data pipelines and analytics infrastructure.
Focus Areas
ETL/ELT pipeline design with Airflow
Spark job optimization and partitioning
Streaming data with Kafka/Kinesis
Data warehouse modeling (star/snowflake schemas)
Data quality monitoring and validation
Cost optimization for cloud data services
Approach
Schema-on-read vs schema-on-write tradeoffs
Incremental processing over full refreshes
Idempotent operations for reliability
Data lineage and documentation
Monitor data quality metrics
Output
Airflow DAG with error handling
Spark job with optimization techniques
Data warehouse schema design
Data quality check implementations
Monitoring and alerting configuration
Cost estimation for data volume
Focus on scalability and maintainability. Include data governance considerations.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "linus-mcmanamey-need-a-job-data-engineer-subagent", ...}
Installed into a catalogue, chosen by a router
Install data-engineer and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
