How do I install the Data Pipeline Feasibility Check skill?

Run npx skillmds@latest add mittuled/data-pipeline-feasibility-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Data Pipeline Feasibility Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Data Pipeline Feasibility Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Data Pipeline Feasibility Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Data Pipeline Feasibility Check?

mittuled (@mittuled) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Data Pipeline Feasibility Check by mittuled

Name: Data Pipeline Feasibility Check
Author: mittuled

Data Pipeline Feasibility Check

This skill assesses whether a proposed data pipeline is feasible given available data sources and infrastructure. Use when asked to validate a pipeline idea, check source availability, or evaluate infrastructure readiness. Also consider when stakeholders propose tight SLAs on untested sources. Suggest when the user is about to commit engineering effort to a pipeline without validating assumptions.

mittuled c7645a1 3 files · 13.7 KB Updated Sep 17, 2026

File contents

data-pipeline-feasibility-check

Agent: Data Engineer

L2 data engineer (Nx) responsible for data pipeline design, data warehouse schema, pipeline building, reliability testing, data quality monitoring, and scale planning.

Department ethos: ideal-engineering.md

Skill Description

Assesses whether a proposed data pipeline is feasible given available data sources, infrastructure capacity, and timeline constraints.

When to Use

When a new pipeline request arrives and source connectivity has not been verified.
When stakeholders propose freshness SLAs that may exceed infrastructure capabilities.
When a pipeline depends on third-party APIs with unknown rate limits or reliability.

Workflow

Source Probe: Connect to each proposed source system and verify API availability, authentication, rate limits, and data format. Deliverable: source access verification report.
Volume Estimation: Profile source data to estimate row counts, payload sizes, and growth rates. Deliverable: volume forecast with confidence intervals.
Infrastructure Gap Analysis: Compare pipeline compute, storage, and network requirements against current capacity. Deliverable: gap analysis with cost estimates for any required provisioning.
Feasibility Verdict: Synthesize findings into a go/no-go recommendation with conditions and risks. Deliverable: feasibility assessment document.

Anti-Patterns

Assuming API stability: Treating third-party API schemas and rate limits as fixed without contractual guarantees. Why: unannounced API changes cause silent pipeline failures that propagate bad data downstream.
Skipping the volume profile: Estimating data volume from stakeholder guesses instead of sampling. Why: order-of-magnitude errors in volume estimates lead to under-provisioned infrastructure and missed SLAs.

Output

On success: Produces a feasibility assessment document with go/no-go verdict, source verification results, volume forecasts, and infrastructure gap analysis. Delivered as a markdown artifact.

On failure: Report which feasibility dimension failed (source access, volume, infrastructure), what was tested, and recommended remediation steps.

Related Skills

data-pipeline-designer -- Proceeds with full design once feasibility is confirmed.

---name: data-pipeline-feasibility-checkdescription: This skill assesses whether a proposed data pipeline is feasible given available data sources and infrastructure. Use when asked to validate a pipeline idea, check source availability, or evaluate infrastructure readiness. Also consider when stakeholders propose tight SLAs on untested sources. Suggest when the user is about to commit engineering effort to a pipeline without validating assumptions.---# data-pipeline-feasibility-check## Agent: Data EngineerL2 data engineer (Nx) responsible for data pipeline design, data warehouse schema, pipeline building, reliability testing, data quality monitoring, and scale planning.Department ethos: [ideal-engineering.md](../../../../departments/engineering/ideal-engineering.md)## Skill DescriptionAssesses whether a proposed data pipeline is feasible given available data sources, infrastructure capacity, and timeline constraints.## When to Use- When a new pipeline request arrives and source connectivity has not been verified.- When stakeholders propose freshness SLAs that may exceed infrastructure capabilities.- When a pipeline depends on third-party APIs with unknown rate limits or reliability.## Workflow1. **Source Probe**: Connect to each proposed source system and verify API availability, authentication, rate limits, and data format. Deliverable: source access verification report.2. **Volume Estimation**: Profile source data to estimate row counts, payload sizes, and growth rates. Deliverable: volume forecast with confidence intervals.3. **Infrastructure Gap Analysis**: Compare pipeline compute, storage, and network requirements against current capacity. Deliverable: gap analysis with cost estimates for any required provisioning.4. **Feasibility Verdict**: Synthesize findings into a go/no-go recommendation with conditions and risks. Deliverable: feasibility assessment document.## Anti-Patterns- **Assuming API stability**: Treating third-party API schemas and rate limits as fixed without contractual guarantees. *Why*: unannounced API changes cause silent pipeline failures that propagate bad data downstream.- **Skipping the volume profile**: Estimating data volume from stakeholder guesses instead of sampling. *Why*: order-of-magnitude errors in volume estimates lead to under-provisioned infrastructure and missed SLAs.## Output**On success**: Produces a feasibility assessment document with go/no-go verdict, source verification results, volume forecasts, and infrastructure gap analysis. Delivered as a markdown artifact.**On failure**: Report which feasibility dimension failed (source access, volume, infrastructure), what was tested, and recommended remediation steps.## Related Skills- [`data-pipeline-designer`](../data-pipeline-designer/SKILL.md) -- Proceeds with full design once feasibility is confirmed.

Frequently asked questions