一键导入
creating-skills
Use when a new reusable skill needs to be built, either detected by gap analysis, requested by the user, or triggered by /singularity-create
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when a new reusable skill needs to be built, either detected by gap analysis, requested by the user, or triggered by /singularity-create
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a skill has proven itself with consistently high scores across multiple executions and should be locked as a stable, immutable version via /singularity-crystallize
Use when wanting an overview of all singularity-managed skills showing their scores, maturity levels, trends, and alerts via /singularity-dashboard
Use when a singularity-managed skill is failing, scoring below threshold, or producing incorrect outputs that need automated correction via /singularity-repair
Use when wanting to assess the health of a singularity-managed skill, check its maturity, decide whether it needs repair or is ready for crystallization via /singularity-review
Use after any singularity-managed skill execution to rate performance 0-100, track quality over time, and trigger repair when scores drop below threshold
Use when starting any conversation where skills may need to be created, evaluated, repaired, or when a capability gap is detected during task execution
| name | creating-skills |
| description | Use when a new reusable skill needs to be built, either detected by gap analysis, requested by the user, or triggered by /singularity-create |
Build a new Claude Code skill through a structured workflow that ensures quality, testability, and integration with the singularity evolution engine.
superpowers:writing-skills if available — it defines SKILL.md authoring best practicesAsk the user ONE question at a time:
Read ~/.claude/singularity/registry.json to verify no duplicate or overlapping skill exists.
If a similar skill exists, ask: "A skill called '' already covers . Should I extend it or create a separate skill?"
Create the skill following these conventions:
---
name: <skill-name> # kebab-case, verb-first (e.g., creating-api-clients)
description: Use when <triggering conditions> # Max 500 chars, start with "Use when"
---
Content structure:
Rules:
superpowers:skill-name) not file pathsWrite to ~/.claude/skills/<skill-name>/SKILL.md
If the skill needs supporting files (templates, rubrics, scripts), create them in:
~/.claude/skills/<skill-name>/references/
Update ~/.claude/singularity/registry.json:
# Using score-manager to initialize scoring
"${CLAUDE_PLUGIN_ROOT}/scripts/score-manager.sh" init <skill-name>
Then update registry.json to add the skill entry:
{
"skills": {
"<skill-name>": {
"location": "~/.claude/skills/<skill-name>/SKILL.md",
"createdBy": "singularity-claude:creating-skills",
"createdAt": "<ISO-8601>",
"currentVersion": "v1.0.0",
"maturity": "draft",
"tags": ["<relevant>", "<tags>"],
"lastExecuted": null,
"executionCount": 0,
"averageScore": 0
}
}
}
Invoke the newly created skill via the Skill tool to verify it loads correctly.
Run singularity-claude:scoring on the test output to establish a baseline score.
"${CLAUDE_PLUGIN_ROOT}/scripts/telemetry-writer.sh" log <skill-name> \
--trigger "creation" \
--summary "Created new skill: <description>"
After creation, report:
~/.claude/skills/<skill-name>/SKILL.md/singularity-score