excel-schema-and-mapping
Use when working with the Excel data files, brand column mapping, missing-column errors, or a data-source header rename. Trigger when a brand shows zero sales, a column is not found, or new files do not match the schema.
- License 许可
- MIT
- 最近更新
- 2026-08-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- excel-schema-and-mapping
- license
- MIT
- sources
- [ "anthropics/skills (xlsx)", "MiniMax-AI/skills (minimax-xlsx)" ]
- version
- 1.0.0
- description
- Use when working with the Excel data files, brand column mapping, missing-column errors, or a data-source header rename. Trigger when a brand shows zero sales, a column is not found, or new files do not match the schema.
03 SKILL.md 正文
Excel Schema & Column Mapping
Two layers: config.py defaults + per-company mappings
The default schema lives in config.py — a rename there is a config change,
not a code change. But each company (companies/<slug>.json) can carry its own
schema.sales / schema.party mapping (sheet, header_row, {role: actual
column}); the first load of a file auto-detects it via schema.py (fuzzy
synonym matching) and stores it. pipeline.load_dataframes renames the
actual columns to the canonical names at load time, so the engine never sees
the raw layout.
The default schema (config.py)
| Setting | Default | Meaning |
|---|---|---|
SALES_SHEET |
"DATA" |
sheet holding transactions |
SALES_HEADER_ROW |
4 |
0-indexed header row of the sales dump |
COL_DEPOT |
"Name Of Depot" |
sales: owning depot |
COL_SYNDICATE |
"SYNDICATE NAME" |
sales: group/syndicate |
COL_VENDOR |
"VENDOR_NAME" |
sales: outlet/vendor |
COL_PARTY |
"PARTY" |
master: join key |
COL_SEND / COL_PRIORITY / COL_PHONE |
"SEND" / "PRIORITY" / "PHONE" |
master: report opt-in, priority slab, contact |
COL_TOTAL |
"Total" |
sales: volume column |
TOTAL_TARGET_COL |
"TOTAL_TARGET" |
master: overall target |
INDIVIDUAL_SYNDICATE |
"INDIVIDUAL" |
standalone-outlet sentinel — compared case-sensitively |
SEND_YES |
"YES" |
always-report value (case-insensitive) |
Brand columns
Default convention: target <CODE>_TARGET in the master, actual <CODE>.1 in the sales dump — overridable per brand via target_col / actual_col in user_settings.json.
Helpers
pipeline.detect_column_candidates(df_sales, df_master)— suggests column dropdowns for the brand dialog.pipeline.validate_brand_columns(settings, df_sales, df_master)— missing-column report before a run (skips muted brands).- GUI: the Brands tab offers detected-column Comboboxes; a run with missing columns warns and asks before continuing.
When a column is renamed upstream
Edit the value in config.py (and only that) for the global default — or, for
one company only, update its companies/<slug>.json schema mapping (or re-run
the mapping dialog in the GUI Company/Run flow). No pipeline/template changes.
For a brand with a custom column, update it in user_settings.json or the
Brands tab.
Common mistakes
- Treating
SALES_HEADER_ROW = 4as 1-based — it is 0-indexed (the 5th row). - A typo'd brand column silently zeroing a whole brand — run mapping validation before dispatching.
- Expecting case-insensitivity from
INDIVIDUAL_SYNDICATE— it is compared as-is.
04 同仓库更多 Skills
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).