cot_prompt_templates
Build standard, chain-of-thought, and ablation few-shot prompts with auditable prompt structure metadata.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- cot_prompt_templates
- description
- Build standard, chain-of-thought, and ablation few-shot prompts with auditable prompt structure metadata.
02 资源文件 2
03 SKILL.md 正文
Chain-of-Thought Prompt Templates
Use this skill when you need to construct prompts for the chain-of-thought prompting paper or for a recovery experiment that compares direct few-shot answers against reasoning-before-answer exemplars. Do not use it to run an LLM, compute a task answer, or score a prediction.
Inputs
- A JSON list of exemplars. Every exemplar needs
questionandanswer; chain-of-thought and ablation modes also needreasoning. - A target question string.
- A mode:
standard,chain_of_thought,equation_only,variable_compute_only, orreasoning_after_answer.
Outputs
- Prompt text containing rendered exemplars and the target question.
- Metadata describing mode, exemplar count, reasoning placement, and whether final-answer markers are present.
Workflow
- Select the prompt mode that matches the comparison being run.
- Validate exemplar fields before rendering; reject missing reasoning in chain-of-thought modes.
- Render exemplars as
Q:andA:blocks. - For
chain_of_thought, place reasoning beforeThe answer is .... - For
standard, omit reasoning and include only the direct answer. - For ablations, preserve the structural difference being tested: equations only, useless variable-compute padding, or reasoning after the answer.
- Append the target question and
A:prefix without including the target answer.
Validation
Run:
python scripts/cot_prompt_templates.py --self-test
python -m unittest discover -s tests
The tests verify that standard prompts omit reasoning, chain-of-thought prompts include reasoning before the final answer, and ablation modes are structurally distinct.
Limitations
This skill does not infer missing reasoning, call a model, or canonicalize answers. Pair it with cot_answer_extraction and cot_equation_calculator for evaluation or recovery work.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).