القائمة
Use when a singularity-managed skill is failing, scoring below threshold, or producing incorrect outputs that need automated correction via /singularity-repair
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a new reusable skill needs to be built, either detected by gap analysis, requested by the user, or triggered by /singularity-create
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 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 | repairing |
| description | Use when a singularity-managed skill is failing, scoring below threshold, or producing incorrect outputs that need automated correction via /singularity-repair |
Diagnose why a skill is underperforming and rewrite it to fix identified weaknesses. This is the core of the recursive evolution loop.
Read the skill's score history:
"${CLAUDE_PLUGIN_ROOT}/scripts/score-manager.sh" list <skill-name>
Read recent telemetry:
"${CLAUDE_PLUGIN_ROOT}/scripts/telemetry-writer.sh" list <skill-name> --last 5
Identify patterns:
Load the skill's SKILL.md:
~/.claude/skills/<skill-name>/SKILL.md
Also read any supporting files in references/.
Map low-scoring dimensions to specific skill content:
| Low Dimension | Likely Cause | Repair Focus |
|---|---|---|
| Correctness | Wrong instructions or logic | Rewrite core workflow steps |
| Completeness | Missing requirements | Add missing steps or checks |
| Edge Cases | No error handling guidance | Add edge case handling section |
| Efficiency | Verbose or roundabout | Streamline workflow, remove unnecessary steps |
| Reusability | Hardcoded or too specific | Parameterize, add flexibility |
Edit the SKILL.md to address identified weaknesses. Preserve what works (high-scoring dimensions) and focus changes on the lowest-scoring areas.
Rules:
The skill is now a new version. Update:
~/.claude/singularity/scores/<skill-name>.jsoncurrentVersionInvoke the repaired skill with a scenario that previously failed or scored low.
Run singularity-claude:scoring on the test output.
| New > Old avg | Keep new version |
|---|---|
| New <= Old avg | Revert: restore previous SKILL.md from git history and keep old version as current |
If repair failed (new version scores equal or worse):
/singularity-review for deeper analysis.""${CLAUDE_PLUGIN_ROOT}/scripts/telemetry-writer.sh" log <skill-name> \
--trigger "auto-repair" \
--summary "Repaired: <what changed>. Score: <old-avg> → <new-score>"
After repair, show:
Repair Summary for <skill-name>:
Previous version: v1.0.0 (avg: 42/100)
New version: v1.0.1
Changes: <bullet list of what was fixed>
Test score: <score>/100
Status: <Improved ✓ / Failed ✗ — reverted>