cjms-solution-algorithm
Use when choosing the solution route and delivering the algorithm section of a 《中国管理科学》 (Chinese Journal of Management Science) manuscript — exact vs heuristic vs learning-based, with pseudocode, property analysis, and baseline comparison. Covers solving the model; the experiments that showcase it belong to cjms-numerical-experiments.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cjms-solution-algorithm --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 求解与算法设计（cjms-solution-algorithm） ## 触发时机 - 模型建好了，只写"用 Gurobi 求解"一句话 - 自设计算法没有伪代码、没有性质分析、没有对比对象 - 审稿意见出现"算法创新性不足 / 为什么不用现成求解器" ## 核心：求解路线决策表 先答一个审稿人必问的问题：**这个模型为什么不能用现成方法直接解？**答案决定路线： | 模型情形 | 求解路线 | 交付底线 | |----------|----------|----------| | 可转化为 LP/MIP/SOCP 且规模可解 | 商用求解器（Gurobi/CPLEX） | 转化过程 + 规模上限实测；算法不是贡献点 | | 有特殊结构（可分解、单调、凸） | 精确算法（分支定界、列生成、L-shaped、DP） | 结构性质引理 + 收敛/最优性论证 | | NP-难且实例大 | 启发
What does the cjms-solution-algorithm skill do?
Use when choosing the solution route and delivering the algorithm section of a 《中国管理科学》 (Chinese Journal of Management Science) manuscript — exact vs heuristic vs learning-based, with pseudocode, property analysis, and baseline comparison. Covers solving the model; the experiments that showcase it belong to cjms-numerical-experiments.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cjms-solution-algorithm --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.