菜单
Interview the user to produce a structured work-assignment document — background, current state, and per-task breakdown with input/output/checklist. Use when the user says "calm-down assign", wants to hand off work, delegate a task, or needs to write an assignment document for a teammate.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/chuan-khuna/altr-skills --skill calm-down命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Configure an install cooldown (minimum release age) so freshly-published npm package versions can't be installed until they've been public long enough to be caught. Writes .npmrc, bunfig.toml, pnpm-workspace.yaml, or .yarnrc.yml. Use when the user says "harden dependencies", "set up install cooldown", "minimumReleaseAge", "min-release-age", "protect against supply chain attacks", or asks how to avoid installing compromised packages.
Write a markdown document from this conversation or by exploring a codebase feature. Use when the user says "write this to a doc", "document this conversation", "explore X and write the doc", "write how X works", or asks to produce a markdown document from chat context or code investigation.
Query Jira for a start-of-day summary of your tasks. Use when the user says "start of day", "morning standup", "what are my tasks today", "what's on my plate", "daily summary", or asks for a Jira task overview.
基于 SOC 职业分类
正在显示 SKILL.md
| name | calm-down |
| description | Interview the user to produce a structured work-assignment document — background, current state, and per-task breakdown with input/output/checklist. Use when the user says "calm-down assign", wants to hand off work, delegate a task, or needs to write an assignment document for a teammate. |
Help the user turn a rough idea into a structured assignment document a teammate can pick up without prior context.
calm-down assign <brief>
<brief> is the task description — e.g. calm-down assign copy video files and rebuild the app.
Read the <brief> and immediately propose a task list:
Based on your brief, I'm guessing there are N tasks:
- {Task name}
- {Task name}
- {Task name}
Does that look right? Anything to add or change?
Wait for confirmation before proceeding.
Ask one question at a time. Cover only what the brief doesn't already make clear:
Skip questions that are already obvious from the brief.
For each confirmed task, ask one at a time:
Keep total question count across Phase 1 and Phase 2 within 10.
Ask:
Should I output this as md or html?
Then generate immediately. Save to docs/yyyy-mm-dd-{topic}.{md,html} by default.
Tell the user the exact path after saving. If they want a different location, they can say so.
Write the document using the format in references/assign-format.md. Do not preview or ask for approval — generate and save immediately.