data-ingestion
🐉 Fetches and parses time-series data from various sources.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-12
- Stars
- ★ 131
- Forks
- 9
01 前言 Front Matter
- name
- data-ingestion
- metadata
- { "author": "Szymon Stawski + Gemini", "status": "draft", "version": "0.2.0" }
- description
- 🐉 Fetches and parses time-series data from various sources.
02 资源文件 3
- 脚本merge_timeseries.py2.7 KB
- 脚本parse_csv.py2.6 KB
- 参考文档README.md1.4 KB
03 SKILL.md 正文
Data Ingestion Skill
This skill is responsible for fetching and converting time-series data from different sources into a standardized JSON format for other skills to consume.
Inputs:
source_type: String indicating the data source (e.g., "csv", "cloud_monitoring").source_details: A dictionary or list containing the necessary information to access the data source.- For
source_type: "csv": A list of file paths.
- For
Output:
A JSON string in the standardized format (see README.md for details).
Workflow:
- Validate Inputs: Check if
source_typeandsource_detailsare provided. - Route to Parser: Based on
source_type:- If
source_typeis "csv":- Ensure
source_detailsis a list of file paths. - Create a list of temporary file names for intermediate JSON outputs (e.g.,
~/.gemini/tmp/user/parsed_0.json, ...). - Parse Each CSV: Iterate through the input file paths:
- Execute
python ./skills/data-ingestion/parse_csv.py <input_csv_path> > <temp_json_path>usingrun_shell_command(with venv activation). - Check for errors.
- Execute
- Merge JSONs: Execute
python ./skills/data-ingestion/merge_timeseries.py <temp_json_path_1> <temp_json_path_2> ...usingrun_shell_command(with venv activation). - Capture the stdout from
merge_timeseries.pyas the final result. - Clean up: Remove the temporary JSON files.
- Handle any errors during script executions.
- Ensure
- If
source_typeis not supported, return an error message.
- If
- Return JSON: Output the standardized JSON string.
04 同仓库更多 Skills
safe-sre-investigator
🐉 Sets up and uses read-only Service Accounts for GCP and Kubernetes investigations using the principle of least privilege, and provides risk assessments for suggested commands. Use when asked to investigate GCP/GKE resources or suggest gcloud/kubectl commands.
pre-publish-checker
🐉 Thoroughly checks files for profanity, internal links, sensitive paths, and professionalism before publication. Use when preparing a codebase or extension for public release.
postmortem-generator
🐉 Creates a PostMortem given enough context about an incident/outage. Will guide user to timeline, action items/bugs, and finally draft a Google Doc with the results.
postmortem-aggregator
🐉 To be used when you have a folder containing N Post Mortem files. This will help crunch data and maintain/update a POMO_AGGREGATED.md file.
monitoring-graphs
🐉 Skill for generating high-quality, annotated incident graphs for post-mortems using Python. Use this when the user needs to visualize an outage, show error rates, or correlate metrics with incident milestones.
investigation-entrypoint
🐉 The primary entrypoint for investigating production outages, orchestrating SRE response, and mitigating incidents on Google Cloud Platform (GKE, Cloud Run, etc.). Start here when an incident occurs.