symbol-table-builder

Build a global symbol table for mathematical modeling concepts across subquestions.

452|24|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/zhnnky329/MathModeling-skills --skill symbol-table-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symbol-table-builder
Source: https://github.com/zhnnky329/MathModeling-skills/tree/main/.claude/skills/symbol-table-builder
Command: npx skills add https://github.com/zhnnky329/MathModeling-skills --skill symbol-table-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and maintain a single, unified symbol table to ensure consistent notation across all subquestions in a mathematical modeling solution, preventing symbol clashes and misinterpretations.

Core Features & Use Cases

  • Extracts variables from the problem parse and candidate method pools, assigns unique symbols, and tracks their usage across subquestions.
  • Detects and resolves symbol conflicts, harmonizes notation for cross-subquestion handoffs, and records decisions for reproducibility.
  • Provides a global reference (planning/symbol_table.md) that downstream skills must adhere to during code generation and paper composition.

Quick Start

Run the symbol-table-builder to generate the global symbol table, then review planning/symbol_table.md for downstream notation alignment.

Frequently Asked Questions about symbol-table-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain consistent mathematical notation across multiple subquestions?

You can maintain consistent notation by building a global symbol table that captures all concepts across subquestions, assigns unique symbols, and detects conflicts to harmonize cross-question handoffs.

What is a symbol table and when do I need it for mathematical modeling?

A symbol table is a structured record detailing symbol meanings, domains, and usage. You need it when parsing multi-question problems to prevent symbol clashes and misinterpretations during downstream code generation.

How do I resolve symbol conflicts when variables overlap across different subquestions?

Resolve symbol conflicts by applying the symbol-table-builder after problem parsing to enforce unique symbols for each concept, record the resolution history, and produce a structured reference for unambiguous downstream usage.

Can I use a unified symbol table for downstream code generation and paper composition?

Yes, the symbol-table-builder generates a global reference file that downstream skills must adhere to during code generation and paper composition, ensuring all notation remains aligned across the entire workflow.

What types of concepts should be tracked in a global symbol table?

A global symbol table should track sets, indices, parameters, decision variables, state variables, inputs, and outputs, capturing their meanings and domains to ensure cross-subquestion consistency.