Place the skill at .claude/skills-impl/<layer>/<scope>/<skill-name>/SKILL.md. The skill name MUST match the parent <scope>/ directory:
torch/quark-torch-*onnx/quark-onnx-*shared/quark-*(no infix)
For user-facing skills, also add a thin entry stub at .claude/skills/<skill-name>/SKILL.md. The stub's description MUST include backend keywords so the harness can route by prompt-match (torch: PyTorch / HuggingFace safetensors / transformers; onnx: .onnx / onnxruntime).
---
name: <skill-name> # matches the <scope> infix rule above
description: <trigger phrases + backend keywords>
layer: <l0-foundation | l1-atomic | l2-workflows | l3-recipes | meta>
backend: <shared | torch | onnx> # must equal the parent <scope>/ directory
primary_artifact: <artifact file name or report name>
source_knowledge:
- <Quark upstream doc or source file>
---One paragraph describing the stable responsibility boundary of the skill.
- required inputs
- optional defaults
Schema: <primary_artifact>.schema.json
{ "...": "example matching the schema" }- Intake
- Route
- Plan
- Confirm
- Execute or Summarize
- common failure modes
- recovery advice
- traceability to upstream docs, CLI, or code
- guardrails that should not be silently skipped