VincenzoImp/academic-research-skills / skills/develop-contribution
develop-contribution
VerifiedUse when creating a new contribution (analysis, experiment, dataset, software, reproduction) or regularizing a draft folder into badge compliance with its LaTeX report.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| references/data.md | markdown | 2.1 KB |
| references/ethics.md | markdown | 668 B |
| references/experiments.md | markdown | 889 B |
| references/methodology.md | markdown | 1.1 KB |
| references/reproduction.md | markdown | 841 B |
references/data.md
View on GitHub# Data & Input Dependencies
Where a contribution's data lives, and how to handle data that flows between
contributions. Optional — use it only when a contribution has shared/large data
or consumes another contribution's output.
## Where data lives (two axes)
Decide by sharing scope and by tracked-vs-gitignored, not by size alone:
- **Private + small + curated + non-sensitive** (a hand-made input file, the
contribution's own result tables/figures) → committed **inside** the
contribution (`contributions/<slug>/…`).
- **Large OR regenerable OR governed/sensitive** → **gitignored**. For
data-heavy projects, keep it in one root `data/` organized by a subfolder per
**owning** contribution: `data/<slug>/` with tiers `raw/` (immutable source),
`interim/` (regenerable intermediates), `processed/` (consumable datasets).
One root = one place to gitignore, back up, and find; per-contribution
subfolders = clear ownership.
- **Sensitive data** (account ids, raw PII) never enters the tracked tree — see
`ethics.md`.
## Inter-contribution data dependencies
A contribution's input is often another contribution's output, or data
generated and archived by another contribution. When so:
- **Declare** the dependency in this contribution's README: name the producer
contribution and the dataset it consumes.
- **Read it in place** at the producer's location (`data/<producer>/…`) —
**never copy** it into your own folder. One dataset, one physical home.
- Record the lineage under the README "data provenance" badge item (which
contribution and which output produced this input).
## Single source of truth for paths
Map each logical dataset to its one physical location in a single module or
config (e.g. a `paths` module), not as literals scattered across scripts — so
the producing contribution can change the layout in one place without breaking
its consumers.
Rules: a contribution stays self-contained at the interface — it declares what
it reads and never imports another contribution's *code*; data it consumes is
read from the producer's declared location, never duplicated.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |