apps/app/src/app/data/skill-creator.md

The `skill-creator` skill: a template + checklist for authoring new OpenCode/Claude skills inside a workspace. Defines what a skill is (a folder under `.opencode/skills/<name>/` or `.claude/skills/<name>/` anchored by `SKILL.md`), LegalWork-specific behavior (prefer `.opencode/skills/...`, write the real file so the in-app reload banner appears rather than pasting into chat), portability/ credential-safety design goals, the recommended folder structure, the critical "trigger phrases" rule for the description field, a frontmatter template, and an authoring checklist. When creating a new skill for a LegalWork workspace and you want the structure, trigger-phrase rules, and reload-banner convention.

name: skill-creator description: Guide for creating effective skills. Use when users want to create or update a skill that extends OpenCode with specialized knowledge, workflows, or tool integrations.

Skill Creator

This skill is a template + checklist for creating skills in a workspace.

What is a skill?

A skill is a folder under .opencode/skills/<skill-name>/ or .claude/skills/<skill-name>/ anchored by SKILL.md.

LegalWork behavior

In LegalWork, prefer creating the skill at .opencode/skills/<skill-name>/SKILL.md.
Use a file mutation tool (write, edit, or apply_patch) on the real skill path instead of pasting the whole skill into chat.
Writing the skill file lets LegalWork show the reload banner above the conversation so the user can activate the new skill immediately.

Design goals

Portable: safe to copy between machines
Reconstructable: can recreate any required local state
Self-building: can bootstrap its own config/state
Credential-safe: no secrets committed; graceful first-time setup

Recommended structure

.opencode/
  skills/
    my-skill/
      SKILL.md
      README.md
      templates/
      scripts/

Trigger phrases (critical)

The description field is how Claude decides when to use your skill. Include 2-3 specific phrases that should trigger it.

Bad example: "Use when working with content"

Good examples: "Use when user mentions 'content pipeline', 'add to content database', or 'schedule a post'" "Triggers on: 'rotate PDF', 'flip PDF pages', 'change PDF orientation'"

Quick validation:

Contains at least one quoted phrase
Uses "when" or "triggers"
Longer than ~50 characters

Frontmatter template

---
name: my-skill
description: |
  [What it does in one sentence]

  Triggers when user mentions:
  - "[specific phrase 1]"
  - "[specific phrase 2]"
  - "[specific phrase 3]"
---

Authoring checklist

Start with a clear purpose statement: when to use it + what it outputs.
Specify inputs/outputs and any required permissions.
Include “Setup” steps if the skill needs local tooling.
Add examples: at least 2 realistic user prompts.
Keep it safe: avoid destructive defaults; ask for confirmation.
In LegalWork, finish by writing the final SKILL.md file to .opencode/skills/<skill-name>/SKILL.md so the reload banner can appear.