菜单
Run the validate-templates checks locally on Windows before pushing. Use when the user wants to validate templates locally, run validation, check meta.yml, verify CSV header, or reproduce CI validation failures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review an asset at version 0.0.0 against the repo conventions and graduate it to 0.1.0 once it passes. Use when the user wants to review a template, graduate a template, mark a template stable, bump from 0.0.0, or close a template-review issue.
Walk through creating a new asset in todoist-playbook (CSV template, prompt template, or bundle). Use when the user wants to add a new template, add a new prompt, add a new bundle, scaffold a Todoist template, or create a starter kit. Bundles meta.yml / bundle.yml / template.csv / prompt.md stubs.
Branch, commit, push, and open a PR using the repo conventions and gh CLI. Use when the user says open a PR, create a pull request, push a branch, ship this, or commit and push.
| name | validate-templates-locally |
| description | Run the validate-templates checks locally on Windows before pushing. Use when the user wants to validate templates locally, run validation, check meta.yml, verify CSV header, or reproduce CI validation failures. |
validate-templates.yml CI failure locallymeta.yml, template.csv, prompt.md, or bundle.ymlcd /c/Users/<you>/path/to/todoist-playbook
Open .github/workflows/reusable-validate-templates.yml and copy each run: block in turn into Git Bash. The workflow is the single source of truth for validation logic — do not maintain a parallel script.
Typical checks include:
template.csv + meta.yml + README.md, or prompt.md + meta.yml + README.md)meta.yml contains every required keymeta.yml slug: equals the folder nametemplate.csv first line equals the canonical TYPE headertemplate.csv TYPE column values are only section, task, or metaproject_color (when present) appears in .github/scripts/project_colors.txtprompt.md contains at least one {{placeholder}} and inputs: is present in meta.ymlRe-run the failing block after each fix until clean. If a check seems wrong, treat the workflow as canonical — fix the asset, not the check.
Even after a clean local run, push the branch and let validate-templates.yml confirm in CI before opening / updating a PR.
meta.yml slug has stray quotes or trailing whitespaceREADME.md is missing import instructions for a CSV templateproject_color value is not in the allow-listinputs: and {{placeholder}} names disagreeDUE_DATE