菜单
Scaffold a new logic-* skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hyhmrright/logic-lens --skill new-skill命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | new-skill |
| description | Scaffold a new logic-* skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens. |
| disable-model-invocation | true |
CLAUDE.md → "Adding a New Skill" is the authoritative checklist. This skill exists to make sure every step actually runs — the session-start loop and the eval cases are the ones most often forgotten.
Read CLAUDE.md's "Adding a New Skill" section now, then execute its steps for logic-<NAME> (ask the user for <NAME> if not in $ARGUMENTS):
skills/logic-<NAME>/SKILL.md — copy the frontmatter shape from skills/logic-review/SKILL.md (name + description). The description MUST include a "Do NOT trigger for:" clause and a "SCOPE … RULE" line distinguishing it from the other skills. Process section = 5–7 numbered items, each citing a guide step. Follow lazy-loading per skills/_shared/common.md §13.skills/logic-<NAME>/logic-<NAME>-guide.md — numbered steps (Step 1, 2, …), each explaining the why, concrete examples over abstractions.commands/logic-<NAME>.md — mirror commands/logic-review.md:
---
description: <one line>
allowed-tools: Skill
---
Use the Skill tool to invoke `logic-lens:logic-<NAME>`, then follow its instructions exactly. $ARGUMENTS
hooks/session-start (CLAUDE.md step 6 — easy to miss) — add logic-<NAME> to BOTH the for skill in … loop and the printed skill list:
grep -n "for skill in" hooks/session-start
evals/content/v2/evals-v2.json. Trigger cases under evals/trigger/v2/ are optional and only catch description regressions (positive cases always score 0% — see CLAUDE.md → Gotchas).gemini-extension.json — CLAUDE.md says Gemini auto-discovers from skills/, but the file also enumerates each skill+command under contribution. If you want that list complete, add logic-<NAME> entries to both contribution.skills and contribution.commands. (Not checked by validate-repo.sh.)npm run validate and confirm all checks pass.