.claude/skills/self-check/SKILL.md
Audit Prismstack's own skills using its own 15D quality rubric. Trigger: "check our skills", "self audit", "eat our own dog food", "self-check" Do NOT use when: checking a user's domain stack (use the product /skill-check for that)
npx skillsauth add fagemx/prismstack self-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are Prismstack's internal quality auditor. Your job is to score Prismstack's own 10 product skills using the same 15D rubric we ship to users. Eating our own dog food.
Read skills/shared/methodology/quality-standards.md from the Prismstack project root.
Extract all 15 dimensions and their scoring criteria. These are the exact dimensions you will score against — do not invent your own.
If the file is missing or unreadable, stop and report: "Cannot run self-check — quality-standards.md not found."
ls skills/*/SKILL.md
Expect 10 product skills. Read each SKILL.md fully. If fewer than 10 are found, note which are missing.
For each skill, score every dimension 1-5 using the rubric criteria from Phase 1.
Output a summary table:
| Skill | D1 | D2 | D3 | ... | D15 | Total | Avg |
|-----------------|----|----|----|----- |-----|-------|------|
| domain-plan | 4 | 5 | 3 | ... | 4 | 58 | 3.87 |
| domain-build | 3 | 4 | 4 | ... | 3 | 52 | 3.47 |
| ... | | | | | | | |
For any score below 3, add a one-line explanation of what is lacking.
After scoring all 10, look for systemic patterns:
Check if .claude/skills/self-check/last-results.json exists.
If it does, load it and compute deltas:
If no previous results exist, note: "First run — no baseline for comparison."
Present in this order:
Write results to .claude/skills/self-check/last-results.json:
{
"timestamp": "YYYY-MM-DDTHH:MM:SS",
"version": "<from VERSION file>",
"skills": {
"domain-plan": { "scores": { "D1": 4, "D2": 5, ... }, "total": 58, "avg": 3.87 },
...
},
"dimension_averages": { "D1": 3.8, "D2": 4.1, ... },
"overall_average": 3.72
}
Confirm the file was saved so the next run can compare.
data-ai
查看和編輯 domain stack 的 artifact flow、skill 串接、workflow graph。 Trigger: 用戶說「改 workflow」、「skill 串接」、「調整流程」、「看 artifact flow」。 Do NOT use when: 要改 skill 內部(用 /skill-edit)。 Do NOT use when: 要加新 skill(用 /skill-gen)。 上游:現有 domain stack。 下游:被修改的 skill 們。 產出:更新後的 workflow-graph.md + 修改的 SKILL.md 檔案。
tools
打造工具型 skill。雙層架構: Layer 1(直接做):幫用戶自動化一個具體目標。 Layer 2(產出 skill):產出可重複使用的工具型 skill。 涵蓋:browser automation、API 串接、CLI 工具、檔案處理、外部服務。 Trigger: 用戶說「自動化這個網站」、「做一個工具」、「API 串接」、「幫我寫腳本」。 Do NOT use when: 要建 domain skill(用 /skill-gen)。 Do NOT use when: 要轉換已有材料為 skill(用 /source-convert)。 上游:用戶需求 + 目標平台。 下游:/skill-check review。 產出:Layer 1 = working automation / Layer 2 = SKILL.md + scripts/。
devops
Prismstack 超級引導員 — 實戰教練。 Trigger: 用戶不知道下一步、想學串 pipeline、卡關倦怠、想理解 skill 原理、 問「怎麼用」「為什麼這樣設計」「怎麼自動化」。 Do NOT use when: 用戶明確知道要跑哪個 skill(用 /prism-routing)。 Do NOT use when: 用戶要規劃新 domain stack(用 /domain-plan)。 並存:/prism-routing 是快速路由(熟手用),/super-guide 是教學引導(需要理解的人用)。 上游:任何 skill 的產出、用戶的 domain stack。 下游:任何 Prismstack skill(引導完畢後可直接啟動)。
tools
把任何外部來源轉換成 gstack skill 或 skill 片段。 來源類型:skill repo、prompt、影片、文章、書、SOP、代碼庫、ECC skill、git history、用戶想法。 Trigger: 用戶說「這篇文章很好」、「這個 repo 想用」、「把這個變成 skill」、「轉換」。 Do NOT use when: 要從零建 skill(用 /skill-gen)。 Do NOT use when: 要建工具型 skill(用 /tool-builder)。 上游:任何外部來源。 下游:/skill-edit 或 /skill-gen(取決於 placement)。 產出:轉換後的 skill content(新 skill / section / patch)。