| name | _template |
| description | Canonical scaffold for new Syncolab skills. Use when bootstrapping a skill directory, copying structure and conventions, or checking required sections and metadata before publishing a real skill. |
Skill Template
Copy this directory to /skills/<skill-label>/, rename placeholders, and replace every section below. Read /skills/skill.instruction.md and /skills/meta.instructions.md, then check the result against /skills/meta.schema.json.
Purpose
This scaffold provides the canonical directory layout, SKILL.md structure, and meta.yaml fields for authoring new Syncolab skills. A real skill should state what operational capability it provides and what “done well” looks like.
When to Use
- Use when creating a new skill from this repository template.
- Use when reviewing whether an in-progress skill has the required files and sections.
When NOT to Use
- Do not treat this directory as a published operational skill.
- Do not route user tasks here except skill authoring or repository maintenance.
Expected Outcome
After copying and editing, the new skill directory should contain valid SKILL.md and meta.yaml that conform to the repository instruction files and schema.
Inputs to Gather
/skills/skill.instruction.md for SKILL.md conventions./skills/meta.instructions.md and /skills/meta.schema.json for metadata.- Existing related skills under
/skills/ for naming and relationship consistency.
Workflow
- Copy
/skills/_template/ to /skills/<skill-label>/ using lowercase kebab-case for <skill-label>.
- Update
SKILL.md frontmatter: name must equal <skill-label>; write a routing-friendly description.
- Replace every section in
SKILL.md with skill-specific guidance; keep the file high-signal.
- Author
meta.yaml per /skills/meta.instructions.md; ensure type, description, tags, and relationships validate.
- Add optional
references/, assets/, or scripts/ only when needed; move large detail out of SKILL.md.
- Review against the schema and instruction files, then use publish-skill to open a PR.
Tool Availability Rules
- If only read tools are available, produce a plan and exact file contents for the user or a dispatched task.
- If write tools are available, create the skill directory, edit files, and run validation.
- Never fabricate validation results or repository state.
Review / Decision / Execution Criteria
- Directory name matches
name in SKILL.md frontmatter.
- Metadata is concise, router-friendly, and consistent with
SKILL.md.
- Boundaries and triggers are explicit enough for reliable routing.
Output Format
When authoring from this template, deliver:
- The target
<skill-label> and file list.
- Completed
SKILL.md and meta.yaml (or a clear diff).
- Validation command output or remaining fixes.
Quality Bar
- High-signal instructions; no marketing filler.
- Evidence-based, concrete workflows and outcomes.
- Safety and tool rules stated explicitly.
- Large reference material lives under
references/, not in SKILL.md.
Safety and Boundaries
- Do not expose secrets in skills or examples.
- Do not invent tool results or validation outcomes.
- State assumptions when context is missing; ask before destructive changes.
Escalation / Dispatch Rules
- If the task spans multiple domains, split work or add
relationships.skills entries instead of bloating one skill.
- Dispatch implementation when write tools are unavailable but changes are required.
References
/skills/skill.instruction.md/skills/meta.instructions.md/skills/meta.schema.json
