yonglun/dama-skill / skills/delivering-data-science
delivering-data-science
VerifiedUse when a project must test a data-driven hypothesis, develop or deploy a statistical or machine-learning model, combine new data sources for hypothesis testing, prediction, or model-based insight, or manage experiment validity, model evaluation, reproducibility, production monitoring, and retirement.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| agents/openai.yaml | config | 293 B |
| references/playbook.md | markdown | 13.3 KB |
| templates/delivery-pack.en.md | markdown | 3.1 KB |
| templates/delivery-pack.zh.md | markdown | 2.8 KB |
| templates/register.en.xlsx | binary | 8.5 KB |
| templates/register.zh.xlsx | binary | 9.0 KB |
| templates/report.en.docx | binary | 37.5 KB |
| templates/report.zh.docx | binary | 38.0 KB |
templates/delivery-pack.en.md
View on GitHub# Data Science Delivery Pack
Skill: `delivering-data-science`
[Word report](report.en.docx) · [Excel register](register.en.xlsx)
## Record details
| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |
## Domain analysis and decisions
### Business hypothesis and decision boundary (`hypothesis`)
Define the hypothesis, baseline, success criteria, and decisions not delegated to automation.
> Enter project evidence, conclusion, and owner.
### Data features and labels (`data_features`)
Fix prediction time, data purpose, feature availability, label delay, and leakage checks.
> Enter project evidence, conclusion, and owner.
### Experiment and evaluation protocol (`evaluation`)
Set temporal split, independent test, group errors, costs, and comparator metrics.
> Enter project evidence, conclusion, and owner.
### Reproducibility evidence (`reproducibility`)
Record data version, code, environment, randomness, and evaluation artifacts.
> Enter project evidence, conclusion, and owner.
### Model card and limitations (`model_card`)
State intended use, performance, known failures, affected groups, and human fallback.
> Enter project evidence, conclusion, and owner.
### Production service and rollout (`production`)
Define shadow or canary gates, human process, observability, and release approval.
> Enter project evidence, conclusion, and owner.
### Monitoring retraining and change (`monitoring`)
Set drift, effectiveness, bias, retraining triggers, and independent review.
> Enter project evidence, conclusion, and owner.
### Rollback and retirement (`rollback`)
Define stop thresholds, rollback, data retention, and retirement ownership.
> Enter project evidence, conclusion, and owner.
## Working registers
### Data Features (`features`)
Record feature sources, availability, and use constraints.
| Feature (`feature`) | Definition (`definition`) | Source (`source`) | Rule (`rule`) | Owner (`owner`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- |
| | | | | | |
### Validation Monitoring (`validation`)
Track independent validation, drift, and stop actions.
| Metric (`metric`) | Validation (`validation`) | Drift threshold (`drift_threshold`) | Test result (`test_result`) | Owner (`owner`) | Evidence (`evidence`) | Review date (`review_date`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |