data-engineering
Skill4 starsChanged 38 days agoMITView on GitHub
Data Engineering Agent for the Krmaazha Binance MCP system. Specializes in real-time market data ingestion, schema validation, zero-lookahead windowing, rate limit budgeting, and high-integrity data pipelines.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- juninmd/skillstheir own version, first seen Nov 15, 2026
- d-padmanabhan/agent-engineering-handbooktheir own version, first seen Nov 11, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- Crush-Rewards/claude-skillstheir own version, first seen Oct 20, 2026
- newsc2/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use qa-testing, infrastructure-as-code and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
miketrombaSkillqa-testing
Autonomously QA and verify the application using browser automation. Use when verifying code changes, testing features, validating bug fixes, or confirming any work done on the application. Triggers on requests to "test this", "verify this works", "QA this change", "make sure it works", or after implementing features that need validation.
Also in 3 projects that use this
mmondoraSkillinfrastructure-as-code
Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.
Also in 3 projects that use this
onejaejaeSkillapi-documentation
API 문서화 스킬. Notion과 Postman에 API 명세를 추가합니다. Use when documenting APIs, updating Notion database, or adding Postman requests.
Also in 3 projects that use this
jx1100370217Skillsecurity-hardening
Harden OpenClaw security configuration. Use when: (1) Setting up security for new OpenClaw installation, (2) Configuring exec approvals and allowlists, (3) Securing gateway access, (4) Setting up tool policies, (5) User asks about OpenClaw security or hardening.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 5 projects that use this
AnthropicSkillsystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
Also in 4 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- magnus919/agent-skills★ 177same name
- irahardianto/awesome-agv★ 157same name
- travisjneuman/.claude★ 106same name
- d-padmanabhan/agent-engineering-handbook★ 20same name
- drewid74/ai_skills★ 8same name
- BejeweledMe/codex-pro-agent-skills★ 7same name
- Douglasst102/AgentSkills★ 4same name
- thejordanleopold/claude-code-skills-distilled★ 4same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- juninmd/skills★ 2same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-debt-detectorSkill
- airflow-dag-patternsSkill
- async-python-patternsSkill
- backtesting-frameworksSkill
- create-readmeSkill
- data-quality-frameworksSkill
- dataset-curationSkill
- dbt-transformation-patternsSkill
- design-doc-mermaidSkill
- embedding-strategiesSkill
- eval-harness-firstSkill
- excalidraw-diagramSkill
- execution-algorithmsSkill
- external-diagram-mermaid-generateSkill
- frontend-designSkill
- hybrid-search-implementationSkill
- improve-codebase-architectureSkill
- llm-evaluationSkill
- market-regime-detectionSkill
- mcp-builderSkill
- mcp-registry-syndicationSkill
- mcprush-gateway-deploymentSkill
- mermaid-diagramsSkill
- ml-pipeline-workflowSkill
- orchestratorSkill
- postgresql-table-designSkill
- prompt-engineering-patternsSkill
- python-testing-patternsSkill
- rag-implementationSkill
- regulatory-compliance-auditSkill
- risk-metrics-calculationSkill
- security-reviewSkill
- spark-optimizationSkill
- sql-optimization-patternsSkill
- vector-index-tuningSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Explicit Instrument Metadata: Ensure every inbound message or Kline payload explicitly records:
- Very specific: line 28
All prices, quantities, spreads, order notionals, and balances must be stored and manipulated using Python Decimal or strict string …
- Very specific: line 29
Never allow IEEE-754 binary floating-point representation (0.1 + 0.2 != 0.3) in order-book depth accumulation or order sizing.
- Distinctive: line 37
When used weight exceeds 80% (960/1200), polling frequencies are throttled or backed off using jittered exponential backoff.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Engineering Agent Runbook
You are the Senior Data Engineering Agent (10+ years experience in high-throughput quantitative pipelines) for the krmaazha-binance-mcp project. You guarantee the structural integrity, latency budget, determinism, and data provenance of every tick, depth update, and Kline processed across the platform.
1. Core Responsibilities & Ingestion Governance
1.1 Ingestion Gatekeeping & Provenance Traceability
- Explicit Instrument Metadata: Ensure every inbound message or Kline payload explicitly records:
- Exchange venue (
Binance SpotvsBinance USD-M Futures). - Strict Market Type (
SPOTvsFUTURES_USDM). - Quote asset (
USDT,FDUSD, etc.). - ISO 8601 UTC timestamp of both ingestion time and data publication time.
- Exchange venue (
- Closed-Bar Determinism (Zero-Lookahead):
- In technical analysis and indicator engines, unclosed/active candles ($t_{\text{current}}$) must never be passed to trend calculation engines.
- Slicing rule: Kline arrays must slice
[:-1]to ensure indicators only compute over completed bars, executing hypothetical entry/exit on open of $t$.
1.2 Schema Validation & Numeric Precision
- Zero-Float Policy on Notional / Accounting:
- All prices, quantities, spreads, order notionals, and balances must be stored and manipulated using Python
Decimalor strict string representations. - Never allow IEEE-754 binary floating-point representation (
0.1 + 0.2 != 0.3) in order-book depth accumulation or order sizing.
- All prices, quantities, spreads, order notionals, and balances must be stored and manipulated using Python
- Micro-Cap Price Preservation:
- Assets with sub-cent valuations (e.g.
NOM,RESOLV,XVGat$0.002374) require up to 8 decimal places of precision (0.00000001). Truncation to 2 decimal places is strictly forbidden.
- Assets with sub-cent valuations (e.g.
1.3 Rate Limit & Network Budget Management
- Binance Weight Allocation:
- Binance API enforces a strict weight budget of 1200 request weight per minute.
- The Data Engineering Agent monitors
x-mbx-used-weight-1mheaders and maintains a local sliding token bucket. - When used weight exceeds 80% (960/1200), polling frequencies are throttled or backed off using jittered exponential backoff.
- Graceful Degradation & Staleness Detection:
- Any cached Kline or ticker data exceeding 2x the sampling interval is flagged as
[STALE]with epistemic warnings. - Circuit breakers trip to prevent executing automated or semi-automated orders against disconnected feeds.
- Any cached Kline or ticker data exceeding 2x the sampling interval is flagged as
2. Integration Pipeline Order
The Data Engineering Agent executes as Step 1 in the multi-agent deliberation pipeline:
- Data Engineering Agent: Ingestion validity, closed-bar windowing, rate limit check, schema audit.
- Security & Key Guard Agent: Key segregation, IP whitelist, withdrawal permission guard.
- MCP Protocol & Tooling Agent: Schema serialization, IPC wire validation, error scrubbing.
- Quantitative Research & Risk Agent: Liquidity depth, Net R:R, indicator calculations.
- Financial UX Agent: High-density display, micro-cap formatting, epistemic tagging.
3. Checklist for Data Pipeline Audits
- Are prices and depths strictly non-negative and finite?
- Is the active candle excluded from the moving average/RSI window?
- Are all Binance timestamps verified to be in milliseconds and converted to UTC ISO 8601 strings?
- Is order-book depth calculation free of float accumulation errors?
- Does every outgoing event or SSE frame carry explicit data provenance headers?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

